saranskumar Goal
Focus performance work on measured bottlenecks and the most meaningful optimizations.
When to Use
- A system is slow or resource-heavy.
- Performance review is needed before scale or release.
- A design decision has clear performance implications.
Instructions
- Identify the performance symptom and where it appears.
- Separate measurement from proposed fixes.
- Trace the likely bottleneck across runtime, DB, network, or UI.
- Recommend changes with expected tradeoffs.
Constraints
- Do not optimize without a bottleneck hypothesis.
- Do not trade away correctness or observability casually.
- Keep recommendations tied to the active runtime.
Output Format
- bottleneck summary
- likely causes
- optimization plan
- tradeoffs and validation steps
Examples
- "Optimize this slow API path."
- "Why is this frontend rendering so heavily?"