Vibe coding for game devs

A vibe-coding tool will happily invent a game. It will not, by itself, invent the feel of one. This is a short stack for game developers who want the speed of a prompt without throwing away the engine they already know.

Start with something you can play

If the idea is still a sentence, do not open a blank Unity scene and ask an agent to "make an RPG." Ask for a slice you can finish in a weekend.

Rosebud AI is the blunt instrument: describe the game and it builds a playable browser project, with code, art, and sound in the same place. That is the right shape for a prototype you can send to a friend tonight.

GDevelop is the open-source alternative when you want a real engine and AI beside a visual editor, and you care that the project is not locked to one vendor.

If you already live in Unity, skip the detour and use Unity AI: an agent in the Editor, plus a CLI and an MCP server, so the same kind of coding agent you use on web apps can see a Unity project.

Put a coding agent on the real project

The prototype is not the game. Once the loop is fun, move the work into the repository you will ship.

Cursor and Claude Code are the two agents most game programmers already have open next to an engine. Aider is the open-source terminal option if you want the commits on your machine and you bring your own model.

Point the agent at the engine files. A second prototype that cannot merge is a trailer. Ask for one system at a time: player controller, save slot, dialogue trigger. Make it run in the editor before the next prompt.

Assets without a pipeline rewrite

Generated art is useful when it lands as a file your engine already imports.

Ludo.ai covers a lot of that surface: sprites, 3D, audio, and starter Unity scripts. PixelLab is the narrower tool when the game is pixel art and you need characters, tiles, and animations that match.

For 3D, Meshy and Tripo turn text or an image into a model you can export. Use them for props and blockouts. Do not expect a hero character to survive a close-up without a person.

Scenario is the team tool. It is built for a consistent style, and it exposes an MCP so a coding agent can call the same models instead of a person downloading PNGs all afternoon.

Characters that talk

Inworld and Convai are for spoken, reactive characters in a realtime world. Convai has plugins for Unity and Unreal. Treat the first dialogue as a prototype of the conversation, not the script you will ship. Generated lines wander. A content pass is still the job.

What not to outsource

Collision, camera, and the rules of the game are the game. An agent can draft them. You still have to play them. If a tool cannot show you the change inside the engine, it is not done.

Also leave pricing questions on the vendor site. This directory marks price as unknown until someone checks, because these plans move.

A weekend path

1. Write one sentence: who the player is, what they do, and when the session ends.
2. Build that sentence in Rosebud, or in GDevelop if you want the open-source engine from the start.
3. Play it. Cut anything you cannot explain to a person who did not see the prompt.
4. Recreate the loop in your shipping engine. Use Cursor or Claude Code on that repo, not on a parallel toy.
5. Fill the missing art with Ludo, PixelLab, Meshy, or Scenario, as files.
6. Add a talking character only after the silent version is fun.

The rest of the game-dev shelf is on the vibe coding for game devs page. If you ship with one of these tools and the listing is stale, the submit form is there for that.