animation-jump-check
Skill9 starsChanged yesterdayMITView on GitHub
Check a page's animations frame by frame for what a screenshot cannot show. Elements that snap instead of gliding, neighbours moving out of step, and open popovers that lose their anchor. Runs scripts/check-animation-jumps.mjs, judges each finding by watching the motion, and reports. Use when asked to check an animation for jumps, find a pop or snap in some motion, or run the animation jump check. Never fixes, commits, pushes, or deploys.
In this repository38 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- accessibility-auditSkill
- api-consistencySkill
- chat-qualitySkill
- checkpointSkill
- component-consistency-auditSkill
- component-doc-pageSkill
- content-auditSkill
- dependency-advisorySkill
- design-qaSkill
- dogfoodSkill
- drift-auditSkill
- figma-paritySkill
- figma-tokensSkill
- first-deploySkill
- landSkill
- link-rotSkill
- new-backgroundSkill
- new-componentSkill
- new-figma-componentSkill
- new-figma-templateSkill
- new-pageSkill
- new-presetSkill
- new-templateSkill
- new-tokenSkill
- new-validatorSkill
- parkSkill
- pre-deploySkill
- release-postSkill
- releaseSkill
- responsive-sweepSkill
- security-auditSkill
- seo-auditSkill
- shipSkill
- super-shipSkill
- token-auditSkill
- token-renameSkill
- visual-reviewSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Report only: Do not fix, commit, push, or deploy unless separately asked.
- Very specific: line 25
Prefer the production build, since a dev server adds its own stalls and reloads.
- Distinctive: line 57
Never raise a threshold to make a run quieter without the owner's yes.
≈ “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
animation-jump-check
design-qa judges animations after they settle, and the served-site checks do not look at motion, so a one-frame snap reaches no check. scripts/check-animation-jumps.mjs records every element's box on every frame of a page. This skill points it at the motion in question and judges what it finds. The script's doc block owns what each line means, what it skips, its options and its exit codes.
Report only. Do not fix, commit, push, or deploy unless separately asked.
Instructions
1. Decide what to record
Name the route and what sets the motion off. An entrance plays on load; anything else needs --click or --hover to start it. Use --select for the part of the page that moves: a smaller recording stalls less and reports less noise. Set --ms long enough to cover the whole animation.
2. Run it
Prefer the production build, since a dev server adds its own stalls and reloads. With no --origin, the script boots the existing build, so confirm that build is of the tree under review. Keep output in the session's scratchpad.
node scripts/check-animation-jumps.mjs /some-route --select ".some-root" --click ".some-trigger" --json <scratchpad>/jumps.jsonExit 2 means the recording cannot be trusted, usually because too many frames stalled. Narrow --select and run again; never read an incomplete run as clean. Run the same recording twice before believing a single-frame finding, because headless timing varies.
3. Judge every finding by watching it
Step through the moment the line names, using the built-in browser or Playwright with the animation slowed down. Give each finding one verdict:
- Defect: a person would see it pop, or two things visibly part ways.
- By design: the motion is meant to step. Cite the code or design.md spec that says so.
- Instrument error: nothing visible happens, for example a change under something opaque, or a page layout shift unrelated to the animation.
manual lines are not findings. Look at them only when the swap is part of the motion in question.
4. Report
Repeat the full report in the final message; there is no report file.
- What was recorded: route, trigger, width, frames, and the share stalled.
- Defects: each with its time, the element, what is seen, and the likely cause in the source.
- By design and instrument errors: one line each.
- What it could not see: colour and opacity changes, easing that is smooth but wrong, and every state not triggered.
"No jumps" is a valid outcome, and it means no measurable snap in what was recorded, not that the motion is good.
Guardrails
- Propose
data-snaprather than adding it, and only for an element whose stepping is deliberate. It hides that element from the check for good. - Never raise a threshold to make a run quieter without the owner's yes.
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.

