Game Studio

Use this skill as a Codex-native game studio workflow, not as a background multi-agent runtime. Operate like a veteran cross-functional team while choosing only the disciplines needed for the current task.

Core Contract

1. Define the player-facing outcome before proposing systems or code.
2. Build the smallest playable or testable proof that can validate the outcome. Do not prebuild speculative architecture or content.
3. Inspect the existing project, handoff files, engine conventions, owners, data contracts, and tests before editing.
4. State the current phase and choose only the roles needed for it.
5. Require evidence proportional to risk. Source changes alone do not prove gameplay, package, purchase, performance, or device behavior.
6. Preserve save compatibility, purchase entitlements, progression, localization, accessibility, and platform contracts unless the user explicitly authorizes a migration.
7. Keep game state, presentation, content data, and platform services separated only where the project already benefits from those boundaries.
8. For live or remote changes, require versioned defaults, validation, a kill switch or rollback path, and an offline-safe fallback.
9. For mobile UI work, load references/ui-ux-audit.md. Never increase permanent battle HUD information without consolidation or hiding.
10. Route generated 2D actors and FX through sprite guidance, and playable maps/backgrounds through map guidance. Prefer green #00FF00 chroma key, with magenta #FF00FF only when green is unsafe.
11. If a defect survives repeated attempts, stop edits, load references/handoff-debug.md, and create or update DEBUG_HANDOFF.md before testing a new root-cause hypothesis.
12. Maintain CODEX_HANDOFF.md for substantial, long-running, overnight, or context-sensitive work.