agentleFS
Sign inStart free
sukirman1901sukirman1901/frontend-expert/skills/motion-inspection/SKILL.md

motion-inspection

Skill9 starsChanged 2 months agoMITView on GitHub

Inspect rendered UI motion frame by frame: start, mid, end, interrupt, and reduced-motion. Reverse-engineer unnamed animation into families/patterns from motion-families.md. Trigger for “inspeksi animasi”, “frame by frame”, “kenapa animasinya aneh”, “jelaskan transisi”, or reverse-engineer motion. Implementing new motion stays on motion; decorative spam stays on anti-slop-design.

The file

Create a free account to mount
Files
SKILL.md

Motion Inspection

Overview

Source duration is not proof. Play the animation (or mark Not verified). Name what it actually does at start / mid / end, whether it can be interrupted, and whether reduced-motion was observed. Then map it to catalog families/patterns.

When to use

  • Explain, debug, or audit existing transitions
  • “Kenapa animasinya aneh” / frame-by-frame / reverse-engineer motion
  • /design on animated UI when claims depend on how it plays
  • Naming a mystery transition before changing it

When to skip

  • Implementing new motion from a named pattern → motion
  • Decorative stack / motion spam as a visual tell → anti-slop-design (then inspect leftovers here)
  • Press-scale / duration heuristics on a new control → polish + motion
  • Comparing layout directions → prototype
  • WCAG classification of the target → accessibility

MUST

RuleDetail
RenderedPlay or step the motion; do not pass from CSS/transition text alone
Not verifiedIf it was not played, say so — never “smooth” / “perfect”
BeatsRecord start, mid, end, interrupt (click/focus/route away), reduced-motion
Name itMap to ≤2 families and named patterns in motion-families.md
MeaningIf the only cue is motion, that is a defect — hand copy/a11y owners
Fix via motionInspection does not ship a new stack; implementation follows motion

Workflow

  1. Scope — which transition, trigger, and viewport.
  2. Play — full run, mid-interrupt, reduced-motion (or Not verified).
  3. Name — family/pattern from the catalog; flag unnamed one-offs.
  4. Budget — count intentional motions in the viewport (≤2–3 is the pack default).
  5. Handoff — spam → anti-slop-design; implement/fix → motion; conformance → accessibility.

Boundaries

  • May decide: whether a shell default is enough vs a named marketing pattern.
  • Must not: invent pattern names, claim scores without playback, or replace motion with a registry install.

Checklist

  • Playback (or Not verified) for start / mid / end
  • Interrupt and reduced-motion checked or labeled
  • Families/patterns named from the catalog
  • Viewport motion budget noted
  • Fixes routed to motion / anti-slop-design / accessibility

Depth

Inspection protocol: references/motion-inspection.md. Vocabulary: references/motion-families.md. Implementation: skills/motion/SKILL.md.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free