Menu
Use when optimizing code performance, addressing slowness complaints, or measuring application speed improvements
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when orchestrating parallel Claude Code instances across tmux panes with git worktree isolation — managing multiple concurrent development tasks visually
Use when production incident occurs, alerts fire, service degradation detected, or on-call escalation needed - guides systematic organizational response before technical fixes
Use when conducting manual PR reviews - provides structured checklist covering security, performance, maintainability, and code quality dimensions with anti-sycophancy principles
Run local CI checks and ship changes — create branch, commit, push, and PR. Optionally link to a GitHub issue. Use when changes are ready to ship.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Architecture guide using Next.js App Router's Parallel Routes for Widget-Slot pattern. Separates static layouts from dynamic widgets to achieve separation of concerns, fault isolation, and plug-and-play development.
| name | performance-optimization |
| description | Use when optimizing code performance, addressing slowness complaints, or measuring application speed improvements |
| context | fork |
| agent | general-purpose |
| allowed-tools | Read, Grep, Glob, Bash |
Iron Law: NO OPTIMIZATION WITHOUT PROFILING FIRST
No exceptions - not for "obvious" bottlenecks, "quick wins", or "best practices".
Use for: Slow APIs, UI lag, high memory, slow builds, database queries, any "make it faster" request.
| Phase | Activity | Output |
|---|---|---|
| 1. Profile | Find hot paths with profiler | Bottlenecks with % of time |
| 2. Benchmark | 5 warm-up + 10 measured runs | Baseline with mean, std, p95 |
| 3. Prioritize | Apply Amdahl's Law | ROI-ranked list |
| 4. Optimize | ONE change, verify | Measured improvement |
| 5. Prevent | CI gates, monitoring | Regression detection |
Formula: Speedup = 1 / ((1 - P) + P/S)
| Bottleneck % | Max Speedup | Action |
|---|---|---|
| < 5% | < 1.05x | Skip |
| 5-20% | 1.05-1.25x | Low priority |
| 20-50% | 1.25-2x | Medium |
| > 50% | > 2x | High priority |
Multiple similar %? Optimize easiest first. Re-profile after each.
Add CI gate: PERF_BUDGET_MS: 150 → fail build if exceeded
| Excuse | Reality |
|---|---|
| "I know the bottleneck" | Profiling surprises 90% of time |
| "Micro-optimizations add up" | Amdahl's Law: 5% code = 95% time |
See documentation-template.md for before/after template.
