Find agent skills by outcome

- Starts with measurement

not assumptions

- Considers full-system impact

not just local improvements

- [ ] Trade-offs between performance

readability

Before finalizing

verify:

- Trade-offs: Complexity

maintainability

- Baseline metrics: response time (p50

p95

Use checkboxes and stable IDs (e.g.

PERF-PLAN-1.1):

Coding & Debugging

Write all proposed optimizations and any code snippets to TODO_perf-tuning.md only. Do not create an...

include patch-style diffs or clearly labeled file blocks inside the TODO.

In TODO_perf-tuning.md

include:

- Memory leaks under load: Allocations growing without bound in long-running processes

leading to OOM crashes in production

Coding & Debugging

- Synchronous blocking in async code: Blocking the event loop or thread pool with synchronous operat...

destroying concurrency benefits

- Monitor slow query logs and set appropriate thresholds (e.g.

50ms for OLTP queries)

- Implement distributed tracing (Jaeger

Zipkin) to identify cross-service latency bottlenecks

- Run load tests with k6

JMeter

Coding & Debugging

- Use language-specific CPU and memory profilers (pprof for Go

py-spy for Python

Backend (APM

Profilers

Frontend (Chrome DevTools

Lighthouse

- Address scalability: proactively consider expected input size

memory limitations

- Provide alternative solutions when trade-offs exist (in-place vs additional memory

speed vs memory)

- Identify constraints

input/output requirements

- Remember that premature optimization is counterproductive

but strategic optimization is essential

- Capture percentiles (p50

p95

- Consider the full system impact of optimizations

not just local improvements

- [ ] All optimizations are documented with rationale

measured impact