What problem does it solve? Working with Codex (Astra 6) on Unity mini-games wastes its usage limit on problem discovery rather than fixes, and poorly scoped prompts cause context compaction, lost task items, and wasted effort. This Skill defines a division of labor where Claude diagnoses issues in the running game and writes targeted prompts, while Codex only executes fixes. ## Core Features & Use Cases - Role separation workflow: Claude enters Play mode via Unity MCP, captures screenshots, diagnoses bugs, and verifies results; Codex writes code, builds art, and edits scenes. - Prompt modes and reasoning levels: Distinguishes cheap targeted prompts (symptoms listed, medium reasoning) from expensive creative prompts (artistic search, xhigh reasoning), with rules for prompt size and session splitting. - Post-Codex verification checklist: Validates frozen files, console output, in-game visuals, network code, and commits after every Codex session. - Use Case: A game designer notices broken UI in a Unity mini-game. Claude enters Play mode, captures screenshots of the failure, writes a five-point targeted prompt with exact symptoms, Codex fixes it, and Claude verifies the result in-game before committing. ## Quick Start Ask Claude to enter the Unity game, diagnose the visible problems, and write a targeted prompt for Codex to execute.