以 EvonX 為例，如何用 AI 提示詞製作遊戲（無需編碼）

Most "make a game with AI" guides stop at "type a prompt and hope". This one is about the part that actually decides whether you end up with something playable: how you write the first prompt, how you test it, and how you edit it without breaking what already works.

I'll use EvonX, a browser-based AI game maker I work on, for the examples, but the workflow applies to any prompt-to-game tool.

1. Write the first prompt in five parts

One sentence is enough to get a first build. A better sentence has five parts:

1. Genre: match-3, endless runner, tower defense, idle tycoon
2. Theme: candy shop, space station, haunted forest
3. Goal: clear 20 levels, survive 3 minutes, reach 1M coins
4. Core rule: what the player does every few seconds
5. One twist: the thing that makes it yours

Example:

A tower defense game in a frozen harbour. Defend the lighthouse for 15 waves. Towers are fishing boats you place on the water. Twist: ice spreads each wave, so you lose space over time.

Compare that with "make a tower defense game". The second prompt forces the AI to guess four things, and it will guess the most generic option every time.

2. Play the first build before you change anything

The first build is a draft, not a result. Play it for two minutes and write down only three things:

• What is broken (a button that does nothing, a level you cannot win)
• What is boring (no reason to keep playing after level 2)
• What is missing (sound, a score, a lose state)

Fix broken first, boring second, missing last. Mixing them in one prompt is the most common reason AI edits go wrong.

3. Edit with small, specific prompts

Good edit prompts read like bug tickets:

• "Fewer moves on level 2, it is too easy."
• "Add a shield booster that blocks one hit."
• "Make the boss twice as big and slower."

Bad edit prompts read like wishes: "make it more fun", "improve the graphics". The AI has no idea which of fifty things you mean.

One change per prompt also makes it easy to undo when something breaks.

4. Check difficulty, not just visuals

AI tools are good at art and decent at code. Where they slip is balance: a level that cannot be won, or a curve that jumps from trivial to impossible. Play the first five levels yourself, or ask for a difficulty curve directly ("each level should need about 10 percent more moves than the last"). EvonX checks that each generated level is winnable, but you should still feel the curve with your own hands.

5. Ship it early

Share a link with three friends before you polish anything. Watch where they quit. That is your next prompt.

Prompt ideas to steal

• Word game: "A word search for a 5th grade science class, 10 words about the solar system, timer of 2 minutes."
• Idle game: "An idle coffee shop. Tap to brew, hire baristas to brew automatically, unlock a new drink every 500 coins."
• Runner: "An endless runner on rooftops at night. Collect lanterns, jump over chimneys, speed goes up every 30 seconds."
• Puzzle: "A sort puzzle with stacked coffee cups. Move cups so each column holds one colour."

If you want to try this workflow, EvonX has a free starter plan and runs in the browser. You can browse example games to see what a first build looks like before writing your own prompt.

What genre would you try first? I'd like to hear which prompts work for you and which ones fall apart.