performance-budget-enforcer

Performance regressions are prevented by enforcing budgets on bundle sizes, Lighthouse scores, and Web Vitals metrics during CI/CD workflows. Define thresholds in a performance-budget.json configuration file, integrate checks into your build pipeline, and deployments are blocked automatically when budgets are exceeded.

Yes, bundle size and Lighthouse scores are monitored simultaneously across initial, route, and total bundles plus Lighthouse categories. The Skill tracks both metrics in a single configuration, generates unified reports, and gates deployments when either metric breaches its budget.

Configure Web Vitals thresholds in performance-budget.json alongside bundle and Lighthouse budgets. Use the included generation script to initialize baselines, integrate checks into your CI workflow such as GitHub Actions, and start monitoring from your next deployment automatically.

The Skill includes Python scripts—check_budgets.py and track_bundle_size.py—that compute bundle overruns and compare metrics across deployments. No external tooling is required; configuration and the provided scripts handle tracking, reporting, and deployment blocking end-to-end.

Integrate the budget checks into your CI/CD pipeline; when metrics exceed thresholds, the Skill generates alerts, marks builds as failing, and blocks deployments. CI platforms like GitHub Actions surface these alerts automatically as part of build status and PR checks.