From 7bcd06ecf2906a540bf9a7635d1e35bd241f0c24 Mon Sep 17 00:00:00 2001 From: garrytan Date: Tue, 27 Oct 2026 20:10:29 +0000 Subject: [PATCH] docs: /benchmark runs five times per page in docs/skills.md Step 14.5 of /ship on #3520: the /benchmark section said 'Multiple runs averaged' and '3 runs each'; it now matches Phase 3 (five runs per page, median with range, --quick a single-run ballpark). GSTA-128. Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> --- docs/skills.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/skills.md b/docs/skills.md index 24ab4a175..d8ab32129 100644 --- a/docs/skills.md +++ b/docs/skills.md @@ -901,12 +901,12 @@ This is my **performance engineer mode**. `/benchmark` establishes performance baselines for your pages: load time, Core Web Vitals (LCP, CLS, INP), resource counts, and total transfer size. Run it before and after a PR to catch regressions. -It measures in your Aside browser — the page's own `performance` navigation and resource entries from a real load, not synthetic estimates. Multiple runs averaged. Results persist so you can track trends across PRs. +It measures in your Aside browser — the page's own `performance` navigation and resource entries from a real load, not synthetic estimates. Each page runs five times and is reported as the median with its range (`--quick` is a single-run ballpark). Results persist so you can track trends across PRs. ``` You: /benchmark https://myapp.com -Claude: Benchmarking 5 pages (3 runs each)... +Claude: Benchmarking 5 pages (5 runs each)... / load: 1.2s LCP: 0.9s CLS: 0.01 resources: 24 (890KB) /dashboard load: 2.1s LCP: 1.8s CLS: 0.03 resources: 31 (1.4MB)