motion-runtime-guard
Skill4 starsChanged 31 days agoMITView on GitHub
Validate runtime motion performance, long tasks, audio autoplay safety, and reduced-motion parity under DPR-2 retina conditions (1440x900@2x = 5.2MP) with 4x CPU throttling, filtering dev-server false failures.
In this repository47 other files it gives its agents.
- AGENTS.mdAGENTS.md
- anti-slop-engineeringSkill
- anti-slop-engineeringSkill
- api-ergonomics-and-contract-governorSkill
- apple-craft-and-frame-budgetSkill
- apple-craft-and-interaction-physicsSkill
- asset-provenance-guardSkill
- backprop-guardSkill
- chaos-and-degradation-choreographerSkill
- chromatic-drift-guardSkill
- cognitive-load-and-attention-governorSkill
- comment-budget-guardSkill
- context-window-and-token-economics-architectSkill
- cryptographic-agility-and-secret-lifecycle-gateSkill
- decision-guardSkill
- demock-guardSkill
- design-system-drift-guardSkill
- deterministic-simulation-and-property-testingSkill
- distributed-consensus-and-concurrency-gateSkill
- finops-and-unit-economics-governorSkill
- future-scale-gateSkill
- grumpy-senior-staff-engineerSkill
- honeypot-trap-guardSkill
- house-tell-guardSkill
- install-anti-slopSkill
- llm-eval-and-prompt-injection-fortressSkill
- mandela-guardSkill
- mechanical-sympathy-and-perf-gateSkill
- mechanical-sympathy-profilerSkill
- observability-and-slo-architectSkill
- observability-and-slo-gateSkill
- paranoid-principal-architectSkill
- pr-boundary-guardSkill
- privacy-and-data-lineage-gateSkill
- re0-handoff-guardSkill
- reduction-guardSkill
- repo-memory-and-invariant-stewardSkill
- root-fix-gateSkill
- safe-evolution-and-rollout-choreographerSkill
- scientific-fault-isolationSkill
- styleseed-guardSkill
- supply-chain-and-sbom-sentinelSkill
- tagore-guardSkill
- type-level-and-ast-slop-gateSkill
- ui-and-copy-disciplineSkill
- verification-oracle-architectSkill
- zero-downtime-migration-gateSkill
The file
Files
DPR-2 Runtime Motion & Fillrate Sentry
Enforce honest runtime performance measurement under retina display conditions (5.2MP) with 4x CPU throttling, long-task bounding, audio autoplay gesture gating, and dev-server false-positive filtering.
Why This Skill Is Needed & Target State
Static linters and frozen screenshots are blind to time:
- Fillrate-Aware Motion Pricing: Fullscreen post-processing passes (bloom, grain, depth of field, full-frame shaders) cost per pixel, not per geometry. Measuring at DPR 1 quarters the pixel fillrate cost and reports 60 FPS for a scene that stutters on a retina laptop (5.2MP at DPR 2).
- Dev-Server False Failures: Dev servers (Vite HMR, Webpack hot updates, Next.js dev bundles) cost roughly $2\times$ per frame, triggering false failures that cause developers to needlessly butcher performant production scenes.
- Long Tasks & Audio Autoplay: Unbounded JavaScript blocks the main thread, while unmuted autoplaying media violates user experience standards.
The target state is honest SRE measurement: evaluating production builds at DPR 2 with 4x CPU throttling, bounding long tasks ($LT \le 50\text{ms}$), locking audio behind explicit user gestures, and verifying prefers-reduced-motion art-direction parity.
Invariant Rules
- Retina Resolution Mandate: Motion performance benchmarks must be conducted at $\text{DPR} \ge 2.0$ ($1440 \times 900 \times 2 = 5.184\text{MP}$) with 4x CPU throttling.
- FPS & Long-Task Bounds: Minimum acceptable frame rate is $\ge 50$ FPS; maximum individual long task is $\le 50\text{ms}$.
- Gesture-Initiated Audio: Audio and video elements must remain silent/muted on initial load; sound starts exclusively upon an explicit user interaction.
- Reduced-Motion Alternative Art Direction: Reduced-motion branches must provide an intentional alternative composition (calm stills, rich editorial cuts), never blank scenes or broken layouts.
- Dev-Server Discrimination: Flag and isolate dev-server measurements to prevent optimizing already-efficient scenes.
CLI Usage
# Validate pre-recorded runtime motion report
bunx anti-slop-engineering motion-runtime --file .anti-slop/motion-report.json
# Check inline performance metrics under DPR 2
bunx anti-slop-engineering motion-runtime --fps 58.5 --dpr 2.0 --longtask 24.0 --json
# Enforce strict zero-warning exit code
bunx anti-slop-engineering motion-runtime --file runtime.json --strictDoes 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.

