performance-budgetlisted

# Performance budget Use this skill at Stage 6e (after QA, on full / quick / hotfix tracks). Measures the three performance dimensions relevant to the change — Lighthouse Web Vitals, bundle size delta, and load-test throughput — and compares each against configured budgets. ## When to use each check | Check | Use when | |-------|----------| | **Lighthouse** | Frontend change touched a page or route (new component, redesigned flow, added asset loading) | | **Bundle size** | Change adds/removes JS or CSS that is bundled (new import, removed dependency, asset optimization) | | **Load test** | Change modifies an HTTP endpoint, adds a new API route, or changes a query/computation that runs on every request | **When to skip entirely**: If the change is purely backend with no HTTP surface change, doc-only, or infra config with no throughput impact, set `skipped_reason` and status PASS. ## Budget thresholds Look for budgets in this order: 1. `performance.budget.json` at the project root (preferred — machine-readable, shareable) 2. `.devteam/config.yml` under `performance.budgets.*` 3. These defaults when no config exists: | Metric | Default budget | |--------|---------------| | Lighthouse score | ≥ 0.80 (80/100) | | LCP | ≤ 2500ms | | INP | ≤ 200ms | | CLS | ≤ 0.1 | | Bundle total | — (warn only; no hard limit without explicit config) | | Bundle delta | ≤ 50KB per PR | | Load p95 | ≤ 200ms | | Load error rate | ≤ 1% | If `performance.budget.json` is absent, record that in th