Performance Budgeting
Skill Purpose: Define and enforce performance budgets for load time, Core Web Vitals, and bundle size.
Core Skill Pattern
Objective: Prevent regressions by enforcing measurable performance limits.
Universal Pattern:
- •Define budgets per page and asset type
- •Measure against budgets in CI
- •Fail builds on budget regressions
- •Track budget history over time
- •Review and adjust budgets periodically
Key Decisions (Project-Specific):
- •Thresholds for Core Web Vitals
- •Budget scope (global vs per route)
- •Budget enforcement location (CI vs pre-merge)
Project-Specific Implementation Notes
Customize per project:
- •Align budgets with business goals
- •Set stricter budgets for critical flows
Example Budget Config
json
{
"lcpMs": 2500,
"cls": 0.1,
"fcpMs": 1800,
"jsBundleKb": 300
}
Best Practices
- •Start with realistic budgets
- •Tighten budgets over time
- •Fail on regressions, not noise
- •Track budgets in version control
- •Pair budgets with monitoring
Stop Conditions
STOP and escalate if:
- •Budgets are undefined or unrealistic
- •Measurement tooling is missing
- •Budgets conflict with product goals
Skill Version: 1.0.0