agentleFS
TheGoat395TheGoat395/Codex-Skills/skills/performance-budget-lab/SKILL.md

performance-budget-lab

Skill136 starsChanged 5 months agoMITView on GitHub

Set performance budgets before implementation.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to keep visually rich sites fast.

    line 8
  2. Distinctive:

    Run Lighthouse or browser performance checks when feasible.

    line 29
  3. Distinctive:

    Check Core Web Vitals (LCP, CLS, INP) and supporting diagnostics such as TTFB.

    line 30
  4. Very specific:

    Prefer CSS and Motion for small interactions.

    line 32
  5. Very specific:

    Use Lighthouse or browser checks here to validate a budget decision, not to take ownership of deep runtime diagnosis.

    line 35

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

Performance Budget Lab

Use this skill to keep visually rich sites fast.

Own the budget and acceptance policy. Route measured runtime diagnosis, implementation fixes, and React/Next performance work to $performance-audit-websites.

Budget Areas

  • JavaScript bundle size
  • route-level code splitting
  • image dimensions, formats, and lazy loading
  • video poster, preload, autoplay, and reduced-data behavior
  • font loading and fallback metrics
  • animation cost and scroll handlers
  • layout shift sources
  • server rendering/static rendering choices
  • caching and CDN behavior

Workflow

  1. Identify stack and deployment target.
  2. Inspect package dependencies and route structure.
  3. Define route, hardware/device, network/cache state and measurement method.
  4. Run Lighthouse or browser performance checks when feasible.
  5. Check Core Web Vitals (LCP, CLS, INP) and supporting diagnostics such as TTFB; choose metrics that measure the budgeted user experience.
  6. Set media/JavaScript/font budgets from the intended experience and baseline evidence.
  7. Prefer CSS and Motion for small interactions; reserve GSAP/R3F/video for clear value.
  8. Report tradeoffs honestly when visual richness costs performance.

Use Lighthouse or browser checks here to validate a budget decision, not to take ownership of deep runtime diagnosis. When the work shifts from setting thresholds to locating and repairing the bottleneck, hand off to $performance-audit-websites.

Output

Give:

  • current risks
  • recommended budgets
  • measurement conditions and reconsideration rules
  • commands run
  • remaining uncertainty

Scope and evidence

Output a budget contract: route/device class, hardware, network/cache state, metric, threshold, test method and reconsideration condition. Route measured diagnosis/optimization to $performance-audit-websites; a budget-only request does not implement repairs.

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.