What problem does it solve? Deciding whether an element should animate, which tool to use, and which easing, duration, and properties to apply is error-prone, often producing sluggish or jarring motion. This Skill turns a motion request into a reviewed implementation by walking a fixed decision sequence before writing any code. ## Core Features & Use Cases - Gated build sequence: Decides first whether something should animate at all based on interaction frequency, then names its purpose before choosing tools, properties, curves, and durations. - Concrete implementation rules: Enforces transform/opacity-only animation, strong custom cubic-bezier curves, sub-300ms UI durations, spring configs for gestures, and mandatory reduced-motion and hover gating. - Ready-made recipes: Ships implementations for button presses, dropdowns, tooltips, modals, drawers, toasts, accordions, staggers, hold-to-confirm, tab indicators, scroll reveals, and drag-to-dismiss. - Use Case: Ask it to animate a dropdown menu, and it returns CSS using transform-origin anchored to the trigger, a 200ms strong ease-out curve, opacity plus scale(0.95) entry, and the matching prefers-reduced-motion fallback. ## Quick Start Ask the assistant to animate a component, for example: add an entrance and exit animation to my dropdown menu built with Base UI.