This skill runs one loop: set a budget, measure, find the single bottleneck, fix it, measure again and report the numbers. It turns a complaint such as low FPS or a hitch into a frame-time budget (16.67 ms at 60 FPS), uncaps VSync before measuring and profiles a release-like build.
It lists where each engine reports the CPU and GPU split, then gives fixes that recur: object pooling, fewer draw calls and state changes, and removing per-frame allocations that cause GC spikes.
What You Get
- A step-by-step measurement workflow that ends in a report of scene, hardware, build type, before and after, bottleneck and fix
- A table of where Godot, Unity, Unreal and Roblox show the CPU and GPU split
- A headless Godot script that reports average, p95 and p99 frame time and exits with code 1 when p95 exceeds the budget
- Patterns for object pooling, batching and instancing, and zero-allocation Update code in Unity
Common Use Cases
- Diagnosing a game that drops below 60 FPS in big fights
- Removing a periodic GC hitch caused by allocations in Update
- Tracking down a hitch the first time an effect or enemy appears
- Adding a frame-time check to CI
What Makes It Unique
It insists on numbers before changes and lists the measurement traps: VSync hiding headroom, Godot TIME_PROCESS being the worst frame of the last second, editor and Deep Profile timings, mobile thermal throttling and Unity mobile defaulting to 30 FPS. It also says what was measured headless and what still needs the user’s device.
Under The Hood
The skill is instructions and one reference file on profiling and budgets, with no scripts of its own. It tells the agent to run the game and its tools to measure: Godot with VSync disabled and a headless frame-time script, Unity and Unreal profilers and console commands, and Unreal csvprofile, which writes a CSV capture file. It also tells the agent to edit code for pooling and allocation fixes and to ask the user to run phone sessions. It does not fetch web pages or call APIs.