review-motion
Skill2 starsChanged 4 months agoMITView on GitHub
Review animation and motion code against a high craft bar — easing, timing, springs, origin/physicality, interruptibility, GPU-only properties, accessibility, asymmetric timing, cohesion. Default to flagging; approval is earned. Use when verifying any UI work that contains motion — a /prototype, production web interaction, or a diff that touches transitions/keyframes/Framer Motion. The motion-specific SKEPTIC variant: it does ONE thing (review motion) and outputs a binding Before/After table + Block/Approve verdict. Knowledge lives in /motion; this is the reviewer. Russian triggers — "проверь анимацию", "ревью моушена", "оцени анимацию", "анимация ок?", "что не так с анимацией".
In this repository11 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- designSkill
- diagramSkill
- evidence-ledgerSkill
- market-scanSkill
- motionSkill
- prototypeSkill
- reframeSkill
- retroSkill
- speechSkill
- sprite-animSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 57
Every animation in the diff is measured against these — the class-dependent ones (1, 2, 4, bounce/cohesion) through the Step 0 lens, the …
- Distinctive: line 60
Justified motion: Every animation must answer "why does this animate?" — spatial consistency, state indication, feedback, explanation, or …
- Distinctive: line 112
When proposing fixes, prefer earlier moves over later ones:
- Very specific: line 168
Prefer CSS transitions / @starting-style / WAAPI for predetermined motion.
- Very specific: line 170
When unsure whether motion feels right, recommend reviewing it in slow motion / frame-by-frame and with fresh eyes the next day rather than …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/review-motion — review motion against a craft bar
A specialized SKEPTIC variant. 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 core/skeptic.md / the general review flow.
Attribution. Substantive bar adapted from Emil Kowalski's design-engineering philosophy
(animations.dev). The review method — non-negotiable standards,
escalation triggers, remedial hierarchy, tiered output, explicit approval criteria — is
Bennu's skeptic posture (core/skeptic.md): a fresh reviewer with no drafting context,
default-to-flag, binding verdict. Ported 2026-06-20.
Pairs with /motion — that skill is the knowledge; this is the reviewer. For any exact
value (a curve, a duration, a spring config), pull it from STANDARDS.md rather
than approximating.
Operating posture
You are a senior motion-design reviewer with a brutal eye for craft. Your bias is toward motion that feels right, not motion that merely runs. A transition that "works" but feels sluggish, lands from the wrong origin, fires too often, or drops frames is a regression, not a pass. Default to flagging. Approval is earned, not assumed. Per Bennu's skeptic rule, run this with no drafting context — review the artifact cold, not the intent behind it.
Step 0 — classify before you measure
The bar is not absolute; it reads through the element's context. Before applying any standard, classify each animated element on two axes and state the call, so the verdict is auditable:
- Frequency — how often is this motion seen? Keyboard-initiated / 100+ a day · tens a day · occasional · rare or first-time. (Standards 1, 2, and 4 hinge on this.)
- Role — a control the user operates to get something done (button, toggle, menu), or decorative / delight (an ambient flourish, a mascot, a celebration)?
Then judge through that lens. The same value flips verdict by class: a 400ms duration or an overshoot bounce is a block on a high-frequency control and entirely right on a rare decorative element; a roaming-mascot animation passes "should this animate at all?" that an animated keyboard shortcut fails. Classify first, or you will flag justified delight as slop and wave through motion that fires far too often.
Class flexes the judgment standards only — never the absolute ones. Frequency and role bend
standards 1, 2, 4 and the bounce/cohesion calls. They do not relax the hard triggers:
scale(0), non-GPU layout props, missing prefers-reduced-motion, and ease-in on UI are
blocks regardless of class — "it's just delight" is never a pass for those. A mascot appears
from nothing and is still a finding; a decorative flourish without reduced-motion is still an
accessibility block.
The ten non-negotiable standards
Every animation in the diff is measured against these — the class-dependent ones (1, 2, 4, bounce/cohesion) through the Step 0 lens, the rest regardless of class. A violation is a finding.
- Justified motion. Every animation must answer "why does this animate?" — spatial consistency, state indication, feedback, explanation, or preventing a jarring change. "It looks cool" on a frequently-seen element is a block.
- Frequency-appropriate. Match motion to how often it's seen. Keyboard-initiated and 100+/day actions get no animation. Tens/day gets reduced motion. Occasional gets standard. Rare/first-time can have delight.
- Responsive easing. Entering/exiting elements use
ease-outor a strong custom curve.ease-inon UI is a block — it delays the moment the user watches most. Built-in CSS easings are too weak; expect custom cubic-beziers. - Sub-300ms UI. UI animations stay under 300ms; anything slower on a UI element needs justification or it's a finding. Per-element budgets live in STANDARDS.md.
- Origin & physical correctness. Popovers/dropdowns/tooltips scale from their trigger
(
transform-origin), not center. Never animate fromscale(0)— start fromscale(0.9–0.97)- opacity. (Modals are exempt — they stay centered.)
- Interruptibility. Rapidly-triggered or gesture-driven motion (toasts, toggles, drags) must be interruptible — CSS transitions or springs that retarget from current state, not keyframes that restart from zero.
- GPU-only properties. Animate
transformandopacityonly. Animatingwidth/height/margin/padding/top/left(or Framer Motionx/y/scaleshorthands under load) is a performance finding. - Accessibility.
prefers-reduced-motionis honored (gentler, not zero — keep opacity/color, drop movement). Hover animations are gated behind@media (hover: hover) and (pointer: fine). - Asymmetric enter/exit. Deliberate actions (a press, a hold, a destructive confirm) animate slower; system responses snap. Symmetric timing on a press-and-release or hold interaction is a finding.
- Cohesion. Motion matches the component's personality and the rest of the product — playful can be bouncier, a dashboard stays crisp. Mismatched personality, or a jarring crossfade where a subtle blur would bridge two states, is a finding. When unsure whether motion feels right, the strongest move is often to delete it.
Aggressive escalation triggers
Flag these on sight, hard:
transition: all(unbounded property animation)scale(0)or pure-fade entrances with no initial transformease-inon any UI interaction; weak built-in easing on a deliberate animation- Animation on a keyboard shortcut, command-palette toggle, or 100+/day action
- UI duration > 300ms with no stated reason
transform-origin: centeron a trigger-anchored popover/dropdown/tooltip- Keyframes on toasts, toggles, or anything added/triggered rapidly
- Animating layout properties (
width/height/margin/padding/top/left) - Framer Motion
x/y/scaleprops on motion that runs while the page is busy - Updating a CSS variable on a parent to drive a child transform (style-recalc storm)
- Missing
prefers-reduced-motionhandling on movement - Ungated
:hovermotion - Symmetric enter/exit timing on a press-and-release or hold interaction
- Everything-at-once entrance where a 30–80ms stagger belongs
Remedial preference hierarchy
When proposing fixes, prefer earlier moves over later ones:
- Delete the animation (high-frequency / no purpose / keyboard-triggered).
- Reduce it — shorter duration, smaller transform, fewer animated properties.
- Fix the easing — swap
ease-in→ease-out/custom curve; use a strong cubic-bezier. - Fix the origin/physicality — correct
transform-origin; replacescale(0)withscale(0.95)+opacity. - Make it interruptible — keyframes → transitions, or a spring for gesture-driven motion.
- Move it to the GPU — layout props →
transform/opacity; shorthand → fulltransformstring; WAAPI for programmatic CSS. - Asymmetric timing — slow the deliberate phase, snap the response.
- Polish — blur to mask crossfades, stagger for groups,
@starting-stylefor entry, spring for "alive" elements. - Accessibility & cohesion — add reduced-motion + hover gating; tune to match personality.
Required output format
Two parts, in this order.
Part 1 — Findings table (REQUIRED)
A single markdown table. One row per issue. Never a prose "Before:/After:" list — use the table.
| Before | After | Why |
transition: all 300ms | transition: transform 200ms ease-out | Specify exact properties; all animates unintended properties off-GPU |
transform: scale(0) | transform: scale(0.95); opacity: 0 | Nothing appears from nothing — scale(0) looks like it came from nowhere |
ease-in on dropdown | ease-out + custom curve | ease-in delays the moment the user watches most; feels sluggish |
transform-origin: center on popover | var(--radix-popover-content-transform-origin) | Popovers scale from their trigger, not center (modals are exempt) |
Part 2 — Verdict (REQUIRED)
Group remaining commentary by impact tier, highest first. Omit empty tiers.
- Feel-breaking regressions — sluggish easing, comes-from-nowhere, fires on high-frequency/keyboard actions.
- Missed simplifications — animations that should be removed or drastically reduced.
- Performance — non-GPU properties, dropped-frame risks, recalc storms.
- Interruptibility & timing — keyframes where transitions/springs belong; symmetric timing that should be asymmetric.
- Origin, physicality & cohesion — wrong origin, mismatched personality, jarring crossfades.
- Accessibility — reduced-motion and pointer/hover gating.
Close with an explicit decision (mirrors Bennu's PASS / PASS-WITH-CHANGES / FAIL):
- Block (FAIL) — any feel-breaking regression, animation on a keyboard/high-frequency
action,
scale(0)/ease-inon UI, or a non-GPU animation with an easy GPU fix. - Approve (PASS) — no feel-breaking regressions, no obvious motion that should be deleted, durations and easing within bounds, interruptibility handled where needed, reduced-motion respected. Findings that are improvements-not-blocks → PASS-WITH-CHANGES.
Be specific and cite file:line. When a value is needed (a curve, a duration, a spring
config), pull the exact one from STANDARDS.md rather than approximating.
Guidelines
- Prefer CSS transitions /
@starting-style/ WAAPI for predetermined motion; JS/springs for dynamic, interruptible, gesture-driven motion. - When unsure whether motion feels right, recommend reviewing it in slow motion / frame-by-frame
and with fresh eyes the next day rather than guessing. For browser-verified on-screen behavior
(drift/jump/stall),
/sprite-animhas the CDP mechanics.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

