01
Write the one-sentence loop
Use this pattern: “The player repeatedly ___ so that ___ while ___ becomes harder.” Example: “The player rotates a tiny moon base to catch drifting repair drones while solar wind changes their paths.”
02
Define success, failure, and restart
Give the round a finish line. State what creates score or progress, what ends the attempt, what persists, and whether the next round should begin instantly or return to a menu.
03
Choose device and controls
Name portrait or landscape, touch or pointer, keyboard or gamepad, and the minimum supported screen. Explain whether one hand, two hands, shared keyboard, or a microphone is expected.
04
Describe the readable feedback
State how the player recognizes a valid move, damage, score, danger, cooldown, objective change, and failure. Sound and animation should support visible information rather than hide it.
05
Generate one complete prototype
Ask for a single polished level or endless loop. Avoid adding accounts, stores, multiplayer, procedural worlds, and a long story before movement, score, failure, reset, and performance work.
06
Play without reading the prompt
Open the prototype as a new player. Check whether the interface explains itself. Try wrong actions, repeated clicks, a small screen, lost focus, muted audio, and a restart after failure.
07
Request a measured revision
Replace “make it better” with evidence: “the first enemy arrives before controls are understood,” or “the touch button overlaps the score at 390 pixels.” Ask for alternatives and compare them.
08
Prepare a responsible release
Review licenses, rights, privacy, dependencies, analytics, hosting, accessibility, error handling, and security. Remove keys from client code, compress media, and test the deployed build.