Codex Game Studio

中文说明

Codex Game Studio is a reusable Codex-native skills pack for game projects.

It ports the core workflow model of Claude Code Game Studios into Codex skill discovery. The pack is role-driven, workflow-driven, and designed to support the path from project concept through release.

What This Is

This repository is not a project template and not a single prompt.

It is a skill pack that gives Codex a reusable game-studio operating model:

• role skills for professional viewpoints
• workflow skills for stage progression
• shared references for templates, checklists, and conventions

The current pack is especially friendly to Cocos Creator workflows, but it is not hard-locked to one engine.

Install

Clone this repository into:

~/.agents/skills/codex-game-studio

Or symlink a local checkout into that location:

ln -s /path/to/codex-game-studio ~/.agents/skills/codex-game-studio

Then restart Codex so it can rediscover skills.

Quick Start

There are two main ways to use the pack.

1. Ask for a role

Use this when you already know what kind of specialist should lead.

Examples:

• Use game-designer to define the core loop for this puzzle game.
• Use tech-director to review the architecture for this Cocos feature.
• Use ui-ux-designer to draft the onboarding flow for the first three screens.

2. Ask for a workflow

Use this when you want Codex to move the project through a stage.

Examples:

• Use start-game-project to turn this idea into a playable project brief.
• Use write-gdd to turn these notes into a proper design document.
• Use plan-production to split this game into milestones.
• Use prepare-release to run a release-readiness pass.

3. Let the pack route for you

Use this when the request spans multiple specialties.

Examples:

• Use studio-orchestrator to route this project from idea to implementation.
• I have a Cocos game idea and don't know what to do next.

How To Choose

Use a role skill when:

• you need a specific professional perspective
• the problem is already scoped
• you want direct specialist output

Use a workflow skill when:

• you want to push the project into the next stage
• the output should produce handoff-ready work
• multiple roles may need to be involved

Use studio-orchestrator when:

• the request is mixed or ambiguous
• you want help deciding the next step
• you want the pack to coordinate phase progression

Included Skill Groups

• Role skills: producer, directors, designers, programmer, QA, release
• Workflow skills: concept, GDD, planning, implementation, QA, release
• Shared references: templates, checklists, and collaboration guidelines

Skills Included

Role skills

• studio-orchestrator
• producer
• game-director
• creative-director
• game-designer
• tech-director
• gameplay-programmer
• ui-ux-designer
• visual-artist
• audio-designer
• qa-lead
• release-manager

Workflow skills

• start-game-project
• define-game-concept
• write-gdd
• plan-production
• implement-feature
• design-ui-flow
• run-qa-pass
• prepare-release

Typical Project Flow

For a new game project, a common path looks like this:

1. start-game-project
2. define-game-concept
3. write-gdd
4. plan-production
5. implement-feature
6. design-ui-flow
7. run-qa-pass
8. prepare-release

For a feature already in development, a common path looks like this:

1. implement-feature
2. tech-director
3. gameplay-programmer
4. run-qa-pass
5. prepare-release

Repository Structure

codex-game-studio/
├── role skills
├── workflow skills
└── shared/references

Each role or workflow lives in its own directory with a SKILL.md.

shared/references/ contains reusable documents such as:

• project brief templates
• GDD templates
• production planning templates
• UI wireframe templates
• QA and release checklists
• Cocos collaboration guidelines

Cocos Notes

The pack includes shared/references/cocos-collaboration-guidelines.md, which currently covers:

• Cocos Creator + TypeScript assumptions
• scene, prefab, and script organization guidance
• resource lifecycle expectations
• UI structure guidance
• release-focused performance checks

This means the pack is immediately usable for Cocos projects without making every skill engine-specific.

Current Scope

This repository intentionally does not try to recreate Claude runtime behavior such as:

• .claude/ conventions
• slash commands
• hooks
• direct one-to-one recreation of every Claude agent

Instead, it preserves the more valuable part: the operating model.