Measures performance baselines, detects regressions before and after PRs, and compares stack alternatives.
- What it does
- This skill defines a benchmarking workflow with four modes: page performance via browser metrics, API endpoint latency testing, build and dev-loop timing, and before/after comparison against a saved baseline. It records metrics such as LCP, CLS, INP, bundle size, p50/p95/p99 latency, and build times, then reports deltas in a table with verdicts. Baseline data is stored as JSON in a project directory and tracked through Git for team sharing.
- When to use it
- Use it when measuring the performance impact of a change before and after a pull request, establishing a project performance baseline, investigating user reports that something feels slower, verifying performance targets before a release, or comparing the performance of different technology stacks.
- Requirements
- Instructions only, with no bundled scripts. It relies on a browser MCP for page metrics and on the project's own build, test, lint, and TypeScript tooling for build measurements; it also writes baseline JSON files into the repository.