메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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.
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-asset-protocol |
| description | 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. |
Read the full protocol document before generating assets — it is the single source of truth for asset keys, file conventions, and pack structure.
Authoritative source: ${CLAUDE_PLUGIN_ROOT}/docs/asset_protocol.md
Use the Read tool with that absolute path. Do not paraphrase from memory.
Read the asset protocol in full.ui_heavy games.public/assets/asset-pack.json under the correct bucket (images / spritesheets / audio / atlases).Read the resulting asset-pack.json so the exact string keys are in your context for Phase 5.TextureNotFound / AnimationNotFound)asset-pack.json with identical spelling.animations.json must point to a spritesheet registered in asset-pack.json.title_bg in asset-pack.json must point to a real image file before TitleScreen runs.>8 assets are required, split generation into two batches (backgrounds/tilesets first, animations/audio second) to keep each tool call focused.When running inside the swipi-engine Claude Code plugin, use Claude's Bash tool plus whatever image/audio CLI is configured locally — there is no bundled generate-assets MCP tool in this Phase-1 POC. Phase 2 will expose the OpenGame GenerateAssetsTool, GenerateTilemapTool, and GenerateGDDTool through an MCP server bundled with this plugin.
Until then:
curl against any image-generation API you have keys for (DashScope, OpenAI Image, Stability, fal.ai) and save under public/assets/.