What problem does it solve? Deciding whether and how to animate a UI element is error-prone: wrong easings, sluggish durations, non-composited properties, and missing reduced-motion support make interfaces feel sluggish or inaccessible. This Skill turns a motion request into a reviewed implementation by walking a fixed decision sequence — gate, purpose, tool, properties, easing, interruption, accessibility. ## Core Features & Use Cases - Decision-gated construction: A frequency gate rejects animation for high-frequency or keyboard-triggered actions before any code is written, and a purpose check (feedback, spatial consistency, state indication) blocks decorative motion on functional UI. - Opinionated ingredient tables: Fixed easing tokens (cubic-bezier curves), duration ranges per component type, and spring configs eliminate guessed values, with rules like transform/opacity-only properties and transform-origin at the trigger. - Ready-to-build recipes: RECIPES.md provides implementations for button press, dropdown, tooltip, modal, drawer, toast, accordion, stagger, hold-to-confirm, tab indicator, scroll reveal, and drag-to-dismiss. - Use Case: Ask to animate a dropdown menu, and receive CSS with scale-from-trigger origin, a 200ms strong ease-out, starting/ending style states, hover gating, and a prefers-reduced-motion variant. ## Quick Start Ask the AI to animate a component, for example: add an entrance and exit animation to my modal dialog with a backdrop.