hatch3r-perf-audit

> **Note:** Commands below use `npm` as an example. Substitute with your project's package manager (`yarn`, `pnpm`, `bun`) or build tool when your project uses a different package manager. # Performance Audit Workflow ## Quick Start ``` Task Progress: - [ ] Step 0: Detect ambiguity (P8 B1) - [ ] Step 1: Read performance budgets from rules and specs - [ ] Step 2: Profile — bundle size, runtime, memory - [ ] Step 3: Identify violations — which budgets exceeded, which hot paths slow - [ ] Step 4: Plan optimizations — code splitting, lazy loading, memoization, etc. - [ ] Step 5: Implement optimizations with before/after measurements - [ ] Step 6: Verify all budgets met, no regressions ``` ## Step 0 — Detect Ambiguity (P8 B1) Before any work, scan the invocation for unresolved questions in scope, intent, acceptance criteria, target environment, or irreversibility. If any are found, ask the user via the platform-native question tool per `agents/shared/user-question-protocol.md`. Do not proceed under silent assumption. Default path, not an exception. Triggers for THIS skill: target surface (frontend bundle vs backend cold start vs DB query), budget threshold values, profiling environment (local vs CI vs production), regression policy (revert vs ship-and-monitor), and whether optimization is allowed to introduce new deps. ## Fan-out Discipline (P8 B2) Fan-out scales with task size; token cost never justifies serializing independent work (`rules/hatch3r-fan-out-discipline.md` P...