30 lines
1.4 KiB
Markdown
30 lines
1.4 KiB
Markdown
---
|
|
name: using-codex-game-studios
|
|
description: "Use when a user asks how the Codex Game Studios plugin is structured, what workflow to run next, how to initialize it, or how it differs from generic development workflow plugins."
|
|
---
|
|
|
|
# Using Codex Game Studios
|
|
|
|
Codex Game Studios is a game-production plugin built around plugin-discovered skills, not global `~/.codex/skills` bridge folders.
|
|
|
|
## Entry Points
|
|
|
|
- Use `$setup-runtime` when a project needs the bundled director agents installed into `.codex/agents/`.
|
|
- Use `$brainstorm` to turn a rough game idea into `design/gdd/game-concept.md`.
|
|
- Use `runtime/agents/` as the plugin source of bundled custom agents.
|
|
- Use `references/` and `standards/` only when the active workflow points to them.
|
|
|
|
## Review Intensity
|
|
|
|
`production/review-mode.txt` controls review-gate intensity, not whether agents
|
|
exist or whether future team workflows may use subagents for core work:
|
|
|
|
- `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.
|
|
|
|
## Design Rule
|
|
|
|
Do not rely on a global `~/.codex/skills/codex-game-studio` bridge. The installed plugin exposes its skills through `.codex-plugin/plugin.json` with `"skills": "./skills/"`, matching the normal Codex plugin layout.
|