Skip to content
Agentmart
Submit a tool

performance-budget-lab

Set performance budgets before implementation.

Skill by TheGoat395

IndexedMIT★ 132
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/thegoat395-performance-budget-lab

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Set performance budgets before implementation.

Use cases: finance

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md and code. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/performance-budget-lab

What's inside

Skill name
performance-budget-lab
Description
Set performance budgets before implementation.
License
MIT
Instructions
46 lines in SKILL.md · view on GitHub

Files (2)

  • SKILL.md
  • openai.yaml · agents/

SKILL.md (first lines)

# 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.

From TheGoat395/Codex-Skills, MIT.

More from TheGoat395/Codex-Skills

Signals

Stars
132
Forks
48
Open issues
0
Last commit (this folder)
Sep 10, 2026 (1 month ago)
Last release
Aug 30, 2026 (2 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from TheGoat395

Cite this page

performance-budget-lab skill. Agent Mart. https://agentmart.dev/skills/thegoat395-performance-budget-lab (last updated 2026-10-24)