game-performance-profiler — Claude Code skill: frame-time triage

What game-performance-profiler does

Reach for this skill when the evidence is a profiler screenshot, stat unit or stat gpu output, benchmark-route notes, or a review packet from a target device. It starts by pinning down the context: engine, target platform, whether the build is editor or packaged, the symptom, what evidence exists, how to reproduce it, and quality settings such as resolution and preset. From there it picks a single mode — quick triage, bottleneck classification, benchmark-route planning, device review, or escalation to deeper tools.

Then comes the part that matters: naming one primary bottleneck family. Gameplay scripting on the CPU, draw-call pressure on the render thread, GPU shaders and post-processing, garbage collection and allocation churn, loading and streaming, physics and animation, platform and thermal limits. When the packet is too thin to tell, the answer is unknown-needs-better-capture. The skill then recommends the cheapest next capture that would actually separate the candidates: a proper Unity Profiler packet from a player build, a matched stat unit and stat gpu pair on the exact repro route, or a packaged-on-device capture instead of another editor screenshot. Deeper traces such as Unreal Insights or the GPU Visualizer come only after the first packet earns them.

This is triage and planning, not an automatic optimizer. It does not edit code or tune builds — it hands back one artifact the team can act on.