Animate turns a request for motion into a working implementation. It starts by asking whether the element should animate at all, names the purpose, picks the cheapest tool that works, and then chooses properties, easing, duration, interruption behavior and exit. It follows Emil Kowalski’s animation philosophy and ships reduced-motion and hover gating with the animation. A RECIPES.md file beside it holds tested patterns such as clip-path reveals.
What You Get
- A working animation in CSS, WAAPI or Motion, matched to the codebase’s own tokens
- A one-line statement of the purpose and the reasoning behind each choice
- Reduced-motion and hover-gating handling included in the code
- A recipes file with ready patterns
Common Use Cases
- Adding an enter and exit animation to a modal, drawer or toast
- Giving a button, card or menu a press or hover transition
- Building a transition between two states of a component
What Makes It Unique
Most animation prompts start from a curve. This skill starts from whether the element should move at all, and a keyboard-triggered action is a disqualifier that stops the run with zero lines of animation. Every curve and duration comes from the codebase tokens or from fixed tables, so output stays consistent with the companion review-animations skill that enforces the same bar.
Under The Hood
A single SKILL.md of instructions plus a RECIPES.md reference file. It runs no scripts and makes no network calls. On first use it replies with a one-line readiness message, then the model reads the codebase for existing animation tokens, walks the build sequence and edits the files that hold the component. When the request is for a whole component such as a toast or drawer, it sends the model to the pick-ui-library skill.