Creators 6 min read
How AI games are made: one prompt to eight agents
Arkanoid Neon started as one sentence in Swedish, while other creators describe longer builds, with agents splitting the work and a human setting the direction.
On this page
Arkanoid Neon started with one request in Swedish for a good-looking Arkanoid game, while other creators describe much longer builds with several agents and tools such as Claude Code, Codex and Cursor.
Every story here comes from the creators, through the Vibe Jam 2026 submission form as summarized in our catalog or through their own READMEs, which we link wherever we quote them.
One sentence, one game
The shortest builds start and end with a single request. Arkanoid Neon is a neon brick breaker, and Jack-c3l2w’s README says Claude Opus 5.5 built the whole thing through Claude Code, from the code and graphics to the sound, music and levels.
The request really was one sentence in Swedish, “bygg ett riktigt snyggt Arkanoid-spel som jag kan spela på min dator”. In English, that’s “build a really nice-looking Arkanoid game I can play on my computer.”
Little Flock, a multiplayer sheep-farming game, went bigger in one pass. “This game was created one-shot by GPT 6 Astra in Codex, using a single /goal run,” its creator, songkeys, writes in the README.
That one goal covered the 3D world, the game systems, a multiplayer server, artwork, audio and deployment. The prompt tells the agent to solve problems on its own until the end, without the creator stepping in, and asks for a result that astonishes.
Some one-prompt starts just keep growing. Hollow Crown is now a pixel RPG with five classes and a three-stage boss, and its creator, rehan-remade, traces it back in the README. “It started as a single prompt: animate a pixel-art wizard casting a spell, in pure code.” The README also adds “No hand-drawn assets.”
Four prompts and a second opinion
Chess3dastra publishes every prompt it took, which makes it a handy one to learn from. Its creator, yortch, built it in the GitHub Copilot app as a test of GPT-6 Astra, and the README lists all four.
-
“Build a 3D Chess that I can play against computer”
-
“looks great, add a 2D view”
-
“/rubber-duck implementation”
-
“Implement all 3 suggestions”
About 41 minutes passed from the first response to the last. The third prompt asked a second, independent agent to critique the code with nothing but the source files, and it found three problems. The most serious was that if WebGL failed to start, the whole board vanished, even in the 2D view.
The README is open about what still got through, too. After playing the live game, the creator spotted that the 3D knights weren’t turned sideways like the 2D ones. Neither the model nor the review pass caught it, so in the end it took someone who knows what a chess board looks like.
Days, weeks and years
According to the creators, the jam builds took anywhere from days to weeks.
| Game | Tool | Build time, per the creator |
|---|---|---|
| Shoot or Die | Claude Code | A day and a half on game, server and bug fixes, then a day and a half on polish and deployment |
| Kanso | Codex | About a week |
| Doctrine | Cursor | About two weeks |
| Rift Wars | Not named | Under 15 days, one developer |
| Frenchieland Frenchies | Claude Code | About three and a half weeks |
Some ideas waited a lot longer than their builds did. Doctrine’s creator says the idea had been in their head for years, and Frenchieland Frenchies came after more than three years of thinking about it.
Kanso, the week-long build, placed ninth and won the jam’s Most Zen award.
Splitting the work
Some creators split the job between models or agents, and each one gets its own lane. Ombres goes the furthest, since its README describes about 35 hours of autonomous agent time, run as multi-agent workflows in Claude Code.
The README lists eight agents, one per area, covering simulation, bots, world rendering, birds and effects, network and phone app, audio, narrator and computer UI. It’s close to how a human team splits up a codebase, with each agent writing only in its own folders and filing requests when it needed a change somewhere else.
A human still set the direction, though. Brieuc Crosson wrote the brief, supervised and built the deployment, and one of the calls the README lists, asking whether the missing anti-aliasing was intentional, led to a fix. In the words of the README in briossant’s repository, “No line of code in this repository was written by a human, but the project is not human-free.”
Others split the work by task.
-
BoneCrawler had Claude, ChatGPT and Codex write the code while Gemini helped plan, and the creator directed the scope and tested the results.
-
Cybertaxi used Codex for the game, Suno for the music and ElevenLabs for the spoken dialog.
-
VideoVideoGame used Claude Code for the game and Seedance for more than 100 video scenes, with images from the new GPT image model and Nano Banana 2.
-
Survive Coders was “Built with Claude Code (Claude Opus 5.5) as a pair programmer; commits carry Co-Authored-By trailers,” according to travisstephenfraser’s README.
Other creators keep everything in code. Pro Skater: The Warehouse has a neat take on it, with Python scripts in Blender that build every 3D asset, from the skater to the whole park. The creator walks through the process in 3D-Stories’ README.
It doesn’t even ship with a sound file, because the game synthesizes its audio in GDScript when it starts.
Casa de Gemas left all the code to the model. It “was built entirely through conversation with Claude Opus 5.5 in Cursor — no code written by hand,” according to deepujain’s README.
Who’s doing the typing
The creators range from people who hadn’t coded in decades to working game designers, going by how they describe themselves in their jam entries.
-
Rainy Day Sort’s creator hadn’t written code since around 2001 and used the project to learn vibe coding by doing, with Claude Code and Gemini.
-
The Lighter Path’s creator says they couldn’t have made it without vibe coding, since they aren’t an engineer.
-
Shade Chasers’ creator only started learning Three.js days before the jam was announced.
-
Floppy Brawler’s creator is a web developer who uses AI every day at work. The game placed 13th.
-
Shoot or Die’s creator is an experienced UEFN and Unity developer who’d never made a Three.js game before.
-
BEATBACK’s creator is a game designer with seven years of experience, who describes AI as a collaborator that amplifies a designer’s taste.
Mobius Strip’s creator says they used AI like a brush rather than a shortcut, on art, animation, audio and polish, which are the areas they say they’re weaker in.
What went wrong, and what went right
The entries are pretty candid about what went wrong. Floppy Brawler only exists because the very first output from Claude, on day one, inspired the project. Oddly enough, its creator now thinks that early version looks terrible.
Ranger Danger’s creator tried several one-shot ideas and kept the most fun loop, while Sea Control - Cold War Arena added multiplayer as a later step.
Frenchieland Frenchies’ creator calls it unfinished but a start, and says their kid enjoys it.
In Code Rage the core loop is deciding which glitch to fix, an idea that came from AI-coded projects shipping with odd glitches where a bug and a feature are hard to tell apart.
Hollywood Link’s creator, for one, was surprised at how reliably AI produced good quiz questions for the linked format they’d designed.
Made something yourself? The submit form has a “How you made it” box for stories like these, and for a first game there’s how to make a game with AI or the prompts guide.
Games in this post
Chess3dastra
Play chess against a computer opponent on a 3D or 2D board.
Ombres
Steer a giant bird whose shadow paints the desert; biggest territory at nightfall wins.
Arkanoid Neon
Bounce a ball off a paddle to clear glowing neon brick levels.
, Online multiplayerlittle flock
Tend a shared flock of sheep on a cozy farm with other players.
, Phone friendly , Online multiplayerFloppy Brawler
Fight ragdoll-style opponents in a wobbly, physics-driven brawler.
, Phone friendly , Online multiplayerShoot or Die
Grab a gun, shoot rival players, and be the last one standing.
Keep reading
All posts
Guide · 18 min
Make a Gaussian splatting game with Blender 5.3
In Dustlight you're a small paper-lantern spirit on a sky island at night, and the embers you find pull its landmarks back together out of drifting dust. We built that world from Gaussian splats in Blender 5.3, starting from drawings Codex made, and none of it came from a scan.
Jams · 7 min
AI Browser Game Jam: what four editions built
Rogue Memory turned Ghost in the Machine into a first-person maze where you play a deleted AI, and Plug & Prosper made Charge a puzzle about power. Four editions of Focaccai's jam have left four pretty different winners.
