README

Claude Code Game Studios
  
    Describe a game. Claude Code asks a few questions, writes a one-page brief,
    and builds a playable browser game from it.
    
    Then you change it, grow it and finish it, one step at a time.
  



  
  
  
  


---

 Make me a game

Open Claude Code in a copy of this repository and say what you want:


/prototype a fishing game where the rare fish only bite at dusk


1. A few questions. One round, picked from the genre: the choices that
   shape the game, how it should feel, how it looks, how hard it is, the goal.
   Each has a usual answer, so "you pick" works. A vague idea ("a racing game")
   gets two or three one-line pitches to choose from first.
2. A one-page brief. design/game-brief.md: your words kept as you typed
   them, the look, the first minute, the challenge, the features and what is
   left for later. You read it and say Build it, or change something first.
3. A first build. A browser game in prototypes// that opens with a
   double-click: every figure drawn, no emoji art, no copy of another game, and
   not trivially easy. Your session builds it at its own effort ("build it at
   medium" is cheaper and thinner).
4. Checked before you get it. A few scripted key presses in a headless
   browser show it opens with no errors and responds; text that is too small,
   overlapping or off screen and screens that freeze are fixed in one round; and
   every line of the brief is marked built, missing or broken from the
   screenshots and the code, or not assessed when it could not be checked. Your
   play is the real test: the handover card says what passed, what is still broken
   and what was guessed, and ends "Not yet played by a person".

Then it is yours to play. After that:

- Change it by asking. Each change is checked against what you said to
  keep and to avoid, and each one you accept is a checkpoint you can go back
  to. Ask to tune it and it gains a tweak panel with a slider for every value.
- Share it. A clean copy without the panel and the working files, ready
  for itch.io or a link.
- Grow it. When you like it, it becomes a real web project (Vite and
  TypeScript, its values in data files, tests and a build), and you add to it
  one feature a sitting: say the next feature, and it is built, checked and
  committed. After every feature the same seeded run is played again and any
  change is shown to you. Stories (/create-stories, /dev-story,
  /story-done) only when you ask for them.
- Finish it. /cut proposes what to cut and a polish list, and a date
  when the game is to sell.

Already have a browser game? /prototype --from  brings a copy in as it
is, so it can be changed and grown the same way.

 What it has been shown to do

- The first build. In a blind comparison on three game ideas, the brief
  made from its questions was picked over a hand-written brief all three
  times. All six games built from the two kinds of brief were ones the tester
  said they would build on, so on the games t

Top issues

Discussions

Latest release

The story skills are rebuilt around shared helper scripts, a read guard stops whole-file reads of large design docs, the engine references move to Godot 4.7 and Unreal Engine 5.8, and no skill pre-approves every shell command any more. A minor release after 1.1.3.

 Highlights

- The main path is rebuilt. /start, /create-stories, /story-readiness, /create-epics, /dev-story and /story-done follow Anthropic's skill-authoring guidance: shorter, with rarely used branches in references/ and fixed steps handed to helper scripts, so the same question gets the same answer each time. /start works out t