performance-optimization

1# Performance optimization
2 
3Performance work is a measurement discipline, not a bag of tricks. The method is always the
4same: **profile → find the one bottleneck → fix that → measure again**. This skill teaches that
5loop and the highest-leverage fixes (pooling, batching, allocation control, asset budgets), and
6points you at each engine's profiler. It pairs with `physics-tuning` for simulation cost.
7 
8## When to use
9 
10- Use when the frame rate is low or uneven, the game stutters/hitches, or it must hit a target
11  (60 FPS desktop, 30/60 mobile) and currently doesn't.
12- Use to decide *what* to optimize: profile, read the frame budget, and identify whether the CPU
13  or GPU is the bottleneck before changing any code.
14- Use to apply specific fixes: object pooling, draw-call/batch reduction, removing per-frame
15  allocations and GC spikes, and setting asset budgets.
16 
17**When *not* to use:** for physics jitter/tunneling/timestep specifically, use `physics-tuning`.
18For the engine's concrete profiler UI and rendering settings, use that
19engine skill (`godot-export` covers some build settings; engine cores cover the rest). This skill
20is the cross-engine method and the shared fixes.
21 
22## The golden rule: measure first, never guess
23 
24Most performance "fixes" applied without profiling target the wrong thing and add complexity for
25no gain. **Do not optimize code you have not measured.** Open the profiler, find the single
26…