agentleFS
frankxaifrankxai/awesome-motion-design-agent-skills/skills/web-motion-auditor/SKILL.md

web-motion-auditor

Skill111 starsChanged 11 days agoCC0-1.0View on GitHub

Use when reviewing web animations, UI transitions, scroll effects, hover states, loading states, GIF/video captures, reduced-motion support, animation performance, or motion polish in HTML, React, Next.js, or Vercel apps.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    no motion that blocks reading or interaction

    line 15
  2. Distinctive:

    Check performance on desktop and mobile widths.

    line 16
  3. Distinctive:

    Use the bundled motion quality rubric, citing evidence per scored category.

    line 18
  4. Distinctive:

    Use transforms/opacity instead of layout-heavy properties.

    line 24

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Web Motion Auditor

Workflow

  1. Identify the exact revision and target URL. Reuse a qualified preview; run a local app only within the environment's resource and ownership rules.
  2. Inspect the animated states: load, hover, focus, click, route transition, scroll, empty/loading/success/error.
  3. Check accessibility:
    • prefers-reduced-motion
    • focus visibility
    • no motion that blocks reading or interaction
  4. Check performance on desktop and mobile widths.
  5. Capture screenshots/video when possible.
  6. Use the bundled motion quality rubric, citing evidence per scored category. Leave unobserved categories unscored.
  7. Return concrete fixes with file references.

Common Fixes

  • Shorten transitions.
  • Use transforms/opacity instead of layout-heavy properties.
  • Reduce stagger count.
  • Add reduced-motion branch.
  • Replace decorative motion with state-explaining motion.
  • Move complex narrative motion to Remotion or a controlled hero scene.

Required probes

ProbeObserve
KeyboardVisible focus, logical order, Escape/close behavior, no delayed command response
TouchEvery action available without hover; scrolling and taps remain usable
Reduced motionContent, hierarchy, and state remain clear; large movement has a designed alternative
InterruptionOpen then close mid-transition; repeat rapidly; verify the latest state, focus, and cleanup
Navigation and resizeNo orphan overlays, pinned scroll, duplicate listeners, or stale transforms
FailureFailed media or unavailable JavaScript preserves required content and controls
PerformanceMeasure on the target environment; separate traces, frame captures, and subjective observations

Report

Return severity, reproduction steps, file/line, fix, and verification evidence for each finding. Compare before and after in a table when reviewing a patch. Include revision, URL, viewport, input mode, and motion preference. Label missing checks explicitly; a still screenshot cannot prove frame rate or interruption behavior.

This is a review workflow, not a scanner or browser installation. If browser access is unavailable, complete the source review and report runtime checks as pending. Do not invent observations or start other agents or services without authorization.

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.