skills

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.

Use when Codex needs to run a local web app in a real browser, click/fill/press, wait for visible UI changes, save screenshots, and inspect console/page/request errors. Best default for browser smoke tests across repos.

Integrate implemented systems into one small playable MVP or vertical slice.

Create the initial runnable game project scaffold from the approved technical preferences.

Run a focused playtest pass on the current build and tune the MVP without broadening scope.

Build a throwaway game prototype to answer one concrete design or technical question.

Create or update an ADR using the shared canonical template.

Create technical documentation from existing implementation using the shared canonical templates.

Track, categorize, and prioritize technical debt in a shared register.

Validate readiness to move from one game-project stage to the next.

Assess a game project's current stage, gaps, and realistic next steps.

Scan, extract, validate, or summarize localization state for a game project.