Describe your idea. Claude Code interviews you, writes a one-page plan you approve, builds a playable prototype, tests it, and asks you to play it before it polishes. Build it as a browser game you can play and share today, or as a project in your engine: Godot, Unity, Unreal or GameMaker.
You stay in control. The AI is only ever there to assist. It doesn't decide what your game is: every important choice comes back to you as options, and nothing gets built until you say go.
Each game below was built by Claude Code from the same prompt, for a different person: a family making their first game, a developer starting a real project, someone who has never finished one. Play them, then read how each one was made: the interview, the plan they approved and what they changed at each check-in. These eight are browser builds so they can play right here; the prompt builds in Godot, Unity, Unreal or GameMaker just as well if you'd rather work in an engine.
2D
Designed by The Okafor Family · First game ever, made by a parent with their 9-year-old
Bake in two ovens and serve each cat before its patience runs out. Unlock muffins and fish-shaped cookies, and wait for Biscuit at golden hour.
2D
Designed by Priya R. · Shipped a small jam game; wanted to test whether an idea is fun
Eat cyan rocks to grow, dodge pink ones, and spit mass to shrink when you're too slow. Survive two comets, then crack the Final Comet.
2D
Designed by Sofia Marquez · Followed tutorials; wanted to learn how games are made
Turn mirrors to bounce the lighthouse beam into every lantern. Ruby, sea-blue and green glass tint the light, and each colored lantern wants its own.
2D top-down
Designed by Dana & Jules · Shipped something small; pitching it at a local game night
Drift around the ends of the aisles, smash cereal pyramids for a boost (and a second of WOBBLE!), and beat three rivals with fixed, fair speeds.
2D
Designed by Ray H. · Backend developer; the start of a real game he'll build on
Place pebble gnomes, pepper gnomes and the honey flower that only slows. Speedy slugs dodge everything else, so honey earns its place.
2D
Designed by Theo · Started games but never finished one
Crawl up pots, across the underside of the bench and over giant flowers to deliver every letter. Hide when a bird's shadow grows.
2D
Designed by Kenji Watanabe · Tinkered with tutorials; making it to show friends
Dash and swing your pizza peel through five floors, stack toppings on the pizza on your back, and deliver it to a dragon who can smell it.
3D
Designed by Marcus Bell · Three abandoned Unity projects; the start of a real game
Glide through a toy-like house, ride the warm air from glowing heater vents to climb, and fly out the attic window. You never crash out.
You paste the prompt into Claude Code or Cursor in an empty folder. From there it runs like working with a small studio: you're the designer, it's the builder.
Three short batches of questions: about you, your game, and how you want to work. It repeats your answers back and waits for your OK.
You decide: the idea, the one thing it must have, the look, how often it checks in, and how much it explains.
A one-page design: the core loop, controls, how a run builds, and a list of what it won't build yet. If you've started games but never finished one, it says so and proposes a small slice you can actually finish.
You decide: every open choice comes back as two or three options. No code until you say go.
It builds the game the way you chose: one HTML file that plays offline on phones and computers, or a project in your engine. Then it tests everything it can run, a bot playing in the browser at phone and laptop sizes or through your engine's command line, and fixes what's broken.
You decide: browser or engine is your call in the interview. It tells you plainly what it couldn't test, and a bot can prove the game works, but only you can tell whether it's fun.
It stops and asks you to play for a few minutes: what felt good, what felt off, and the one thing you'd change. Your answers drive the next pass.
You decide: in every demo here, this is where the biggest improvements came from.
A README with every call it made on your behalf and how to change it, the five settings worth tweaking, a checklist for watching a real person play, and three ready-to-paste prompts for your next features.
Pick it back up anytime: a log file means "Read PROTOTYPE_LOG.md and continue" resumes where you left off.
Autopilot: approve the plan, then it builds through. Standard: plus your playtest. Hands-on: a look at every milestone.
Just build it, explain my calls, or teach me as we go: a plain-language note on each system with an optional change to try yourself.
This is the real prompt's opening interview: the same three batches, the same questions, and the same profile it reads back to you before anything gets built. It runs right here on the page. There's no AI behind it, and nothing you type leaves this page.
Ready to build it for real? Paste the prompt into Claude Code or Cursor and it opens with these same questions. Copy your profile to have your answers ready.
Describe the game you've always wanted to make. Claude Code interviews you, writes a plan you approve, builds it, tests it, and asks you to playtest before it polishes. You make every creative call.
It makes prototypes, not finished games: a first playable version to find out whether your idea is fun. Every run designs its own version of your idea, so your game won't match these demos.
Each prototype was built by Claude Code running the prompt, for an example person whose interview answers and check-in feedback we wrote, the way a real buyer would. Everything on the AI's side is unedited: the interview questions, the plans, its replies at each check-in, and the game code. The game files you play are exactly what it produced.
Turn someone you love into the star of a 3D holiday sleigh race, with your own message waiting at the finish line.
GameDev Tutor is a structured AI tutor that teaches you to build your game in Godot, Unity or Unreal. It never writes your code.
GameDev Tutor on itch.io · $5+