How to make a game with AI and publish it, no code

Step 01Shrink the idea before you write anything

The most common reason an AI game goes nowhere is a first prompt that describes a dream game: an open world, crafting, online battles and a story, all at once. The AI starts all of it and finishes none.

Cut the idea down to one core action the player repeats. Good first games:

• tap to fight waves of monsters and buy upgrades (idle RPG);
• dodge obstacles and collect coins (runner);
• match, merge or sort things on a board (puzzle);
• answer questions against a timer (quiz);
• play cards against a computer opponent (card battler).

You can add the rest later. Look at the 20 winners of our Solana hackathon: the first place, IMPERIVM, is a card battler, the second, Asyq Atu, is a physics game where you flick knucklebones. Each one does a single thing well.

Step 02Write the first prompt

Open Create and write the idea. One or two sentences are enough; the platform asks a few questions about genre, style and setting, and from the answers it picks a starting template. That is why the new project is playable at once instead of being an empty screen.

A first prompt that works names four things:

1. The genre and the core action: "an idle RPG where a knight fights waves of monsters".
2. The goal: "the player upgrades the sword and armor to reach a boss on wave 10".
3. The controls: "tap to attack, upgrades bought in a shop".
4. The look: "dark fantasy, pixel art, night forest".

Put together: "An idle RPG where a knight fights waves of monsters in a night forest. Tap to attack, coins buy sword and armor upgrades in a shop, a boss waits on wave 10. Dark fantasy pixel art." That fits on one line and gives the AI everything it needs for a first version.

Step 03Build one mechanic at a time

You land in the AI coder with a live preview next to the chat. From here the rule is simple: one change per message, then play it.

Prompts that work:

• "Make the jump higher and the fall faster."
• "Add a shop where the player buys sword upgrades for coins."
• "Add a daily quest: defeat 20 monsters, reward 100 coins."
• "When the knight is hit, flash him red for half a second."

Prompts that don't work as well:

• "Make the game better." The AI has nothing concrete to change.
• "Add a shop, quests, a boss and multiplayer." Four changes at once: when one breaks, you cannot tell which.

Say what you see, not how to code it. "The jump feels floaty" is a better prompt than instructions about gravity variables. The AI knows the code, you know how the game feels.

When you ask for something the platform already has, such as a leaderboard, a store or quests, the AI coder installs the ready system instead of writing a new one. That matters: a store written from scratch can keep prices in the browser, where a player can change them; the ready one checks every purchase on the server.

Step 04When the AI breaks something

It will happen. A change fixes one thing and breaks another, or the preview stops loading. Three habits keep this cheap:

• Every change is a version. Open the version history and go back to the last one that worked. Do this before you try to argue the AI out of a broken state.
• Describe the symptom exactly. "After I buy an upgrade, the coin counter shows NaN" gets fixed in one step. "The shop is broken" takes three.
• Pick the mode for the job. The AI coder has a Fast mode for small edits and a Standard mode for bigger features. A new system or a tricky bug goes better in Standard.

Step 05Add art and sound

Placeholder shapes are fine while you tune the mechanics. Art comes after the game is fun, not before. When you are ready, make sprites, backgrounds and icons in the AI image generator, and sound effects and music on the Audio page, then ask the AI coder to put them in the game.

Keep one style across the game: write the same style words in every image prompt ("pixel art, dark fantasy, limited palette"), otherwise each picture looks like it came from a different game.

Step 06Test it like a stranger

Before you publish, give the test version to a friend and say nothing. Watch where they get stuck. AI does not decide whether a game is fun or whether level 3 is too hard; people do. Play it on a phone too: most players will open your link on one.

Step 07Publish the game

Publishing has two steps: you deploy the build you tested, and the game goes live at its own address, {id}.idos.games. The test copy stays at {id}-dev.idos.games, so you can keep experimenting without touching what players see. A rollback is one click in the version history. When you are ready for strangers, list the game in the idosgames.com catalog. Details: publishing and sharing.