Build a focused first pass
Use your game context to prepare a compact design document with the core loop, first playable scope, and acceptance checks.
How it works

Describe the genre, camera or screen size, and what the player should notice or do. Start with a compact design document with the core loop, first playable scope, and acceptance checks.

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. The pitch says what the player actually does. Keep the decisions you want to carry into your next pass.
Get startedPick a starting point
Work on a compact design document with the core loop, first playable scope, and acceptance checks for a weekend game jam about repairing a lighthouse one room at a time.
Help me plan a compact design document with the core loop, first playable scope, and acceptance checks for a weekend game jam about repairing a lighthouse one room at a time. Give me two workable directions and a small test I can run. Check that the pitch says what the player actually does.

Work on a compact design document with the core loop, first playable scope, and acceptance checks for a strategy game where building a bridge changes the next turn for both sides.
Help me plan a compact design document with the core loop, first playable scope, and acceptance checks for a strategy game where building a bridge changes the next turn for both sides. Give me two workable directions and a small test I can run. Check that the main mechanic fits in one sentence.
Work on a compact design document with the core loop, first playable scope, and acceptance checks for a first game about collecting lost messages in a flooded village.
Help me plan a compact design document with the core loop, first playable scope, and acceptance checks for a first game about collecting lost messages in a flooded village. Give me two workable directions and a small test I can run. Check that the first playable slice fits the project scope.
Why SEELE
Use your game context to prepare a compact design document with the core loop, first playable scope, and acceptance checks.
Keep the same game scene and compare two approaches before deciding what to make.
Set one acceptance check for the next pass. The pitch says what the player actually does.

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

Turn one mechanic into a playable loop and test its goal, feedback, and rewards.

Give designers, artists, and developers one scene or asset sample to review together.
FAQ
AI Game Design Document Generator is a Seele AI workflow for creators who need to GDD outline, scope, mechanics, and production checklist. It turns a short intent into a structured prompt and production checklist.
Yes. Add the genre, style, target platform, and one constraint. The workflow turns that rough input into a clearer workspace prompt.
The page is designed to hand off into the Seele workspace so the output can continue toward a playable prototype, asset pack, or scene plan.
Describe the game, the moment the player sees or uses the result, and the constraint that matters most. Ask for a compact design document with the core loop, first playable scope, and acceptance checks.
Try it in a small scene or review it from the player camera. For the first example, check that the pitch says what the player actually does.
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 compact design document with the core loop, first playable scope, and acceptance checks.
Write a game prompt