Agent skill · Frontend

frontend-lighthouse

Add a portable Lighthouse CI gate for production frontend builds with Core Web Vitals budgets, category floors, median runs, and CI artifacts.

Nick44,086★ · +407/wk · 1 repos on radarProfile →
claude-codecodexcursorMIT
Install
npx skills add sickn33/agentic-awesome-skills --skill frontend-lighthouse --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 15 KB
Bundled scripts: none
Declared author: stareezy-1
Path: skills/frontend-lighthouse/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 44,414 · +328 this week
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Frontend Lighthouse (portable performance gate) > Portable skill — readable by Claude Code, OpenCode, Codex, Cursor, Windsurf, and others. > This skill describes a **CI performance gate** — a Lighthouse CI config plus a workflow — not a > component library or a visual style. It pairs with the **frontend-seo** and > **frontend-architecture** skills: SEO writes the metadata, Lighthouse proves it ships fast. The goal: every pull request is **blocked unless the production build meets explicit Core Web Vitals budgets and category score floors**. Budgets live in **one** `lighthouserc.cjs`, runs are **median-of-N** so the gate doesn't flake, and the same config runs locally and in CI. ## When to Use This Skill - Use when adding a Lighthouse CI performance gate to a web app. - Use when setting Core Web Vitals budgets for LCP, CLS, and TBT as the lab proxy for INP. - Use when configuring category score floors for performance, SEO, accessibility, and best practices. - Use when debugging flaky Lighthouse runs or making reports visible as CI artifacts. --- ## 0. The five core ideas 1. **One config, one source of truth.** All budgets and assertions live in a single `lighthouserc.cjs`. Named c

What's inside
Steps it walks through
  1. When to Use This Skill
  2. 0. The five core ideas
  3. 1. Files this skill adds
  4. 2. The config (lighthouserc.cjs)
  5. 3. Choosing budget severity and thresholds
  6. 4. The npm script
  7. 5. The GitHub Actions workflow
  8. 6. Framework adapters
  9. 7. Debugging failing or flaky runs
  10. 8. Conventions checklist (enforce in review)
  11. 9. How to apply this skill
  12. Publishing / installing this skill
  13. Limitations
Commands it runs
pnpm add -D @lhci/cli        # or npm i -D / yarn add -D
pnpm build && pnpm lhci
desktop form factor:
More from agentic-awesome-skills
All skills →
About this skill
What does the frontend-lighthouse skill do?

Add a portable Lighthouse CI gate for production frontend builds with Core Web Vitals budgets, category floors, median runs, and CI artifacts.

How do I install it?

Run `npx skills add sickn33/agentic-awesome-skills --skill frontend-lighthouse --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going