Claude Cowork Game Studio skill
21 skills run a solo Unity studio: concept, systems, architecture, stories, code and review, gated at each stage.
- 82 ★ on the repository
- Last commit
Extended access
Why this level
- Skills create and edit project files: documents, code and tests.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/claude-cowork-game-studioDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Skills create and edit project files: documents, code and tests.
This is third-party code. Review the repository files before installing.
What it does
The skill set imposes a studio process on a Claude Cowork session for a solo or small Unity team. The pipeline runs: `/start`, `/brainstorm`, `/map-systems`, `/design-system`, `/consistency-check`, `/create-architecture`, `/create-epics`, `/create-stories`, `/story-readiness`, `/dev-story`, `/code-review`, `/story-done`. A gate sits before each next stage: numeric values, entity definitions and architecture decisions come from documents rather than from the agent head. `/propagate-design-change` and `/reverse-document` work outside the main chain. `/resume-session` opens a session, `/save-session` closes it and `/learn` stores a solution worth keeping. Three Unity skills exist: `unity-tdd-workflow`, `unity-clean-architecture-review` and `unity-bug-root-cause`. Each skill carries its own `roles/`, `refs/` and `templates/` folders, so no separate subagents or hooks are needed.
Who it is for. Developers of solo and small Unity game projects who need document and stage discipline when working with AI.
Good fit when
- A game idea sits in notes and must grow into a systems document and an architecture with mandatory ADRs.
- Before development stories are checked against the design document and acceptance criteria.
- A mechanic change in one document must propagate to all dependent ones.
- A gameplay bug must be traced back to its originating decision rather than patched.
Not a fit when
- The game is not built on Unity: the skills and templates assume it.
- You work in Claude Code without Cowork and do not want to adapt instructions.
- You need a quick prototype with no documents or stages.
Example request
Run brainstorm for an orbital survival game, then build a systems map and show dependencies.Limitations
The set targets Claude Cowork and Unity. Skills install as `.skill` files (a ZIP of a folder with `SKILL.md`), while the `design/`, `docs/`, `production/` and `src/` folders are created in your connected project rather than in this repository. A strict process with gates slows small tasks. The repository has no license file and the author states no reuse rights. The last commit dates from October 2026.
How to disable. Remove the installed `ccgs-*`, `unity-*` and `query-me` skills in Cowork settings. Delete the `design/` and `docs/` folders in your project by hand.
FAQ
How do I install the skills?
Connect the project folder in Cowork and install the `.skill` files you want: each is a ZIP of a `ccgs-<name>/` or `<name>/` folder with `SKILL.md` and bundled `refs/`, `roles/`, `templates/`.
In what order does the pipeline go?
First `/start` and `/brainstorm`, then the systems map and design, a consistency check, architecture, epics and stories, implementation, review and story closure.
What does /story-readiness do?
It checks a story file against design document requirements, ADR references and acceptance criteria. The verdict is READY, NEEDS WORK or BLOCKED.
Are subagents or hooks needed?
No. Roles live in `roles/` and are adopted inside the skill, and there is no separate hook configuration.
What does unity-bug-root-cause do?
It traces a gameplay bug back to the originating design decision so the cause is fixed rather than the symptom.
Discussion
No questions or reviews yet.
Related
SkillsA Claude Code project template for game development: a studio hierarchy of agents, skills for every phase, hooks, rules and doc templates
Seventeen Claude Code skills for product work: specs, branch review, a pre-commit check and cleanup of leftovers.
A scaffold for AI game development: 43 agents, 67 commands and 109 skills for Unity, Unreal, Godot and HTML5.
The uloop CLI and 21 skills let an agent build, test and run a Unity project, read logs and check the game in Play Mode.
Official Unity skill set for agents: editor control, builds, 2D and 3D, UI, URP, audio, multiplayer and monetization
22 skills for the full Claude Code project lifecycle: setup and task scope, code review, pre-push checks and session notes.
README in short
Twenty-one skills for the stages of a studio pipeline for Unity with templates and roles inside. Installation uses `.skill` files in Claude Cowork.