Claude Game Studio

How to make a game with AI using Claude Code

To make a game with AI, give Claude Code a brief, build from its design, then play and fix the result.

make me a AAA-looking FPS: samurai in a burning village

65.3 minof Claude Code

$8.05initial build usage

Play Burning Thatch

Start in your own folder

Follow the kit setup steps for the first-person starter and assets. Open Claude Code in an empty project folder and copy the sentence above. Ask it to save the design as design.md before it builds, so you can change the setting, the main action and the win condition together.

Read design.md. Build the game it describes as one HTML file. Play a whole round, reach win and loss, and check restart before handing it over.

New to Claude Code? Anthropic's quickstart covers installation and opening a project. Its instruction is direct: Start your first session. The plugin documentation explains how packaged skills load into that session. Once your project opens, follow the same six steps below.

The build clock

Burning Thatch reached its first playable build 11.7 minutes after setup. The next recorded events concern the sword grip, the test player and the lighting.

Burning Thatch event timesSetup at zero, first play at 11.7 minutes, repair report at 38.2 minutes, lighting repair at 65.3 and final play at 65.4 minutes.0 min65.4 min
  1. 0.0 min

    The sentence goes in

  2. 11.7 min

    First playable build

  3. 38.2 min

    Grip and playtest faults found

  4. 65.3 min

    Lighting fault found and regraded

  5. 65.4 min

    First-pass final play

Events from the 11 November build, rounded to a tenth of a minute from setup. These are event timestamps; the separately logged run duration is 3,917 seconds. Read the exact times and repair notes.

The run, step by step

1

Type one sentence

That is the whole brief. With the kit installed, the sentence goes straight into Claude Code.
claude
> make me a AAA-looking FPS: samurai in a burning village
2

Claude Code writes the design first

It turns the sentence into a one-page design: premise, the first second on screen, the one verb, the loop, scope, look, sound and three things a stranger must be able to do. The game is built from that page.

Premise

You are the village's night watchman. When raiders put the roofs to the torch you take the old blade from the shrine and walk the burning main street until the last of them is down.

Get the template this page follows
3

It builds from a starter that already runs

Burning Thatch starts from the kit's first-person starter, a small game that already runs. The raiders, their animations and the katana come from the kit's asset library.
starter: first-person
weapon: katana (scanned model)
enemies: Raider, Runner, Torchbearer
result: one HTML file (current build 7,321,550 bytes)
4

The first playable build lands at 11.7 minutes

The first-play timestamp is 19:17:10 UTC on 11 November, after setup at 19:05:27. From there a scripted player runs the game in a browser. The next repair entry reports the wrong sword grip, reload assumptions and two lost rounds.
19:05:27 · setup
19:17:10 · first play
19:43:40 · grip and test faults reported
20:10:48.198 · lighting regrade
20:10:48.889 · final play
Open the recorded events
5

Three things broke, and checks caught them

  • The katana model's grip point sat at the guard, so the player and the raiders held the blade.
  • The playtest looked for a reload and a weapon swap. A sword has neither, and its scripted player lost the round twice.
  • A picture check scored the look 3 out of 10 because the lighting had turned the street orange and black. Claude Code switched to a cool moon fill and lower contrast.
grip: katana held by the blade
playtest: reload tested on a sword, player lost twice
look: scored 3/10, street orange and black
recorded repair: cool moon fill, lower contrast, higher bloom threshold
6

You play it

The result is one HTML file that opens in a browser. Play Burning Thatch from this page, then change it by telling Claude Code what to change.
Play Burning Thatch

Ask for a repair you can check

Burning Thatch's later bell-objective revision with burning roofs, a shrine gate and a sword entering from the right
Later bell-objective revision. Compare the street shadows (1) and blade glare (2) in a matched capture. The 20:10:48 UTC repair entry records cool moon fill, lower contrast and a higher bloom threshold.

Check the hand and blade

The repair entry says player and raiders gripped the blade. Ask for the grip point to sit on the hilt, then look at both the first-person hands and an enemy's sword during an attack. A model loading successfully does not establish the right attachment.

Test the actions this game has

A sword has no magazine to reload. Ask the agent to replace reload and weapon-swap assertions with swing, hit, damage, three-wave completion and restart checks. Run the round again after changing enemy health or wave size.

Look at the playable view

The visual review reported orange-and-black lighting and a bloomed blade. The recorded repair used cool moon fill, lower contrast and a higher bloom threshold. Ask for a fresh frame from the same camera after each change so you can compare the street and sword.

Read the original repair entries and download the design. Keep each requested fix tied to an observable result when you adapt this game.

For a first-person browser game, include click-to-start and Escape in that check. MDN's Pointer Lock guide explains why mouse-look needs a user gesture and how Escape releases it. Ask the agent to verify that clicking back into the game restores camera control.

Play the other kit games and compare their build times and API costs. For other approaches to browser 3D, see the portal's WebGL games.

Choose your next game

Shape a brief before building with the Claude game design skill. Download its instructions and try a small delivery game whose carrying limits and deadline you can change.

Build a smaller example you can edit from start to finish: a browser delivery game, a 3D courtyard with collision boxes, or a horror encounter with a warning and escape route. Each guide includes its playable game and HTML source.

Questions

Can AI make a game?

Yes. A coding agent such as Claude Code can write, run and fix a game's code from a description. On this page it built Burning Thatch, a first-person sword game, from one sentence in 65.3 minutes for $8.05, and you can play the result.

How long does it take to make a game with AI?

Burning Thatch reached its first playable build 11.7 minutes after setup. The initial run took 65.3 minutes in total. Later refinements are separate.

How much does it cost to make a game with AI?

Burning Thatch’s initial build cost $8.05 in model usage at 3 November 2026 prices. The kit is a separate $29 a year purchase. For Burning Thatch, that is $37.05 for the kit's first year plus this one initial build, using metered model usage; Claude subscription billing depends on your plan.

Do I need to know how to code to make a game with AI?

You do not write the code. You describe the game, play what comes back and ask for changes. You do need Claude Code running in a terminal, because the agent works in a folder on your computer.

What can go wrong when AI makes a game?

In the Burning Thatch run, checks found three faults before the end: the sword was held by its blade, the playtest looked for a reload a sword does not have, and the look scored 3 out of 10. The run records a lighting regrade with cool moon fill, lower contrast and a higher bloom threshold.