perf-auditlisted

# Perf Audit Reply in the project conversation language (CLAUDE.md → Language); code, identifiers, paths and commit messages stay in English. Budgets — `technical-preferences.md`; references `stack-reference/web-platform.md`, `database.md`, `graphql.md`, `threejs-webgames.md`. ## Phase 1: Baseline (Bash, whatever is available) Web: `lighthouse --preset=perf --form-factor=mobile` / Lighthouse CI; `ng build --stats-json` / `vite build` + visualizer; API: `k6 run` scenario (create with consent); DB: `EXPLAIN (ANALYZE, BUFFERS)` on top queries, `pg_stat_statements`; Go `pprof`, PHP Blackfire/Xdebug; game: `renderer.info`, a Performance trace, memory. A missing tool — say so, offer installation. ## Phase 2: Analysis Table "metric → value → budget → status"; findings with estimated gain and cost; the 3 cheapest. ## Phase 3: Fixes (with consent) Through the relevant engineers; re-measure with the same method — before/after. ## Phase 4: Write "May I write `docs/ops/perf-audit-<date>.md`?" For every `OVER BUDGET` metric one `AskUserQuestion`: record it in `production/findings.md` (`PERF-NNN`, template `findings.md`) (Recommended) · improvement stories now · report only — so the budget miss reaches `/create-stories` and `/sprint-plan`. After the "write" answer: `touch .claude/.write-consent` (rule 7). Verdict: `WITHIN BUDGET` | `OVER BUDGET (metrics: …)`. Next step — one `AskUserQuestion`: improvement stories (Recommended) · `/release-checklist` · re-run `/perf-audit` after fixe