performance-budget-lab
Skill136 starsChanged 5 months agoMITView on GitHub
Set performance budgets before implementation.
In this repository80 other files it gives its agents.
- AGENTS.mdAGENTS.md
- accessibility-audit-websitesSkill
- accessibility-performance-polishSkill
- agent-evaluation-operationsSkill
- agent-memory-provenanceSkill
- agent-orchestration-architectureSkill
- animation-easing-languageSkill
- animation-jank-qaSkill
- animation-tool-routerSkill
- anti-generic-website-reviewSkill
- brand-voice-to-ui-copySkill
- browser-inspection-workflowSkill
- code-change-safety-checkpointSkill
- code-change-undo-revertSkill
- color-material-lighting-directionSkill
- content-pruning-reviewSkill
- content-structure-information-architectureSkill
- conversion-forms-checkout-polishSkill
- creativitySkill
- critical-thinkingSkill
- cross-browser-qaSkill
- css-grid-editorial-systemsSkill
- cta-language-systemsSkill
- deep-researchSkill
- design-motion-principlesSkill
- editorial-typography-systemsSkill
- evidence-reconciliationSkill
- final-client-handoffSkill
- frontend-quality-auditorSkill
- frontend-tooling-trust-gateSkill
- gsap-performanceSkill
- hero-image-art-directionSkill
- image-crop-responsive-qaSkill
- image-video-loading-qaSkill
- logical-thinkingSkill
- mobile-responsive-qaSkill
- modern-site-engineeringSkill
- motion-language-directorSkill
- motion-performance-qaSkill
- motion-react-layout-transitionsSkill
- motion-react-microinteractionsSkill
- motion-react-page-transitionsSkill
- motion-react-patternsSkill
- nextjs-app-router-routingSkill
- nextjs-server-client-boundariesSkill
- nextjs-site-architectureSkill
- non-generic-web-copySkill
- performance-audit-websitesSkill
- premium-visual-reference-librarySkill
- premium-web-build-gateSkill
- radix-accessible-primitivesSkill
- react-accessible-componentsSkill
- react-component-compositionSkill
- react-component-craftSkill
- react-error-loading-empty-statesSkill
- react-form-patternsSkill
- react-responsive-componentsSkill
- react-state-and-effects-disciplineSkill
- reduced-motion-designSkill
- responsive-visual-polish-qaSkill
- The first 60 shown.
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
- Distinctive: line 8
Use this skill to keep visually rich sites fast.
- Distinctive: line 29
Run Lighthouse or browser performance checks when feasible.
- Distinctive: line 30
Check Core Web Vitals (LCP, CLS, INP) and supporting diagnostics such as TTFB.
- Very specific: line 32
Prefer CSS and Motion for small interactions.
- Very specific: line 35
Use Lighthouse or browser checks here to validate a budget decision, not to take ownership of deep runtime diagnosis.
≈ “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.
Files
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
- Identify stack and deployment target.
- Inspect package dependencies and route structure.
- Define route, hardware/device, network/cache state and measurement method.
- Run Lighthouse or browser performance checks when feasible.
- Check Core Web Vitals (LCP, CLS, INP) and supporting diagnostics such as TTFB; choose metrics that measure the budgeted user experience.
- Set media/JavaScript/font budgets from the intended experience and baseline evidence.
- Prefer CSS and Motion for small interactions; reserve GSAP/R3F/video for clear value.
- 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.
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
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.

