← ClaudeAtlas

benchmark-optimization-looplisted

Use when a goal is vague speed ("make it faster", "reduce p95", "cut query time") and you need a bounded, measured loop that promotes only verified, correctness-preserving wins instead of guessed micro-tweaks.
pekral/cursor-rules · ★ 7 · Testing & QA · score 79
Install: claude install-skill pekral/cursor-rules
# Benchmark Optimization Loop (Laravel/PHP) Turn "make it faster" into a recursive, measured loop. Every promoted change beats a recorded baseline on a real measurement and keeps correctness green. No baseline, no budget, no promotion. ## Constraints - Apply `@rules/sql/optimalize.mdc` for any query change (N+1, eager loading, index usage, batching). - Apply `@rules/code-testing/general.mdc` — the correctness gate is the project test suite. - Measure, never guess. Every win is a real readback, not a label or intuition. - Never trade correctness for speed: a faster variant that changes output is rejected, not promoted. - Defer all measurement mechanics (how to run, warm-up, repetitions, noise) to `@skills/benchmark/SKILL.md`. This skill owns the loop and the gate, not the stopwatch. ## Use when - The goal is unquantified speed: "make it faster", "it's slow", "reduce p95". - You are eliminating an N+1, tuning a query, choosing a cache strategy, or raising queue throughput. - Multiple candidate fixes exist and you must pick the one that actually wins. - A "faster" claim was made without a before/after number. Do not use for first-time correctness (use `@skills/test-driven-development/SKILL.md`) or pure latency architecture without a comparison loop (`@skills/latency-critical-systems/SKILL.md`). ## Required baseline Before touching any code, write down all five. If any is missing, stop and define it. 1. **Operation** — the exact thing optimized (route, Action, job, query).