webperf
Run a web performance audit via the web-performance-auditor persona
- Kind
- Prompt
- Works with
- Claude Code
- Source
- addyosmani/agent-skills @ 2686b620fc1f
- Path
- .claude/commands/webperf.md
- License
- MIT
- Jobs
- Review, UI/UX work
InstallCopy it from the source repository, or sign in and let the assistant adapt it for your project.
`/webperf` targets web applications specifically. Do not use it for utility libraries, CLIs, or server-only code with no browser-facing output. ## Determine the mode **Deep mode** — activate when any of these is available: - A Lighthouse JSON report file (e.g. `npx lighthouse <url> --output json --output-path ./report.json`, or `npx -p chrome-devtools-mcp chrome-devtools lighthouse_audit --output-format=json` from the Chrome DevTools MCP CLI) - A PageSpeed Insights JSON response (includes Lighthouse + CrUX) - A CrUX API response (requires `CRUX_API_KEY` or `GOOGLE_API_KEY`) - A DevTools performance trace - A live URL plus the `chrome-devtools` MCP server configured in the harness (the agent can capture metrics directly via `lighthouse_audit` and `performance_*` tools) - The Chrome DevTools MCP CLI invoked locally (via `npx -p chrome-devtools-mcp chrome-devtools <tool>` or after `npm i -g chrome-devtools-mcp`) — the user runs commands like `chrome-devtools lighthouse_audit --output-format=json` and passes the JSON output to the agent …