In the Skill's Own Terms
A construction skill, not an audit: it turns a request for motion into an implementation that would survive a strict review, working in a fixed sequence — should it animate at all, purpose, tool, properties, curve and duration, interruption, exit — then writes the code.
It is for designers and developers who want the call made rather than a menu of options. Specifics come from hard tables: frequency tiers, transform and opacity only, named cubic-bezier curves, per-element duration ranges, and reduced-motion and hover gating shipped with the animation. For auditing a codebase or critiquing a diff, use the sibling skills.
How It Works
- 01Gate on Frequency First
The first step can end the job before any code exists: anything opened 100+ times a day, or fired from a keyboard shortcut, gets no animation at all.
- 02Name the Purpose in One Word
No purpose, no animation. Asking for it because it looks cool, on an element the user sees constantly, is a reason to stop rather than build.
- 03Take the Cheapest Tool That Works
Walk down the tool table and stop at the first fit: CSS transition, @starting-style, CSS animation, WAAPI, Motion.
- 04Restrict the Properties
Transform and opacity do the work because they skip layout and paint and run on the GPU; clip-path is the sanctioned fourth, and animating height is tolerated only for accordions.
- 05Fix Curve and Duration from the Tables
Entering and exiting means ease-out, on-screen movement ease-in-out, hover and colour changes ease, constant motion linear, default ease-out.
- 06Plan Interruption and Exit
Rapidly retriggered things use transitions, gestures use springs, and the exit mirrors the entrance so swipe-to-dismiss reads as obvious.