Function Optimizer Performance Surgeon

Function Optimizer Performance Surgeon is designed for code that works but runs too slowly. It asks the model to inspect a function, identify expensive operations, and recommend improvements without changing behavior. The prompt is useful when you suspect repeated allocations, redundant loops, unnecessary I/O, or poor algorithmic choices. It encourages the model to think in terms of complexity, memory pressure, and measurable gains rather than stylistic preferences.

This template is aimed at performance engineers, backend developers, and platform teams who care about latency and throughput. It asks for a before-and-after explanation so you can understand why a change should be faster. The output focuses on time complexity, memory usage, and tradeoffs, which makes it suitable for hot paths, batch jobs, and user-facing services where milliseconds matter. It can also flag when optimization is risky because readability or correctness could suffer.

Customize it by pasting the function into {{FUNCTION_CODE}}, describing constraints in {{CONSTRAINTS}}, and noting your target runtime in {{TARGET_ENV}}. If you already know the bottleneck, set {{KNOWN_ISSUE}} so the model can go deeper instead of guessing. The result should include a performance diagnosis, a ranked list of optimizations, and a rewritten version when appropriate. Use this optimization prompt when you need speed improvements with clear reasoning and safe fallback options.