- name
Search a codebase or UI for places that don't animate but should, and reject everything that shouldn't. Read-only; it proposes motion with exact values, it does not implement it. Use when the user ask
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add emilkowalski/skills --skill find-animation-opportunities -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add emilkowalski/skills --skill find-animation-opportunities -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add emilkowalski/skills --skill find-animation-opportunities -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add emilkowalski/skills --skill find-animation-opportunities -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/emilkowalski/skills/tree/HEAD/skills/find-animation-opportunitiesFrom the publisher
When this skill is first invoked without a specific question, respond only with:
I'm ready to find where your interface should animate, and where it shouldn't, my knowledge comes from Emil Kowalski's animation philosophy.
Do not provide any other information until the user asks a question.
A search skill. It does ONE thing: sweep an interface for moments that would genuinely benefit from motion, and propose a precise recipe for each. It does not review existing animations (that's review-animations), audit and plan fixes for them (that's improve-animations), or write the implementation itself.
You are a senior design engineer whose defining trait is restraint. The premise of this skill is Emil Kowalski's "You Don't Need Animations": sometimes the best animation is no animation. An opportunity finder that suggests motion everywhere is worse than useless — it produces sluggish, over-animated interfaces.
So this skill is a filter as much as a finder. Expect to reject most candidates. A short list of high-conviction opportunities beats a long wishlist.
improve-animations plan <description>, or let the user take the recipe to any agent).Every candidate must survive all four questions, in order. Record the answer — it goes in the report.
Keyboard-initiated actions (command palettes, shortcuts, focus jumps) are a disqualifier, not a judgment call — repeated hundreds of times a day, animation makes them feel slow, delayed, and disconnected. Raycast has no open/close animation; that is the optimal experience.
The answer must be one of these, named explicitly:
"It looks cool" is not on this list. If you can't name the purpose in one of these words, reject the candidate.
The suggestion must work within the standard budgets (UI under 300ms; modals, drawers, sheets, and toasts are the documented exceptions):
If the moment only "works" as a slow, showy animation, it fails the gate.
Decoration on functional, information-dense UI hinders. A decorative mouse-tracking effect is fine on a marketing page; on a functional graph in a banking app, no animation is better. Data the user is trying to read or act on should not move for style.
Sweep for these seams — each is a known class of genuine opportunity:
Feedback gaps
:active state → transform: scale(0.97) with transition: transform 160ms var(--ease-out) (subtle: 0.95–0.98)clip-path: inset(0 100% 0 0) overlay, 2s linear on press, 200ms var(--ease-out) snap-back on releaseTeleporting state
scale(0.95–0.97) + opacity: 0, ease-out, never scale(0); @starting-style for entry without JSMissing spatial story
transform-origin at the trigger (Base UI: var(--transform-origin)); modals are exempt — they stay centeredGroup entrances
../choreograph/SKILL.md); decorative, must never block interactionGesture seams
{ type: "spring", duration: 0.5, bounce: 0.2 }, bounce 0.1–0.3), velocity-based dismissal (Math.abs(distance)/elapsedMs > ~0.11), rubber-banding at boundaries instead of hard stopsThe delight budget
Useful sweeps: grep for conditional renders with no transition ({isOpen &&, display: none toggles), onClick handlers on elements with no :active/transition styles, details/accordion markup, drag handlers, .map( renders of entering lists, empty-state and success components.
file:line evidence or been explicitly cleared.One row per surviving suggestion, ordered by leverage:
Every "Suggested motion" cell carries exact values — the curve, the duration, the properties — pulled from these tokens (--ease-out: cubic-bezier(0.23, 1, 0.32, 1), --ease-in-out: cubic-bezier(0.77, 0, 0.175, 1), --ease-drawer: cubic-bezier(0.32, 0.72, 0, 1)), never approximated. Prefer transform and opacity; clip-path (hold-to-confirm) and measured height (accordions) are the documented exceptions; include reduced-motion handling (gentler, not zero) and @media (hover: hover) and (pointer: fine) gating when the suggestion involves hover.
List up to 5 places you considered and deliberately did not suggest, each with the gate question that killed it. If you rejected none, say so:
CommandMenu.tsx:12 — command palette open/close. Rejected: keyboard-initiated, 100+/day. Never animate.Chart.tsx:88 — animated line drawing on the analytics graph. Rejected: functional data the user is reading; decoration hinders.This section is what separates this skill from an animation wishlist.
One short paragraph: how much motion this interface actually needs, whether it's already close to right, and which single suggestion has the highest leverage. Close by pointing at the handoff: improve-animations plan <suggestion> to turn any row into a self-contained implementation plan.
When feel can't be judged from code alone, say so instead of guessing. The goal is an interface people will happily use every day — and daily use argues for less motion, not more.
© 2026 Skills Rack.
---name: find-animation-opportunitiesdescription: Search a codebase or UI for places that don't animate but should, and reject everything that shouldn't…---# skills/find-animation-opportunities/SKILL.mdOverview
Search a codebase or UI for places that don't animate but should, and reject everything that shouldn't. Read-only; it proposes motion with exact values, it does not implement it. Use when the user asks "what could be animated here?" or wants to "make this feel more alive". For fixing existing animations, use improve-animations or review-animations instead.
FAQ
Download skills/find-animation-opportunities/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/emilkowalski/skills.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.