What problem does it solve? Frontend animation often ships with wrong easing, excessive frequency, performance problems, or missing accessibility handling, and teams lack a structured way to decide when motion is justified and how to implement or review it consistently. ## Core Features & Use Cases - Three operating modes: Build mode implements animations with the cheapest suitable tool (CSS transitions, WAAPI, or the existing motion library); Review mode inspects motion diffs with file:line evidence and a Block/Approve verdict; Audit mode maps the entire motion surface and produces prioritized findings and self-contained improvement plans. - Standards and recipes: Bundled references provide easing curves, duration ranges, physicality rules, reduced-motion patterns, and ready-made recipes for buttons, modals, drawers, toasts, accordions, staggers, and drag gestures. - Use Case: A developer is asked to review a pull request that adds a modal transition. The skill checks purpose and frequency, verifies easing and duration against project tokens, confirms reduced-motion handling, and returns a verdict table citing exact file:line evidence. ## Quick Start Ask the assistant to review the animation code in your current diff for easing, performance, and accessibility issues using the frontend motion review workflow.
