Game Studios — Codex instructions

This repository is a game-development studio template for Codex and Claude Code. It contains workflows, role briefs, document templates, and engine references; a fresh clone has no selected engine or playable game.

Start here

• Read docs/codex/runtime.md before using a studio workflow or role. It explains how the shared Claude-oriented instructions apply in Codex.
• Read .claude/docs/technical-preferences.md for the project's engine, language, platforms, and specialist routing. Unconfigured fields mean not selected; the bundled Godot references do not select Godot for the project.
• For a new game, use $studio-start. For workflow navigation, use $studio-help. Ask about missing game requirements; do not run onboarding when the user is asking to maintain the template itself.
• Reply in the user's language. Keep code identifiers and document IDs stable.
• Exclude AGENTS.md, AGENTS.override.md, CLAUDE.md, and CLAUDE.local.md from game-document counts and asset audits. An instruction-only directory is not evidence of implemented systems or game progress.

Working agreements

The user owns game direction, scope, and substantive design decisions. Clarify missing requirements and present concrete drafts when a decision is needed. An explicit request authorizes the edits needed to complete that task; do not ask for file-by-file approval again. Preserve any explicit review gates the user chooses. Skills and role briefs do not override user instructions or grant new execution permissions. Do not commit, push, publish, or deploy unless requested.

Use .claude/docs/coding-standards.md for code changes and .claude/docs/context-management.md for larger workflows. Use the domain ownership rules in .claude/docs/coordination-rules.md, applying the runtime guide's Codex translations for models, tools, and delegation.

Directory rules

Before editing a file, read the AGENTS.md files along its directory path, even when the session started at the repository root. Those files explicitly link to shared instructions; read the linked sources. Rules are scoped as follows:

Maintaining this template

• .claude/skills/, .claude/agents/, .claude/rules/, and .claude/docs/ are shared sources, usable without installing Claude Code. Preserve their paths so upstream changes remain easy to merge.
• Edit shared sources and scripts/sync_codex.py, then regenerate. Do not edit files marked Generated by scripts/sync_codex.py directly. Keep custom Codex skills/roles under distinct names; regeneration preserves unmanaged files.
• Read docs/codex/README.md for setup, compatibility limits, and manual checks.
• When changing commands, source attribution, directory layout, setup, or compatibility behavior, update README.md and README.zh-CN.md in the same changeset. Identify upstream-derived content versus fork additions, and keep the Claude-to-Codex usage mappings aligned with actual skill entry points.
• Verify adapter changes with:

python3 scripts/sync_codex.py --check
python3 -m unittest discover -s tests/template -v
git diff --check

Game builds and tests depend on the selected engine. Never report them as passing when no engine/project exists. For an authorized commit or push, run python3 scripts/studio_check.py commit or python3 scripts/studio_check.py push and the configured game tests. The adapter does not register Claude hooks in Codex.