What problem does it solve? Animations get rebuilt repeatedly because nobody decided what the motion was for before writing code. This Skill front-loads that decision by interviewing the user one question at a time until every aspect of an animation — trigger, purpose, easing, duration, interruption behavior, reduced-motion fallback — is settled in a written brief. ## Core Features & Use Cases - Structured interview workflow: Asks one question at a time with a recommended answer for each, covering frequency, purpose, choreography, feel, and edge cases. - Codebase recon first: Reads the component, trigger, animation stack (motion/react, Tailwind, CSS, WAAPI), and existing easing tokens before asking anything, so questions are grounded in the actual code. - Cut-friendly outcomes: Can conclude that an animation should not exist at all (e.g., keyboard-triggered or seen 100+ times per day) and records that as a valid brief. - Use Case: A drawer component has been rebuilt three times and still feels wrong. Run this Skill to decide its enter/exit properties, origin, spring vs. transition behavior, and reduced-motion fallback before touching code again. ## Quick Start Ask the assistant to grill you on how the drawer component should animate and produce a motion brief before writing any code.
