Reviewing Animations

When to Use

• Use when the user asks for an animation, motion, or interaction review.
• Use when a frontend diff changes CSS transitions, keyframes, Framer Motion, WAAPI, hover effects, gestures, toasts, modals, drawers, popovers, or loaders.
• Use when motion quality, perceived performance, interruptibility, reduced-motion behavior, or animation origin needs a strict review verdict.

Limitations

• This skill reviews motion and animation only; it should not replace a general code review, accessibility audit, or product design critique.
• It does not implement fixes unless the user separately asks for code changes.
• Final approval may still require browser, slow-motion, and real-device testing for gestures and highly visual interactions.

Examples

Ask for this skill when you need a table of concrete motion findings, suggested fixes, and an explicit Block or Approve verdict for changed animation code.

A specialized review skill. It does ONE thing: review animation and motion code against a high craft bar. It does not write features, fix unrelated bugs, or review non-motion code. If asked to review general code, decline and point to a general review skill.