unity-diagnostics-performance

# Unity Diagnostics And Performance If it is not already loaded, read `.claude/skills/unity-mcp-operations/SKILL.md` once. Diagnose from the cheapest deterministic signal to the most expensive probe. Enable `VERIFY`, `RUNTIME`, or `MEDIA` only when needed. ## Diagnostic Ladder 1. `mcp_status` for connection and mode. 2. `await_compile(timeout=0)` for compile state and corroborated errors. 3. `console_mark`, reproduce once, then `get_console_since(mark_id=...)`. 4. Targeted hierarchy or component inspection. 5. `scan_scene`, `scene_health`, or domain-specific diagnostics. 6. `verify_after_change(...)` when a completed change needs compile checks plus explicitly requested console, NUnit, or playtest gates. 7. Runtime snapshot, watch, frame statistics, or profile in Play Mode. 8. Screenshot only for a visual symptom. ```text console_mark() # reproduce once get_console_since(mark_id="<exact returned token>") ``` ```text runtime_snapshot(type="FeatureController", name="Subject", compress=True) watch( action="add", path="/Subject", component="FeatureController", field="state", condition="== Error", trigger_action="log" ) get_watches() watch(action="clear") ``` ## Performance - Establish the scenario and baseline before profiling. - Use `get_frame_stats` for a compact snapshot, then `profile` for a bounded capture when the snapshot indicates a problem. - Compare like-for-like Editor state, camera, scene, and time scale. - Separate CPU, allocation, rendering, ...