← Cheatsheets
Tags: game-design-document, gdd, game-design, planning, design-doc, documentation, beginner, game-dev
Last updated: 2026-06-27
Game Design Document (GDD) Cheatsheet
What Is a GDD?
A Game Design Document (GDD) is the blueprint for your game. It describes what the game is, who it’s for, how it plays, what it looks like, and how it’s built. Think of it as the single source of truth that keeps your team (or just you) aligned from concept to ship.
For vibe coders, the GDD is doubly important: it gives your AI assistant the context it needs to generate coherent code, art prompts, and design decisions throughout development.
Why Write a GDD?
| Benefit | What It Means |
|---|
| Clarity | Forces you to define scope, mechanics, and constraints before writing code |
| Scope control | A written feature list is easier to say “no” to than an exciting idea in your head |
| AI context | Paste sections into your AI prompt so it understands your game’s goals |
| Team alignment | Everyone reads the same doc — artists, programmers, sound designers |
| Pivot record | When you change direction, the old doc becomes a reference of what was tried |
| Publisher ready | Investors and publishers expect to see a GDD before they commit |
The Vibe Coder’s GDD Workflow
- CONCEPT → “I want to make a fishing RPG with crafting”
- PROMPT AI → “Write a one-page GDD for a pixel-art fishing RPG”
- REVIEW → Read the output. Does it capture your vision?
- ITERATE → “Add a weather system that affects fish spawns”
- EXPAND → Prompt for each section in detail
- REFER BACK → When coding, refer to the GDD section for the feature
Core Sections of a GDD
1. Game Overview
- Working title — placeholder name for the project
- Tagline — one-sentence pitch (e.g. “Stardew Valley meets Dark Souls”)
- Genre — RPG, platformer, roguelike, simulation, etc.
- Platform — PC, console, mobile, web
- Target audience — casual, hardcore, kids, adults
- USP (Unique Selling Point) — what makes your game different
- Elevator pitch — 2-3 paragraphs summarising the whole game
2. Core Loop
- Primary loop — the 5-30 second action the player repeats (e.g. “move → fight → loot → level up → move again”)
- Secondary loop — the 5-30 minute meta-progression (e.g. “complete dungeon → return to town → craft gear → next dungeon”)
- Tertiary loop — the 5-30 hour overarching journey (e.g. “clear all dungeons → defeat final boss → credits”)
- Player motivation — why the player wants to keep looping
3. Game Mechanics
| Category | Examples |
|---|
| Movement | Walk, run, jump, dodge, swim, climb, fly, grapple |
| Combat | Melee, ranged, magic, stealth, parry, block, dodge-roll |
| Progression | XP, levels, skill trees, stat upgrades, unlockables |
| Crafting | Recipes, materials, workstations, quality tiers |
| Economy | Currency, shops, trading, auction house, bounties |
| Exploration | Map, secrets, fast travel, discoverable points of interest |
| Puzzle | Lock-and-key, logic, environmental, timing-based |
| Social | Co-op, PvP, trading, guilds, chat, leaderboards |
4. Story & Narrative
- Setting — world name, time period, geography, mood
- Protagonist — name, backstory, motivation, personality
- Antagonist — who/what opposes the player and why
- Supporting cast — NPCs, quest givers, companions, vendors
- Main plot — act structure (3-act, 5-act, episodic)
- Side content — optional quests, collectibles, lore entries
- Tone — serious, humorous, dark, whimsical, satirical
- Dialogue style — voiced, text-only, branching, reactive
5. Art Style
- Visual direction — pixel art, low-poly, hand-drawn, 3D realistic, cel-shaded, minimalist
- Colour palette — reference palette (hex codes or mood board links)
- Reference games — “like Hyper Light Drifter meets Hollow Knight”
- Character art — proportions, rigging style, animation count
- Environment art — tile size, parallax layers, lighting approach
- UI style — diegetic, flat, skeuomorphic, minimal
- Resolution / aspect ratio — 16:9, 4:3, 1920x1080 target, pixel-perfect scaling
6. Audio
- Music style — chiptune, orchestral, ambient, synthwave, licensed
- Sound effects — UI clicks, footsteps, attacks, ambient, weather, creature calls
- Voice acting — full VO, partial (grunts/tags), none
- Dynamic audio — adaptive music layers, distance-based attenuation, reverb zones
- Tools — FMOD, Wwise, Unity Audio, sfxr, bfxr, Audacity, LMMS
7. UI / UX
- HUD layout — health bar, stamina, ammo, minimap, quest tracker, hotbar
- Menus — pause, settings, inventory, skill tree, map, journal, shop
- Controls — keyboard/mouse layout, gamepad mapping, touch controls
- Onboarding — tutorial flow, tooltip system, contextual hints
- Accessibility — colourblind mode, subtitle toggles, rebindable keys, text size
- Screen flow — title screen → main menu → gameplay → pause → game over
- Loading screens — tips, lore blurbs, progress bars, animated transitions
8. Tech Stack
| Category | Options |
|---|
| Engine | Unity, Unreal, Godot, Phaser, Bevy, GameMaker, custom |
| Language | C#, C++, GDScript, JavaScript, Rust, Python, Lua |
| Rendering | Built-in, URP, HDRP, WebGL, Vulkan, DirectX |
| Physics | Built-in, Box2D, PhysX, Jolt, Rapier |
| Networking | Mirror, Netcode for GameObjects, Photon, Nakama, Colyseus |
| Audio | FMOD, Wwise, Unity Audio, Web Audio API |
| Backend | PlayFab, Steamworks, Firebase, Supabase, custom |
| Source control | Git (Unity/Unreal with LFS), Perforce, Plastic SCM |
| CI/CD | GitHub Actions, GitLab CI, Jenkins, Unity Cloud Build |
9. Milestones & Scope
- Prototype — core mechanic playable (1-2 weeks)
- Vertical slice — one complete level with all systems (1-2 months)
- Alpha — all features in, content placeholder (3-6 months)
- Beta — content complete, polish and bug fixing (6-9 months)
- Gold / Release — final build (9-12 months)
- Post-launch — patches, DLC, seasonal updates, community features
10. Monetization (if applicable)
- Price model — premium ($5-60), free-to-play, freemium, subscription
- DLC — expansions, cosmetic packs, season passes
- Microtransactions — skins, currency, loot boxes, battle pass
- Ads — banner, interstitial, rewarded video
- Crowdfunding — Kickstarter, Patreon, Indiegogo
GDD Formats
| Format | Best For |
|---|
| One-page GDD | Game jams, prototypes, quick pitches |
| Wiki-style GDD (Notion, Confluence) | Long-term projects, teams, living documents |
| Slide deck | Publisher/investor presentations |
| Markdown + Git | Solo devs, version-controlled docs, vibe coding |
| Trello / Miro board | Brainstorming, visual planning, non-linear design |
| Game Design Canvas | Minimalist alternative — one sheet, nine boxes |
Vibe Coder Prompt Templates
Generate a One-Page GDD
Generate a one-page game design document for a [GENRE] game where
the player [CORE ACTION]. The target platform is [PLATFORM] and the
art style is [STYLE]. Focus on the core loop, 3 key mechanics, and
target audience. Keep it to one page.
Expand a Section
I'm working on a [GENRE] game called [TITLE]. Expand the
[SECTION NAME] section of the GDD with detailed bullet points.
Include specific examples and consider edge cases.
Create a Mechanic Specification
Write a detailed mechanic spec for [MECHANIC NAME] in my
[GENRE] game. Include: trigger conditions, duration, player feedback
(visual/audio), balance considerations, and failure states.
Scope Check
Here's my GDD feature list: [LIST FEATURES]. I have a team of
[SIZE] and [TIME] to ship. Which features should I cut or simplify
to stay on schedule? Prioritise by impact on the core loop.
Common Mistakes
| Mistake | Fix |
|---|
| Too vague | Be specific about numbers, timings, and constraints |
| Too detailed in early stages | Keep the first draft high-level; expand as you build |
| Feature creep | Every new idea goes into a “backlog” section, not the GDD body |
| No scope section | Without milestones, the feature list grows forever |
| Writing for yourself | Use language a new team member or AI could understand |
| Never updating it | The GDD is a living document — update it as you build |
| Ignoring tech constraints | A 2D pixel game and a 3D open-world game need very different GDDs |
Recommended Tools
| Purpose | Tool |
|---|
| Writing & sharing | Google Docs, Notion, Obsidian, Markdown |
| Diagrams & flowcharts | Excalidraw, Mermaid, draw.io, FigJam |
| Visual mood boards | Pinterest, Are.na, PureRef |
| Reference capture | OBS, ShareX, Gyazo (grab frames from reference games) |
| Spreadsheets | Google Sheets, Airtable (for stats, items, dialogue) |
| Versioned docs | GitHub / GitLab with Markdown rendering |
| AI GDD generation | ChatGPT, Claude, Cline (with your prompts) |
GDD Checklist
- One-page summary written
- Core loop defined (primary, secondary, tertiary)
- 3-5 core mechanics detailed
- Story / setting outlined
- Art style direction chosen
- Audio approach decided
- UI wireframes / flow sketched
- Tech stack selected
- Milestones and scope defined
- Monetization strategy (if applicable)
- GDD saved in a shared, versioned location
- Reviewed and updated after each major milestone