菜单
Design rules, template API, and implementation guide for tower_defense-archetype games (fixed enemy paths + waves + placeable towers — Kingdom Rush, Bloons TD, Hajimi Defense). Invoke during Phase 2 for GDD drafting and Phase 5 as the 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 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.
| name | swipi-module-tower-defense |
| description | Design rules, template API, and implementation guide for tower_defense-archetype games (fixed enemy paths + waves + placeable towers — Kingdom Rush, Bloons TD, Hajimi Defense). Invoke during Phase 2 for GDD drafting and Phase 5 as the reading-list index. |
Authoritative sources:
${CLAUDE_PLUGIN_ROOT}/docs/modules/tower_defense/design_rules.md${CLAUDE_PLUGIN_ROOT}/docs/modules/tower_defense/template_api.md${CLAUDE_PLUGIN_ROOT}/docs/modules/tower_defense/tower_defense.mdEnemies follow pre-determined paths. Player places towers on allowed tiles. Gameplay is organised into waves.
Phase 2: design_rules.md + template_api.md.
Phase 5: template_api.md → targeted _Template* / Base* sources → tower_defense.md.
towers/ — BaseTower, _TemplateTower, per-tower behavior filesenemies/ — BaseEnemy, _TemplateEnemy — each follows a Pathentities/ — shared entity primitives (projectiles, pickups)systems/ — WaveManager, PathManager, EconomyManagerscenes/ — BaseGameScene, _TemplateLevellevelData.json and consumed by PathManager. Do not hard-code waypoints in enemy subclasses.gameConfig.json under waveConfig. Hard-coded waves in code break the wave editor workflow.canPlaceTowerAt(cell) in BoardManager must be called before committing a placement. It checks path overlap, existing towers, and the allowed-tiles mask.BaseTower.applyAOE(); writing custom overlap logic bypasses the damage-reduction pipeline and breaks balance.