review-animations

Reviews animation and motion code against easing, duration, performance, and accessibility standards.

Updated Jul 30, 2026
One-click install
npx skills add https://github.com/j172/bid --skill review-animations-j172
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-animations
Source: https://github.com/j172/bid/tree/main/agent/skills/review-animations
Command: npx skills add https://github.com/j172/bid --skill review-animations-j172

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Animation code often ships with subtle craft defects — sluggish easing, wrong transform origins, non-GPU properties, missing reduced-motion handling — that make interfaces feel slow or broken even when they technically work. This Skill reviews motion code against a strict, opinionated standards bar so these issues are caught before merge. ## Core Features & Use Cases - Standards-based review: Evaluates every animation against ten non-negotiable rules covering easing curves, sub-300ms durations, transform origins, interruptibility, GPU-only properties, and accessibility. - Structured findings output: Produces a Before/After/Why findings table plus a tiered verdict (feel-breaking regressions, performance, timing, accessibility) ending in an explicit Block or Approve decision. - Precise citations: Pulls exact cubic-bezier curves, duration budgets, and spring configs from STANDARDS.md instead of approximating values. - Use Case: A pull request adds a dropdown that animates with transition: all 400ms ease-in from scale(0). The review flags the unbounded transition, the ease-in curve, the over-budget duration, and the wrong origin, then prescribes transform 200ms with a strong ease-out from scale(0.95) anchored to the trigger. ## Quick Start Review the animation and motion code in this pull request and give me a findings table with a block or approve verdict.

Frequently Asked Questions about review-animations

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review CSS animation code for quality issues?

Check each animation against concrete rules: ease-out for entering elements, durations under 300ms for UI, transform and opacity only, correct transform-origin, and prefers-reduced-motion handling. This Skill automates that review and outputs a findings table with a block or approve verdict.

What animation issues should block a pull request?

Block on feel-breaking regressions: ease-in on UI, scale(0) entrances, animation on keyboard or high-frequency actions, durations over 300ms without justification, and non-GPU property animation with an easy transform-based fix.

Does Framer Motion x/y/scale cause performance problems?

Yes. Framer Motion x, y, and scale shorthands run on the main thread via requestAnimationFrame and drop frames under load. Use the full transform string, such as transform: translateX(100px), to get hardware acceleration.

When should I use CSS transitions versus keyframes for animations?

Use transitions for anything triggered rapidly or interruptibly, like toasts and toggles, because transitions retarget from current state. Keyframes restart from zero when retriggered, so reserve them for predetermined one-shot motion.

How should animations handle prefers-reduced-motion?

Reduced motion means gentler animation, not zero. Keep opacity and color transitions that aid comprehension, but drop transform-based movement. Gate hover motion behind @media (hover: hover) and (pointer: fine) to avoid false triggers on touch.

What are the limitations of this animation review approach?

It only reviews motion code and declines general code review requests. Judgments about whether motion feels right may still require slow-motion or frame-by-frame inspection in DevTools, since some cohesion issues cannot be settled from code alone.