What problem does it solve? Frontend teams often ship performance regressions because Lighthouse audits are run manually, against dev servers, or as single flaky runs. This Skill adds a CI gate that blocks pull requests unless the production build meets explicit Core Web Vitals budgets and category score floors. ## Core Features & Use Cases - Single-source budget config: All budgets and assertions live in one lighthouserc.cjs with named constants for LCP, CLS, and TBT (as the INP lab proxy), plus category floors for performance, SEO, accessibility, and best practices. - Flake-resistant gating: Median-of-N runs (aggregationMethod: "median-run", numberOfRuns >= 3) against the production build, never the dev server. - CI integration: A GitHub Actions workflow builds the app, runs lhci autorun, and always uploads HTML/JSON reports as artifacts for debugging failures. - Use Case: A team adds the gate to their Next.js app so every PR touching apps/web is blocked if LCP exceeds 2500 ms or the accessibility score drops below 0.95. ## Quick Start Ask the AI to add a Lighthouse CI performance gate with Core Web Vitals budgets and a PR-blocking GitHub Actions workflow to your web app.