codex-game-studios/README.md

Codex Game Studios

Codex Game Studios is a Codex plugin for game-production workflows. It follows the normal plugin layout: .codex-plugin/plugin.json points to ./skills/, and skills expose the runtime workflows directly. Do not use a global ~/.codex/skills/codex-game-studio bridge as the plugin entry point.

Current State

• Skills:
  • $brainstorm guides game concept ideation into design/gdd/game-concept.md and design/gdd/game-pillars.md.
• Runtime agents: creative-director, art-director, technical-director, producer
• Runtime source: runtime/agents/
• Project guide template: project-template/AGENTS.md
• References: references/studio-docs/director-gates.md, references/studio-docs/templates/game-concept.md, references/studio-docs/templates/game-pillars.md
• Standards: standards/design-docs.md
• Marketplace: .agents/plugins/marketplace.json
• No hooks, rules, MCP servers, or app integrations yet

Review Intensity

production/review-mode.txt controls review-gate intensity:

• full: all key director / lead review gates call their custom agents.
• lean: only PHASE-GATE review gates such as /gate-check call directors; ordinary per-skill review gates are skipped.
• solo: all director review gates are skipped.

This is not a global off switch for all custom agents. Future team workflows may still call specialist subagents as part of their core work.

Runtime Setup

To install the bundled custom agents into a game project, run the installer directly:

python3 scripts/install_codex_runtime.py /path/to/game-project

The installer writes custom agents and the project guide to:

/path/to/game-project/.codex/agents/
/path/to/game-project/AGENTS.md

Each runtime agent is a standalone TOML file with name, description, and developer_instructions, matching Codex custom-agent conventions.

If the target project already has a different AGENTS.md, the installer reports a conflict and leaves it unchanged. Use --force-agents-md only when you intend to overwrite it.

Packaging Hygiene

Only plugin source files should be packaged. .git/, .env, .DS_Store, local caches, and generated artifacts are not part of the plugin runtime. Run the validation script before publishing or refreshing an installed cache:

python3 scripts/validate_plugin.py