AI Game Dev
is a tool in your hands, not a developer you hired.
clears away boilerplate , draft art, dialogue and translation. Decide what to ask for and what to check, then build the smallest working piece first.
Start from a minimum playable game
- One rule
- One screen
- One goal
A minimum playable game — an — is not a demo or a . It is the smallest thing that a stranger can pick up, understand in ten seconds, and enjoy for two minutes. One mechanic, one screen, one clear goal. If you can't name the single moment that makes it fun, the game is not small enough yet.
Publishing that small thing is what changes everything. Real players do what you never predicted, quit where you thought they'd stay, and tell you in one day what six months of solo work would not. Shipping is not the end of development — it's the first honest feedback you get.
Decide your publishing date before you decide your feature list. Then cut features until they fit. A game that ships in three weeks and gets played beats a masterpiece that never leaves your machine.
A game runs in two parts — client and server
Everything a player sees and touches is handled by the running on their device. Connecting players and keeping records safe is the job of a somewhere on the internet. Thinking of them separately makes it clear what to hand to AI and what to check yourself.
Client
Drawing the screen, keyboard and touch input, sound, and — the part that actually runs the game every . For a web game the is the , so it opens from a link with nothing to install.
Describe the behavior you want — controls, collisions, scene changes — and let AI write the . Judge the result by playing it yourself.
More on game clientsServer
Accounts and sign-in, save , , chat, for multiplayer — the part that ties many people into one game. Most are run as .
- Docker
Get and a first draft of your score from AI, but a person must review , cost and data retention.
More on game serversA single-player web game is complete with just a client. When you need saves or a leaderboard, look at the of a game such as before standing up your own server. Running servers can wait until your game has players.
What AI actually does in game development
Not "it makes the game". These are the specific jobs where handing work to AI genuinely pays off.
The four-beat loop of building with AI
- 1 Describe Write exactly what should move and how — keys, speed, how you win and lose.
- 2 Generate AI writes the . Ask for one feature at a time, not the whole game at once.
- 3 Play it Run it and find what feels wrong. Copy any exactly as it appears.
- 4 Report back Pass on what you saw and the exact error, and ask for a fix. Repeat these four beats in small, frequent loops.
Six jobs worth handing to AI
What a good request looks like
A vague request gets vague code back. Include the behavior, the conditions and how you will check it, as in these examples.
Make a game in a single file. Pressing Space makes the character jump, and obstacles come in from the right, getting faster. On a collision, show the score and restart with R. On phones, tapping the screen jumps.
Controls, rules, the end condition and mobile are all stated. Whatever you leave out, AI fills in on its own.
If I press jump twice quickly, the character jumps again in mid-air and flies off the screen. Before fixing it, explain which code causes it.
It says how to the bug and asks for the cause first. Reading the explanation lets you catch a fix aimed at the wrong place.
this game to . Before uploading, check that the layout meets the rules, and give me the play address when you're done.
With the Cadeplay installed, an AI tool follows the whole procedure from this one sentence — packaging, uploading and the check.
People who understand how a picks its output get dramatically better results from the same tool. They know why the same request gives different answers, why a long conversation gets worse instead of better, and why adding one example changes everything. Without that, you are pressing buttons and hoping.
You don't need months. The beginner track on this site covers what a model is, why it answers in , and how to write a request that gets what you meant. Come back here after that and every page will read differently.
Start with AI basicsWhat AI cannot do for you
An AI is a machine running over . It has never been bored, never felt a game click, never wanted to play one more round. Everything below depends on exactly that.
Once it's playable, put it on Cadeplay
is a web game where games play instantly in the , with nothing to install. Upload your game as a single and you get a permanent address, with saves and available too. It's free, and you keep the rights to your game.
Set up the skill and token once, and "deploy it" is all you say
The Cadeplay is a bundle of instructions that teaches an AI tool the entire publishing procedure. Once it's installed, the tool zips the build, uploads it, waits for the check and makes it live — in order — then reports back.
Deploy this game to Cadeplay
- Zipped from inside the
- Uploaded — the automatic check passed
- the new build to live
- Drafted the store description
Your play address is ready — open it now!
What to do this week
- 1Write down, in one sentence, the single moment that makes your game fun. If you can't, you don't have a game yet — you have a setting.
- 2Pick a publishing date three to four weeks out. Write it somewhere you'll see it.
- 3Ask an AI to draft the as , then run it. Not the whole game — just the one fun moment, playable.
- 4Put it in front of one person who has never seen it. Say nothing. Watch where they hesitate.
- 5Fix the one thing that made them hesitate. Then ship it — once the and are set up, " it" gets you a play address you can send as a single link.
Build a game right here, right now
Reading alone won't give you the feel. Type the game you want below, and the AI tool writes the — play it right beside the chat. To keep going on a bigger screen with the code in view, practise in the menu.
Practise in Vibe Coding