Skip to content

gamedev-skills/awesome-gamedev-agent-skills / skills/workflows/game-docs

game-docs

Verified

Writes and maintains a game's design docs: a one-page GDD with a feature index and short feature notes, kept true to the code by a link and status checker. Use for "draft a GDD", "spec out this mechanic", or updating docs after a playtest or code change. Not for building a game when no docs were asked for (`prototype-fast`, `game-jam`), READMEs or level layouts (`level-design`).

references/gdd-template.md

View on GitHub
# GDD template

Copy this into `GDD.md` in the docs folder. The GDD is the game as a whole on about one page: why it exists, what it feels like, and a map of its features. A feature's rules and numbers belong in its `design.md`; the GDD gives a one-line summary and a link.

Keep the headings `Feature index`, `Decisions` and `Change log` as written: the header links point at them. Add `· [Architecture](ARCHITECTURE.md)` to the header only once that file exists. Leave out a summary row or optional section that doesn't apply yet, with no note. Text in *italics* is guidance; don't copy it.

~~~markdown
# <Title> — Game Design Document

**Version:** 0.1 · **Updated:** <YYYY-MM-DD> · [Features](#feature-index) · [Decisions](#decisions) · [Change log](#change-log)

## Summary
<2–4 sentences: who the player is, what they do, what makes it fun, how a run or game ends.>

| | |
|---|---|
| Genre and camera | |
| Audience | <age, skill, casual or core> |
| Platforms and input | |
| Session | <one run or level, total playtime> |
| Engine | <one line; mark [ASSUMPTION] if not chosen> |
| Scope | <jam / prototype / small release, deadline> |
| References | <games this feels like, and what's taken from each> |

## Pillars
*3 to 5. A pillar is a short bold statement plus one sentence on the choices it settles. Pillars end design arguments, so a pillar nobody could disagree with ("fun gameplay") is not one.*
1. **<Pillar>.** <What it makes you choose, and what it rules out.>

## Core loop
```
<action → reward → growth → harder challenge → back>
```
- **Seconds:** *(the moment-to-moment features, linked)*
- **Minutes:** *(recurring events)*
- **Session and between sessions:**

## Feature index
*One row per feature; this table is the map of the game and the checker keeps it in step with features/. A row links its design.md once that exists.*

| Feature | Status | Scope | Summary | Docs |
|---|---|---|---|---|
| Lane movement | implemented | MVP | Swipe between 3 lanes; jump and duck | [design](features/lane-movement/design.md) |
| Combo | designed | MVP | Stunts fill a meter for a ×1–×5 multiplier; a hit resets it | [design](features/combo/design.md) |
| Leaderboard | idea | later | Weekly distance board | — |

## Milestones
*Each ends in something playable. M1 is usually a greybox of the core loop.*
1. **M1, greybox core loop:** <features> · done when: <a checkable statement>

## Decisions
*IDs run in sequence and are never reused; a superseded decision stays, marked "→ superseded by D-n".*

| ID | Date | Decision | Alternatives considered | Why | Affects |
|---|---|---|---|---|---|
| D-001 | <date> | | | | |

## Open questions
- **Assumptions to confirm:** *(every [ASSUMPTION] in the GDD)*
- **Risks:** *(design "is X fun?", tech, scope; each with how you'll find out)*

## Change log
**0.1 (<date>):** first draft.
~~~

## Optional sections

Add these to the GDD, after Milestones, when the game needs them:

- **Screens and flow:** `Boot → Title → Game ⇄ Pause → Results → Title`, with one line per screen linked to the feature that owns it.
- **Direction:** the rules every feature follows, one short paragraph each, only for what is decided: tone and narrative, art (style, palette, readability of danger and safety), audio, game feel (what a hit, a reward and a failure feel like), accessibility and localization.
- **Game-level acceptance:** only criteria that span features ("a first-time player finishes a run in under 60 s without reading text"; "60 fps on <device>").

Change-log lines stay one line per version, with the detail in the linked docs: `**0.2 (<date>):** combo designed ([combo](features/combo/design.md)); D-003 logged.`
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall