메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Reference for generating game assets (sprites, backgrounds, tilemaps, audio) and wiring them into asset-pack.json. Invoked by the swipi-workflow skill during Phase 3, or any time the user asks Claude to add, replace, or debug game assets.
Pick the correct swipi game archetype (platformer, top_down, grid_logic, tower_defense, ui_heavy) from a user prompt using physics-first logic. Invoke from the swipi-workflow skill during Phase 1, or any time you need to decide which template module a game belongs to.
Pre-build consistency checklist and verify→diagnose→repair loop for swipi games. Invoke during Phase 6 of the swipi-workflow, or any time a build/test/dev command fails, or whenever the user reports that a generated game does not run.
Design rules, template API, and implementation guide for grid_logic-archetype games (discrete grid + turn-based or step-based motion — Sokoban, Fire Emblem, Match-3, Pikachu-grid puzzles). Invoke during Phase 2 for GDD drafting and Phase 5 as the reading-list index.
Design rules, template API, and implementation guide for platformer-archetype games (side view + gravity — Mario, Street Fighter, Metal Slug, Castlevania). Invoke during Phase 2 to inform GDD drafting, and again during Phase 5 as a reading-list index.
Design rules, template API, and implementation guide for top_down-archetype games (top-down + free continuous motion — Zelda, Isaac, Vampire Survivors, twin-stick shooters). Invoke during Phase 2 for GDD drafting and Phase 5 as the reading-list index.
| name | swipi-gdd-schema |
| description | 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. |
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.).