plugins/design-motion/skills/design-motion-audit/SKILL.md
Audit a repository, route, screen, component, or 3D scene for motion quality — design-token consistency, R3F/three.js polish, Reanimated native motion, interaction physicality, frame-rate/draw-call risk, reduced-motion coverage, accessibility, and missing hallmark-motion opportunities. Use when asked to audit, review, critique, find gaps, check performance, verify reduced motion, or assess whether UI animation feels premium. Returns a prioritized punch list. For building/implementing motion route to design-motion-system, expo-motion, web-three-r3f, r3f-scene-polish, or gsap.
npx skillsauth add bjornmelin/dev-skills design-motion-auditInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Audit the target surface (a repo, route, screen, component, or 3D scene) for
motion quality and implementation safety, and return a prioritized punch list
with exact files, severity, reasoning, and concrete fixes. This skill diagnoses;
it routes implementation to the owning skill (design-motion-system for
system/token work, expo-motion, web-three-r3f, r3f-scene-polish, or gsap).
Optionally run the static analyzers to gather leads (treat findings as leads, verify each against the real code before reporting):
python3 scripts/detect_motion_stack.py <project-root> --pretty # what stacks/files exist
python3 scripts/audit_motion_system.py <project-root> --pretty # heuristic motion-quality scan
Read the flagged files and judge against the dimensions below.
Return the punch list, most-severe first.
references/motion-vocabulary.md)setState in useFrame, missing delta-time,
per-frame allocations, disposal, DPR, shadows, postprocessing budget.runOnJS/runOnUI, worklet misuse, interruptibility, layout-vs-transform.references/performance-accessibility.md)Score against references/quality-gates.md, and shape the output with
references/report-template.md. For any change with a visible motion surface, add
runtime proof (references/runtime-verification.md) — static findings alone do
not prove a scene renders or holds its frame budget; the motion-runtime-verifier
subagent (design-motion plugin) drives that when the browser tools are available.
For deep implementation fixes, hand each finding to the skill that owns its stack.
development
Pre-PR multi-model review, parallel opus and codex exec adversarial lanes, then adversarial verification of merged findings. Read-only. Use before shipping nontrivial diffs.
tools
Independent gpt-5.6 diff review via the Codex CLI, normal or steerable adversarial with JSON findings. Use before shipping nontrivial changes.
development
Delegate implementation, investigation, or bulk work to gpt-5.6 codex via pinned codex exec. Use for clear-spec builds, migrations, debugging, or any task MODELS.md routes to codex.
development
Adversarial pre-mortem: imagine the plan failed, work backwards to surface risky assumptions + irreversible bets, then harden them. Proactively offer it (after the current request; confirm first) before a hard-to-reverse or one-way-door call (API, schema, framework, a hire), an all-upside plan, or unvalidated assumptions. Also on request.