Emil Kowalski's craft bar for interface work - the taste layer that stops an agent shipping generic motion.
The complete design-engineering skill set from Emil Kowalski, creator of Sonner and Vaul and previously of Vercel and Linear. Eight skills that give an agent real motion taste: Apple's fluid-interface physics translated for the web, a strict animation review bar, a codebase-wide motion audit that produces executable plans, an opportunity finder that is built to say no, a reverse-lookup vocabulary so you can name the effect you want, an opinionated library picker, and a variant prototyper. Mirrored from Emil's open-source repo under MIT with his license intact. Every skill in this pack was audited before listing - claims verified against primary sources, npm specifiers re-checked, and each deviation from the original disclosed in the skill body.
Arranged in the author's recommended order. Walk through them in sequence, or open any one on its own.
Use when building or reviewing gesture-driven web UI that must feel physical – drag/swipe/sheet interactions, spring damping and response, velocity handoff at release, momentum projection, interruptible transitions, translucent materials.
Use when writing or reviewing web animation code – easing curves, durations, whether to animate at all, springs versus CSS transitions, swipe and drag dismissal, transform-origin on popovers, @starting-style, clip-path reveals, stagger.
Review already-written animation or motion code against a strict craft bar and return a findings table plus a block or approve verdict.
Use when someone asks to "improve the animations", "audit the motion in this codebase", "make this app feel better", "why does our UI feel janky", or wants a prioritized roadmap of animation fixes.
Search a codebase or UI for places that do not animate but should, and reject everything that should not. Read-only – it proposes motion with exact values, it does not implement it.
Reverse-lookup glossary that turns a vague description of a web animation or motion effect into its exact term ("the bouncy thing when a popover opens" becomes Pop in; "the iOS rubber-band scroll" becomes Rubber-banding).
Use when someone asks "what should I use for toasts / drag and drop / a command menu / a big list / animating a number", or is about to hand-roll a UI primitive that a good package already solves.
Use when someone says "give me three versions of this pricing card", "build a few takes on the empty state and let me flip through them", or "prototype some variations of this button".