Build a focused first pass
Use your game context to prepare a rule sheet with inputs, game states, and expected edge cases.
How it works

Describe the genre, camera or screen size, and what the player should notice or do. Start with a rule sheet with inputs, game states, and expected edge cases.

Ask for two versions around the same scene or player action. Vary one choice at a time so you can compare the result.

Use a small scene or sample to check your choice. A first time player can see both options. Keep the decisions you want to carry into your next pass.
Get startedPick a starting point
Use a starting prompt from this tool and adapt it to your own game.
Design a no-code game logic flow for a puzzle roguelite where players combine elemental tiles to open routes and trigger hazards.

Work on a rule sheet with inputs, game states, and expected edge cases for a short platforming level that teaches one move before asking players to combine it with another.
Help me plan a rule sheet with inputs, game states, and expected edge cases for a short platforming level that teaches one move before asking players to combine it with another. Give me two workable directions and a small test I can run. Check that the learning step comes before the challenge.
Work on a rule sheet with inputs, game states, and expected edge cases for a replayable arena with two entrances and a clear way to recover from a mistake.
Help me plan a rule sheet with inputs, game states, and expected edge cases for a replayable arena with two entrances and a clear way to recover from a mistake. Give me two workable directions and a small test I can run. Check that the rules create different viable choices.
Why SEELE
Use your game context to prepare a rule sheet with inputs, game states, and expected edge cases.
Keep the same game scene and compare two approaches before deciding what to make.
Set one acceptance check for the next pass. A first time player can see both options.

Start with one action and one goal. Make a version you can play through once.

Test one direction in a small prototype and use the result to decide what to build next.

Turn a design exercise into something the class can play, compare, and discuss.
FAQ
Yes. It works for simple loops and more layered systems as long as the prompt explains the player verbs and design goal clearly.
No. Final implementation, testing, and integration still need engineering or tool setup work. The workflow is strongest for planning and handoff.
Include the player actions, game rules, success and failure states, and what the first prototype needs to prove. Edge cases and progression details also help.
Use it when the team understands the game fantasy but still needs to clarify how the system should actually behave in a playable form.
Describe the game, the moment the player sees or uses the result, and the constraint that matters most. Ask for a rule sheet with inputs, game states, and expected edge cases.
Try it in a small scene or review it from the player camera. For the first example, check that a first time player can see both options.
Yes. Pick one small scene or interaction and describe what the player should see or do. You can revise the prompt as the idea becomes clearer.
Bring a game idea to Workspace and work through a rule sheet with inputs, game states, and expected edge cases.
Write a game prompt