agentleFS
TheGoat395TheGoat395/Codex-Skills/skills/animation-jank-qa/SKILL.md

animation-jank-qa

Skill136 starsChanged 5 months agoMITView on GitHub

Diagnose a concrete rendered hitch or stutter.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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:

    Use this skill for symptom-led runtime diagnosis.

    line 8
  2. Distinctive:

    Read Animation Jank QA Guide for relevant diagnosis and retesting steps.

    line 13
  3. Distinctive:

    Run the narrowest meaningful trace or rendered check for the symptom.

    line 14
  4. Distinctive:

    Do not claim something was tested unless it was actually tested.

    line 21
  5. Distinctive:

    Keep secrets out of code, logs, screenshots, summaries, widgets, and committed files.

    line 24
  6. Distinctive:

    Prefer project-local tooling and existing scripts before adding dependencies.

    line 25

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

Animation Jank QA

Use this skill for symptom-led runtime diagnosis. Start from a reproducible jank case and determine whether it comes from main-thread work, layout/paint, asset pressure, scroll coupling, competing animation systems, or lifecycle cleanup.

Workflow

  1. Reproduce the exact affected route, interaction, viewport, and device class.
  2. Read Animation Jank QA Guide for relevant diagnosis and retesting steps.
  3. Run the narrowest meaningful trace or rendered check for the symptom; inspect frame timing, long tasks, forced layout, paint/compositing, asset decode, observers, timers, and RAF loops as applicable.
  4. Fix issues when they are in scope; otherwise record exact evidence and remaining risk.
  5. Retest the original symptom and summarize commands, URLs, traces/screenshots, changed files, and what was not tested.

Always Protect

  • Inspect the framework, motion stack, affected media, component lifecycle, and available browser/performance tooling before changing code.
  • Do not claim something was tested unless it was actually tested; report exact commands, URLs, screenshots, viewports, failures, skipped checks, and remaining risk.
  • Reproduce and retest rendered output on the affected route and supported viewport/device classes; inspect console, trace, network and layout evidence relevant to that symptom.
  • Respect accessibility, performance, reduced-motion, and no-JavaScript/no-WebGL/no-autoplay fallbacks where relevant.
  • Keep secrets out of code, logs, screenshots, summaries, widgets, and committed files.
  • Prefer project-local tooling and existing scripts before adding dependencies. Explain any new dependency before installing it.
  • End with a concise handoff: changed files, commands run, checks passed, checks not run, deployment URL if any, and next risks.

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.