How to Write Better AI Game Prompts
A prompt structure that gives game-building tools less room to guess.
Write prompts like compact design specifications: name the input, objects, rule changes, UI response and acceptance test, then revise one system at a time.
Replace adjectives with observable behavior
| Weak | Better |
|---|---|
| Make movement smoother | Accelerate to full speed over 0.25 seconds and decelerate over 0.15 seconds |
| Make it harder | Spawn one extra obstacle every ten seconds, capped at six |
| Fix the score | Add 10 only when the player touches a new coin; never count the same coin twice |
Use acceptance tests
End a request with what must be true: “After time reaches zero, movement stops, the final score remains visible and tapping Replay resets score, timer and objects.” That gives the model and you a concrete definition of done.
Debug with evidence
State the exact sequence, expected result and actual result. Avoid asking for several unrelated fixes. If a change fails twice, request an explanation of the relevant state flow before asking for another patch.
Features, pricing and terms can change quickly. Recheck the linked sources and current official terms before making a commercial or platform decision.