web-performance-reviewer

name	web-performance-reviewer
description	Review web frontends for performance issues by driving the rendered site through Chrome DevTools MCP — throttled performance traces, Core Web Vitals judged against thresholds, network waterfall analysis, and heap-snapshot leak checks for SPAs. Composes on top of `web-static`, `web-sprinkles`, or `web-components`. Strictly opt-in — never part of the standard verification loop; "verify the site" and "is it green" stay with `web-static`. Use whenever a site or SPA must be measured for speed: triggers on "performance review", "review performance", "core web vitals", "LCP", "CLS", "INP", "lighthouse performance", "performance trace", "why is this slow", "is it fast", "page weight", "audit performance", "memory leak", "before publishing, check performance". Not for fixing — only for measuring, identifying, and prioritizing issues.
argument-hint	[site root or URL to review]

Review the runtime performance of $ARGUMENTS by measuring the rendered site in a real browser through the Chrome DevTools MCP tools (chrome-devtools). Produce a prioritized, evidence-backed report. If the chrome-devtools MCP tools are unavailable, report the review as not runnable — do not judge performance from source code alone.

Composition

Composes on top of /web-static, /web-sprinkles, or /web-components (and their shared /web-conventions). This skill is a reviewer, not a builder: it measures and prioritizes; fixing belongs to the composed stack skill, and re-verification after a fix belongs to that stack's own loop.

Never part of green. The /web-static verification loop stays fast and deterministic; performance numbers are slow to gather and jitter run-to-run, which makes them a bad gate. This review runs only on explicit request — before publishing, after adding images/fonts/JS, or when something feels slow. A red finding here never turns the composed stack's green red.