How do I install the Performance Budget skill?

Run npx skillmds@latest add thedaviddias/performance-budget in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Performance Budget safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Performance Budget?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Performance Budget free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Performance Budget?

thedaviddias (@thedaviddias) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Performance Budget by thedaviddias — Agent Skill

Name: Performance Budget
Author: thedaviddias

Performance Budget

Use when reviewing CI configuration, bundle analysis workflows, or pull requests that add dependencies and assets. Distinguish bundle-size budgets from runtime budgets such as Lighthouse or Core Web Vitals so teams can enforce both.

thedaviddias b67a485 2 files · 7.0 KB Updated Sep 17, 2026

File contents

Enforce performance budgets in CI

Without automated enforcement, performance degrades gradually — each PR adds a small library, each feature adds a few KB, and within months the app that loaded in 2 seconds now takes 5. Performance budgets make regressions visible at PR time rather than after user complaints. Catching 'this PR added 200KB to the bundle' in review is far cheaper than debugging a slow production site.

Quick Reference

Define specific thresholds: max bundle size, min Lighthouse score, max LCP time
Fail CI when budgets are exceeded to prevent performance regressions
Size budgets catch accidental heavy dependencies; Lighthouse budgets catch runtime regressions
Start with loose budgets and tighten them as you optimize
Monitor production RUM so regressions are caught after deploy, not only in CI

Check

Does this project have performance budgets defined? Check package.json and CI configuration for size or Lighthouse thresholds.

Fix

Set up bundle size limits with size-limit and Lighthouse CI assertions in the CI pipeline.

Explain

Explain performance budgets, how to choose appropriate thresholds, and how to enforce them with size-limit and Lighthouse CI.

Code Review

Inspect CI workflows, package.json, and Lighthouse or bundle-size config for explicit thresholds. Flag repos where budgets are missing, too loose to catch regressions, or unenforced on pull requests. Check whether production RUM and alerting are wired to detect regressions after release.

For full implementation details, code examples, and framework-specific guidance, see references/rule.md.

Rule page: https://frontendchecklist.io/en/rules/testing/performance-budget

---name: performance-budgetdescription: Use when reviewing CI configuration, bundle analysis workflows, or pull requests that add dependencies and assets. Distinguish bundle-size budgets from runtime budgets such as Lighthouse or Core Web Vitals so teams can enforce both.---# Enforce performance budgets in CIWithout automated enforcement, performance degrades gradually — each PR adds a small library, each feature adds a few KB, and within months the app that loaded in 2 seconds now takes 5. Performance budgets make regressions visible at PR time rather than after user complaints. Catching 'this PR added 200KB to the bundle' in review is far cheaper than debugging a slow production site.## Quick Reference- Define specific thresholds: max bundle size, min Lighthouse score, max LCP time- Fail CI when budgets are exceeded to prevent performance regressions- Size budgets catch accidental heavy dependencies; Lighthouse budgets catch runtime regressions- Start with loose budgets and tighten them as you optimize- Monitor production RUM so regressions are caught after deploy, not only in CI## CheckDoes this project have performance budgets defined? Check package.json and CI configuration for size or Lighthouse thresholds.## FixSet up bundle size limits with size-limit and Lighthouse CI assertions in the CI pipeline.## ExplainExplain performance budgets, how to choose appropriate thresholds, and how to enforce them with size-limit and Lighthouse CI.## Code ReviewInspect CI workflows, `package.json`, and Lighthouse or bundle-size config for explicit thresholds. Flag repos where budgets are missing, too loose to catch regressions, or unenforced on pull requests. Check whether production RUM and alerting are wired to detect regressions after release.---For full implementation details, code examples, and framework-specific guidance,see `references/rule.md`.Rule page: https://frontendchecklist.io/en/rules/testing/performance-budget

Frequently asked questions