Build a neon maze game with Claude in four prompts
A playable 3D maze game where you eat dots and dodge ghosts, made with Claude in R3's terminal in four plain prompts: each prompt, what it added, then publish.
This is how Neon Maze was made: with Claude, in the terminal inside the R3 app, in four short prompts. Nobody wrote a line of code by hand.
The prompts below are what was typed, typos included (only the name of the arcade game it was modelled on is replaced). You don't need perfect prompts. You need to say what you want, look at the result, and ask for the next thing.
Before you start
- Open the terminal. Click Terminal in the navigation (the
>_icon). A panel opens and Claude starts by itself, already connected to your R3 account. The first time, Claude asks you to sign in with your own Anthropic account: Claude in your terminal walks you through it. - Keep the editor beside it. Claude's changes appear in the editor as it works, so you can watch the game being built.
Prompt 1: make the game
hey claude - can you make me a 3d maze game?
Claude reads R3's docs, makes a new project (now called Neon Maze) and builds it:
- a floor, the player and four ghosts (red, pink, cyan and orange);
- a Code component that runs every frame: it builds the maze with its walls, pellets and power pellets, moves the player, and gives each ghost its own way of chasing you;
- small Code components for swipes on a phone and for restarting;
- a How to play help, behind R3's own ? button.
It then starts the game in your editor, takes a picture to check it works, and gives you a preview link.
While it was working, one more message asked to watch along. It is not one of the four prompts, because it changes nothing in the game:
can you have the project open in the editor so i can see the progress please?
What to look at: before you press Start, the scene is only a floor and some spheres. The maze is built by the code when the game starts.
Prompt 2: sounds, and turns that wait for a gap
ok - can you create some sounds please for the maze game? and make it so it 'queues' the keypresses - example - if i hit a key it will go the direction if it passes a hole (do you understand what i mean?)
Claude makes eight new 8-bit style sounds with R3's sound tools (waka, power pellet, eating a ghost, death, a start jingle, the siren, frightened ghosts, level clear) and plays them from the game code.
It also does what the prompt describes: press a direction early and the player keeps going, then turns at the next opening that way. A small arrow next to it shows the turn it is waiting to take.
Tip: saying what you want it to feel like ("if i hit a key it will go the direction if it passes a hole") works better than guessing at how to code it.
Prompt 3: a kid's feedback
The first player to try it said it was too fast and there were too many ghosts. One prompt fixed both:
ok - can you make it so if i pres 1,2,3,4 - then it has 1,2,3,4 enemies - and if i press - and + it increases . decreases speed?
- 1 to 4 sets how many ghosts play.
- - and + slow the game down or speed it up, from half speed to double.
The top of the screen shows the number of ghosts and the speed, so you can see what each key did.
Prompt 4: a follow camera
Sent while Claude was still on prompt 3, and it picked it up in the same go:
ok - and another thing - could you make it if i press 'c' then it goes into camera follow mode and follows the player from behind and above?
Press C and the camera sits behind and above the player and turns with it. Press C again for the view of the whole maze.
Play it
In the editor, start Code and start Audio (the buttons at the top), then click the scene so it gets the keyboard. Steer with the arrow keys or WASD, or swipe on a phone.
Share it
- Preview: Claude already gave you a preview link. It shows the project as it is now and works for 7 days.
- The share picture: the camera button in the editor takes a picture of what the project's camera shows. That picture is what link previews and your live page show. Set it while the game looks good.
- Publish: in the Deploy panel, press Publish to give the game a public link. See Publishing & Going Live.
Tips
- Be specific about what you see or want. "Too fast, too many enemies" turned into "1 to 4 enemies, + and - for speed".
- One thing at a time, then look. Each prompt above asks for one or two things, and each time the game was tried before the next ask.
- Let someone else play it. The best prompt here came from watching someone else play.
- Ask Claude to explain. "What did you change?" or "how does the ghost chasing work?" are good prompts too.