From swipi-engine
Universal 6-section Game Design Document schema used by every swipi archetype. Invoke during Phase 2 of the swipi-workflow before writing GAME_DESIGN.md, or any time the user asks for the structure of a swipi GDD.
How this skill is triggered — by the user, by Claude, or both
Slash command
/swipi-engine:swipi-gdd-schemaThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Authoritative source:** `${CLAUDE_PLUGIN_ROOT}/docs/gdd/core.md`
Authoritative source: ${CLAUDE_PLUGIN_ROOT}/docs/gdd/core.md
Read the full schema before drafting a GDD. The sections below are the contract between Phase 2 (design) and Phases 3–5 (generation + implementation).
| Section | Title | Downstream consumer |
|---|---|---|
| 0 | Architecture | Phase 4 — main.ts registration, LevelManager.LEVEL_ORDER |
| 1 | Assets | Phase 3 — asset generation, asset-pack.json |
| 2 | Config | Phase 4 — gameConfig.json merge |
| 3 | Entities / Scenes | Phase 5 — per-file implementation |
| 4 | Levels / Content | Phase 3 — tilemap generation & Phase 5 content loops |
| 5 | Roadmap | Phase 5 — todo-list expansion, file-by-file checklist |
scene.start() / scene.launch() calls later. Pick them once here and never retype them.asset-pack.json keys character-for-character.screenSize, debugConfig, renderConfig are not in Section 2 — they survive untouched through a merge.platformer / top_down / grid_logic must reference tile glyphs from the archetype's design_rules.md tile legend. Invented glyphs break tilemap generation.After loading this schema, invoke the matching swipi-module-<archetype> skill for design rules that are specific to the chosen physics regime (entity types, scene flow, level progression, etc.).
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub citronetic/swipi-engine --plugin swipi-engine