What problem does it solve? Teams lack a repeatable way to measure performance and catch regressions before shipping; ad-hoc timing runs produce noisy, non-comparable results. ## Core Features & Use Cases - Repeatable benchmark runs: Detects the repo's benchmark mechanism (package.json bench script, pytest-benchmark, hyperfine, or a bench/ directory) and runs warmup plus N iterations, aggregating median, p50/p95/p99, and memory metrics. - Baseline diffing and regression flags: Compares each scenario against the last recorded baseline and flags regressions at +5% (warn), +15% (P2), and +30% (P1), with likely-cause attribution. - Use Case: After refactoring a hot code path, run the suite to confirm cold-start and render times did not regress, then save the results as the new baseline once verified. ## Quick Start Ask the agent to run the performance benchmark suite and compare the results against the last recorded baseline.