Game Design Concept Prompt Template

ROLE: Game designer with shipped titles across indie and mid-budget studios — specialising in the GDD (game design document) phase where conceptual ideas become buildable systems, with a focus on what is actually fun to play and why. CONTEXT: Most game concept documents describe a world rather than a game. A world is not a game until it has a core loop — the repeating cycle of challenge, player action, and feedback that creates the compulsion to keep playing. The best game concepts can be explained in one sentence of core loop, then expanded into mechanics, then into content. Starting with world-building and hoping a game emerges is how projects fail. TASK: Write a mini game design document that describes a workable, buildable game concept with a clear core loop, defined mechanics, and an honest articulation of why this will be fun. RULES: • State the core loop in one sentence before anything else: "[Action] → [Consequence] → [Reward/Complication] → repeat" • Every mechanic must serve the core loop — if it doesn't, it's a feature, not a mechanic • Win/lose conditions must create meaningful tension without feeling arbitrary — explain the player psychology behind each condition • The "what makes it fun" section must name the specific psychological reward mechanism: mastery, discovery, collection, social comparison, narrative investment, etc. • Include a "scope reality check" — what is the minimum viable version of this concept that is still fun to play? CONSTRAINTS: Mini GDD format — this is a pitch document, not a full technical specification. 500–700 words. Clear headers. Specific enough that a developer could scope it, broad enough that it still invites creative iteration. EDITABLE VARIABLES: • [GENRE] — game genre (puzzle, platformer, RPG, strategy, simulation, horror, etc.) • [CONCEPT] — the core idea in one sentence • [PLATFORM] — target platform(s): mobile, PC, console, browser • [AUDIENCE] — target player (casual / hardcore / specific age / specific interest) • [TONE] — the aesthetic and emotional atmosphere you're aiming for • [INSPIRATION] — 2–3 games you'd cite as reference points or contrast points OUTPUT FORMAT: Concept statement (1 sentence) Core loop (written as: action → consequence → reward/complication) Why it's fun (specific psychological mechanism named) Core mechanics (3, each with: what it does, why it serves the loop) Win/lose conditions (with player psychology note) Art style direction (2–3 sentences with visual reference points) Target platform + audience fit rationale Scope reality check (minimum playable version) Risk / challenge (the one hardest design problem to solve) QUALITY BAR: A game developer reading this GDD should understand the game, want to play it, and be able to estimate a rough scope — and should be able to tell immediately if the mechanics actually serve the core loop or if they're just ideas bolted onto a concept.