What problem does it solve? Teams struggle to name animation effects, decide when motion is appropriate, and implement animations that feel physical rather than decorative, often shipping stuttering layout animations or endless loops. ## Core Features & Use Cases - Effect Naming: Reverse-lookup table maps plain descriptions ("bouncy thing when a popover opens") to named effects like pop-in, rubber-banding, and stagger. - Decision Framework: Ordered questions determine whether an interaction deserves motion based on frequency, visibility, and purpose before any code is written. - Build & Review Guidance: Concrete rules for properties (transform/opacity only), curves, durations, interruption, exits, and reduced-motion support, plus audit checklists for existing codebases. - Use Case: When asked to "make this UI feel alive," the skill audits the screen, flags decorative loops for removal, and specifies exact spring values for the interactions that genuinely need feedback. ## Quick Start Ask the agent to review the animations on this page and suggest which ones to keep, fix, or remove.