Replace vague adjectives with observable moments
Instead of “make it smoother,” describe the moment: “When I release the falling tile, show which column it will enter before it lands.” Instead of “make it more fun,” say what decision should feel different. A useful correction points to an action and an outcome that you can reproduce.
Try a plain-language prompt
Example prompt: “Make a small single-player puzzle where I move one numbered tile left or right before it drops. Join equal numbers when they touch, and finish when the target number appears. If the board fills before then, show that the run ended. Put Restart near the board and clear every tile when I use it. Keep the next landing position visible while I choose.” No implementation language is needed; the example is a concept to generate and test.
Give feedback in one sentence at a time
Play until something surprises you. Record exactly what you expected, what appeared, and which prompt detail might explain the difference. Ask for one revision, replay the same moment, then decide whether the change fixed the issue. Avoid combining a new theme, faster movement, more levels, and altered scoring into one revision because the result will be difficult to evaluate.
If the game behaves in a way you cannot describe, capture the visible sequence in simple words and ask for a clearer cue or rule. You do not need to diagnose the code; you do need to verify that the player experience matches the instructions.
Questions about AI game design for non-programmers
Do I need to understand code to give useful feedback?
No. Describe the action you took, what you thought would happen, and what you saw. Specific player-facing observations can guide a focused revision.
What should I do if the generated version misses an instruction?
Test the same moment again and restate the missing behavior as an observable rule. Change one request at a time so you can tell whether the next version addressed it.