원클릭으로
Run the full design pipeline with brainstorm wizard, or add one missing system.
npx skills add https://github.com/Yuki001/game-dev-skills --skill gat-design이 명령을 Claude Code에 복사하여 붙여넣어 스킬을 설치하세요
Run the full design pipeline with brainstorm wizard, or add one missing system.
npx skills add https://github.com/Yuki001/game-dev-skills --skill gat-design이 명령을 Claude Code에 복사하여 붙여넣어 스킬을 설치하세요
Use this skill whenever a user asks to generate, create, draw, render, or edit images with GPT Image 2 / gpt-image-2, text-to-image, reference-image editing, inpainting, posters, typography, Chinese text, UI mockups, diagrams, or gallery prompts. Analyze the user's prompt, search the bundled Reference Gallery/craft files for matching design patterns, confer on direction when useful, then call the bundled CLI script directly. Do not write new image-generation code unless explicitly asked to modify this repo.
READ this skill when designing or planning any game system architecture — including combat, skills, AI, UI, multiplayer, narrative, or scene systems. Contains paradigm selection guides (DDD / Data-Driven / Prototype), system-specific design references, and mixing strategies. Works as a domain knowledge plugin alongside workflow skills (OpenSpec, SpecKit) or plan mode of an agent.
Inspect the repo state and recommend the next step in the simplified workflow.
READ this skill when implementing or configuring animation-style shaders (Toon/Cel Shaders) — including outlines, rim lighting, toon shading, MatCap, emission, dissolve, hatching, or any stylized rendering effect. Contains preset styles and feature-to-reference mappings for lilToon, Poiyomi, UTS2, RToon, SToon, and ToonShadingCollection. Works as a domain knowledge plugin alongside workflow skills (OpenSpec, SpecKit) or plan mode of an agent.
Implement one ready task from a milestone tasks.md.
Break the project into milestones and create production/milestone.md plus milestone directories.
| name | gat-design |
| description | Run the full design pipeline with brainstorm wizard, or add one missing system. |
| argument-hint | [<hint> | <system-name>] |
| user-invocable | true |
| allowed-tools | Read, Glob, Grep, Write, Edit, Agent, AskUserQuestion |
This skill writes all design and art documents.
Check existing files:
design/gdd/game.md missing → Mode: wizardsystems-index.md → Mode: systemgame.md exists and at least one system in systems-index.md lacks a GDD → Mode: continuegame.md exists and all systems have GDDs → report design is complete, stopTreat any non-system-name argument as a concept hint passed into the wizard.
Skip this phase if Mode is continue or system.
If a concept hint was provided, first spawn gat-designer to extract what is already answered from the hint:
Then use AskUserQuestion to ask only the questions the hint did not answer. If the hint answered all four, skip Step 1 entirely and proceed to Step 2.
Spawn gat-designer to generate 2-3 short concept directions (3-5 sentences each) based on Step 1 answers.
Use AskUserQuestion:
Spawn gat-designer to propose a system list with brief rationale for each, based on the chosen direction.
Use AskUserQuestion (multiSelect):
Then use a second AskUserQuestion:
Show a one-paragraph summary: chosen direction + confirmed system list.
Use AskUserQuestion:
Yes, write them (Recommended) / Let me adjust somethingIf user wants to adjust, loop back to the relevant step.
Read templates:
.claude/docs/templates/design/game-overview.md.claude/docs/templates/design/systems-index.md.claude/docs/templates/design/system-gdd.md.claude/docs/templates/design/global-art.md.claude/docs/templates/design/system-art.md.claude/docs/templates/design/content-data.mdIf Mode is wizard: execute Steps 1-5 below in order.
If Mode is continue: skip Steps 1-2, go directly to Step 3.
Step 1 — Spawn gat-designer to write design/gdd/game.md and design/gdd/systems-index.md:
Step 2 — Spawn gat-artist to write design/art/art-direction.md:
game.md, global-art templateart-direction.md if presentAsk after Step 2 complete - After step 2 complete, Let user confirm changes:
Use AskUserQuestion:
Yes, continue to next step / Let me adjust somethingStep 3 — For each system in systems-index.md lacking a GDD, in order:
Spawn gat-designer → design/gdd/<system>.md:
game.md, systems-index.md, system-gdd templateStep 4 — Content Fill (for systems with high content volume)
For each system whose system GDD is complete AND which requires substantial content data, spawn gat-designer to write design/content/<system>-data.md:
game.md, systems-index.md, content-data templateA system needs a content-data doc when its GDD defines data structures that need many concrete instances (e.g. an enemy GDD defines enemy attributes → content doc fills 25+ specific enemies; a stage GDD defines wave scheduling → content doc fills wave-by-wave scripts for all 5 stages).
Systems that are purely mechanical (e.g. input, tbs-scoring) typically do NOT need content-data docs — their parameters fit within the GDD itself.
Step 5 — For each system in systems-index.md lacking an art doc, in order:
Spawn gat-artist → design/art/<system>-art.md:
game.md, art-direction.md, the system GDD, the content-data doc (if it exists), system-art templateRequire design/gdd/game.md and design/gdd/systems-index.md.
Step 1 — Spawn gat-designer → design/gdd/<system>.md
Step 2 — If the system needs content data, spawn gat-designer → design/content/<system>-data.md
Step 3 — Spawn gat-artist → design/art/<system>-art.md (pass GDD + content-data if exists)
Summarize what was created or updated.
Use AskUserQuestion:
Plan milestones (Recommended) → Run /gat-milestoneAdd another system → Run /gat-design <name>Stop here