メニュー
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.
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.
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.
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 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-module-platformer |
| description | 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. |
Authoritative sources (read with the Read tool — absolute paths):
${CLAUDE_PLUGIN_ROOT}/docs/modules/platformer/design_rules.md${CLAUDE_PLUGIN_ROOT}/docs/modules/platformer/template_api.md${CLAUDE_PLUGIN_ROOT}/docs/modules/platformer/platformer.mdDuring Phase 2 (GDD): read design_rules.md + template_api.md for design knowledge and code capabilities.
During Phase 5 (code): read in this order, last-read stays freshest:
template_api.md — compressed reference for every template hook, behavior, and utility (Layer 1)._Template*.ts you will COPY and every Base*.ts you will EXTEND, as identified from GDD Section 5 (Layer 2).platformer.md — implementation manual (Layer 3 — read last).Shipped in templates/modules/platformer/src/:
behaviors/ — reusable AI/physics behaviors (patrol, chase, jump, shoot)characters/ — BasePlayer, BaseEnemy, _TemplatePlayer, _TemplateEnemyscenes/ — BaseGameScene, _TemplateLevelutils.ts — platformer-specific helpersgameConfig.json — platformer config defaultslevelData.json per-tile — not in the scene code. Read design_rules.md for the tile-property schema.behaviors/PatrolBehavior.ts — do not reimplement patrol in the enemy subclass.