Codex Game Studios Project Guide

This file is the root project guide for Codex. It is installed at the game project root so Codex and bundled subagents have shared context before running game-production workflows.

Technology Stack

Engine: [CHOOSE: Godot 4 / Unity / Unreal Engine 5]
Language: [CHOOSE: GDScript / C# / C++ / Blueprint]
Version Control: Git with trunk-based development
Build System: [SPECIFY after choosing engine]
Asset Pipeline: [SPECIFY after choosing engine]

Engine-specialist agents will be added later. For now, use the four bundled director agents only when a workflow explicitly asks for them.

Runtime Agents

Bundled custom agents are installed into:

.codex/agents/

Current bundled agents:

creative-director
art-director
technical-director
producer

These agents are primarily used by director / lead review gates. They are not a replacement for user decisions.

Review Intensity

Review intensity is configured by:

production/review-mode.txt

Allowed values:

full — all gates active; every workflow step is reviewed.
lean — PHASE-GATEs only (/gate-check); per-skill gates are skipped.
solo — no director gates anywhere.

Default when the file is missing: lean.

Collaboration Protocol

User-driven collaboration, not autonomous execution. Every workflow follows:

Question -> Options -> Decision -> Draft -> Approval

Ask clarifying questions when the user's intent or constraints are unclear.
Present options with trade-offs before major creative or technical decisions.
The user makes final strategic decisions.
Show drafts or summaries before writing important project files.
Do not commit changes unless the user asks.
Do not overwrite existing project guidance or design documents without explicit approval.

Current Workflow Surface

The current plugin build exposes only the migrated /brainstorm workflow.

/brainstorm produces:

design/gdd/game-concept.md

Game pillars and anti-pillars are defined during /brainstorm and recorded inside design/gdd/game-concept.md. A separate design/gdd/game-pillars.md may be created later from the template if the project needs a standalone pillar source of truth.

Design Documents

Use these project paths:

design/gdd/
design/ux/
docs/architecture/
production/

design/gdd/game-concept.md, optional design/gdd/game-pillars.md, and design/gdd/systems-index.md are top-level design documents. They are not per-system GDDs.

Per-system GDDs under design/gdd/ should include:

Overview
Player Fantasy
Detailed Rules
Formulas
Edge Cases
Dependencies
Tuning Knobs
Acceptance Criteria

Context Management

If a workflow becomes long, persist decisions into the relevant project file instead of relying only on chat context.
When resuming, read existing project documents before restarting a workflow.
Preserve user-authored content and update only the sections needed for the active task.

3.0 KiB Raw Blame History