What problem does it solve? Game performance issues like frame hitches, low frame rates, memory leaks, and excessive draw calls are hard to diagnose without disciplined profiling. This Skill guides you through capturing reproducible evidence with the right Unity or Godot profiler, separating measured facts from hypotheses, and validating fixes with before/after captures. ## Core Features & Use Cases - Tool Selection Guidance: Maps each symptom (CPU timing, memory growth, rendering passes, static project risk, Godot frame monitors) to the correct first tool: Unity Profiler, Memory Profiler, Frame Debugger, Project Auditor, or Godot Profiler. - Reproducible Capture Recipes: Enforces capture hygiene including target hardware, warm-up, consistent quality settings, repeated trials, and labeled metadata so results are comparable. - Hypothesis-Driven Triage: Translates observations into bounded hypotheses (e.g., main thread over 16.67 ms budget, recurring GC.Alloc, retained native textures) and validates one change at a time. - Use Case: A Unity mobile game hitches during enemy spawns. Use this Skill to capture a CPU timeline on device, identify GC.Alloc spikes in the spawn step, switch to object pooling, and confirm the fix with a repeated capture. ## Quick Start Ask the assistant to help profile a Unity or Godot performance problem, describing your engine version, target device, and the exact symptom such as a frame hitch or memory growth.
