Audit game assets against naming, size, format, and reference integrity rules.
Implement one approved game system in production-facing project code.
Define the first audience-facing demo contract from a proven playable MVP and route the follow-up UI, asset, and presentation work.
Write or update a game-system GDD using the canonical gamedev template.
Decompose a game concept into systems, map dependencies, and maintain the systems index.
Choose a game engine or runtime direction and create a project technical-preferences document from the canonical gamedev template.
Refactor one raw Obsidian note into a clean, structured note with preserved meaning, frontmatter, and useful tags.
Use when browser testing is blocked and Codex must diagnose the exact failure layer: app server, local bind, reachability, repo wrapper, browser launch, trust/profile config, or sandbox/runtime. This is the doctor skill, not the normal runner.