gamedev-skills/awesome-gamedev-agent-skills / skills/workflows/game-docs
game-docs
VerifiedWrites 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`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.2 KB |
| agents/openai.yaml | config | 228 B |
| references/architecture-template.md | markdown | 2.5 KB |
| references/doc-rules.md | markdown | 4.5 KB |
| references/feature-templates.md | markdown | 4.2 KB |
| references/gdd-template.md | markdown | 3.6 KB |
| references/workflow-modes.md | markdown | 8.4 KB |
| scripts/check_docs.py | script | 29.2 KB |
references/architecture-template.md
View on GitHub# ARCHITECTURE template
Copy into `ARCHITECTURE.md` next to the GDD once the code has structure that more than one feature depends on (a save format, an event bus, a scene flow), or when the user asks. Until then, the engine is one line in the GDD summary. If the GDD has another file name, change the `[GDD](GDD.md)` link to match. A feature's own modules, data and events go in its `implementation.md`, which links back here for the shared parts.
**Describe the code as it is**: read the repo and use real paths and names. Leave out a section with nothing in it yet. Text in *italics* is guidance; don't copy it.
~~~markdown
# <Title> — Architecture
**Updated:** <YYYY-MM-DD> · [GDD](GDD.md)
## 1. Stack
| | |
|---|---|
| Engine / framework | <name + exact version> |
| Language | |
| Build / bundler | |
| Target runtime | <browsers, devices, OS versions> |
| Key libraries | |
| Hosting / distribution | |
## 2. Structure
*Scenes/states and how control moves between them; the main loop (fixed vs variable step); who owns the game state.*
```
<diagram: e.g. Boot → Title → Play ⇄ Pause → Results, or a module dependency sketch>
```
## 3. Module map
| Module / folder | Responsibility | Used by features |
|---|---|---|
| `src/systems/runSim.ts` | one run as pure logic, no rendering | [combo](features/combo/implementation.md), … |
## 4. Cross-cutting conventions
- **Events / messaging:** *(bus or direct calls; the list of shared event names and payloads; who may emit)*
- **Config and tuning:** *(where tunables live, e.g. one `config.ts`; naming; how design.md numbers map to constants)*
- **Data / content:** *(data file formats, where content tables live)*
- **Persistence:** *(save format, storage, current save version, migration rule)*
- **Randomness:** *(seeded RNG? where seeds come from; determinism requirements)*
- **Rendering / UI layering:** *(canvas vs DOM overlay, scaling, safe areas)*
- **Input:** *(abstraction layer, devices)*
- **Assets:** *(pipeline, naming, budgets)*
## 5. File layout
```
<tree with a short note per folder>
```
## 6. Performance budget
*Target and floor FPS on named devices; draw-call, entity, memory and download-size limits; the "no per-frame allocation" kind of rules.*
## 7. Testing and tooling
*Test runner and how to run it; test folder layout; bots / simulations; debug keys and flags; the manual device check routine. Each feature's testing.md points at specific files.*
## 8. Build and release
*Dev server command and port; build command; versioning; deploy target and steps.*
## 9. Open questions and tech risks
~~~
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |