gamedev-kit

Plugin gamedev-kit from marketplace claude-gamedev-kit in dudwns0921/claude-gamedev-kit. Commands read from the repo's manifest — 18 days ago.

Skills (9)

• balance-table

  Keeps the balance table (data/balance.xlsx) — an Excel sheet where the game's balance numbers are seen at a glance — in step with the balance value file in code, which is what the game runs on. Code → table (export; a hook does it whenever the value file changes), table → code (bake), are they equal

• board

  Draws the game's status board — HTML pages made by a script. First screen: the cycle in hand (its goal in one line, where it stands, its tasks, what waits on the user), then the stages of play in the order the player meets them, each with what is still open in it (problem · not made · placeholder ·

• ceo

  Runs a game's cycles for the user in the background — several at once, one headless Claude Code run (a worker) per step — while the user only decides and plays. This window coordinates: it proposes the next goals, starts workers for the cycles that can move, takes the dashboard's answers, and keeps

• cycle

  Drives one game-dev cycle — Goal → Spec → Design → Plan → Build → Play — through a single document (docs/cycle/). Systems designer, designer and developer agents work stage by stage; every decision goes back to the user. Use when the user states a bundle of goals ("이번 사이클", "다음 버전 만들자", "이번엔 ○○ 를 넣자

• feedback

  Keeps the user's own rules — what their games taught that would trip them again (a trap, a way to verify), one line each, on this machine and loaded into every game of theirs — and sends them to the kit's repository as GitHub issues, so the kit grows from every game that uses it. Rules are written w

• gdd-sync

  Syncs the game design document (docs/GDD.md) and the game code in both directions. Matches the IDs in the GDD's Appendix A sync table against `GDD: <ID>` markers in code to find mismatch, missing and orphan items, aligns values in the given direction (GDD→code or code→GDD), then updates the table's

• init

  Sets a game repo up for gamedev-kit, from an empty folder if need be: asks where the game will be played (a phone · a computer · a browser — one or several) and so which engine (the editor and the engine project are made with the engine's own tools), then installs the files the kit uses — engine con

• playtest

  Playtest → analysis → build flow. The analyst agent (playtest-analyst) turns the problem list the user wrote after playing into a task document in docs/playtest/, and one developer agent (developer, Sonnet) per task handles it. Use when the user lists several problems or to-dos ("플레이해 봤는데", "해 보니까 이

• start

  Takes a game from "the kit is installed, nothing is decided" to the first cycle: writes the GDD with the user by interview (one loop → one question per turn), agrees on the look with concept images, proposes the first cycle's goal, and hands over to the CEO (the ceo skill — or the cycle skill, for o

Subagents (4)

• designer

  Takes the "Spec" section of a cycle document (docs/cycle/*.md) and writes how it looks and sounds — UI appearance · effects · sound · needed assets — as the "Design" section. Does not decide rules, numbers or spatial dimensions. Given screenshots, checks them against docs/DESIGN.md. Does not change

• developer

  Takes a work document and does one of four things — plan: reads the goal, spec and design sections of a cycle document (docs/cycle/*.md) and writes the task list and order. build: implements and verifies one task (T3) of a cycle document or playtest analysis document (docs/playtest/*.md) exactly as

• playtest-analyst

  Takes the list of problems from a playtest, reads the code and the GDD to find the causes, and organizes them into a work document (docs/playtest/*.md) that another (cheaper) model can implement as written without re-analyzing. Does not change code. Called by the playtest skill — used when the user

• systems-designer

  Takes the goal of a cycle document (docs/cycle/*.md) and writes the rules · balance numbers · structure and dimensions of spaces as the "Spec" section. Does not fix values; offers ranges with the calculation attached — the user decides. Does not edit code · the GDD · the balance table. Called by the

Hooks (17)

• UserPromptSubmit

  python3 "${CLAUDE_PLUGIN_ROOT}/hooks/context_watch.py"

• UserPromptSubmit

  python3 "${CLAUDE_PLUGIN_ROOT}/skills/board/scripts/board.py" watch --notice

• SessionStart

  python3 "${CLAUDE_PLUGIN_ROOT}/skills/init/scripts/init.py" --rules-check

• SessionStart

  python3 "${CLAUDE_PLUGIN_ROOT}/skills/feedback/scripts/feedback.py" --notice

• SessionStart

  python3 "${CLAUDE_PLUGIN_ROOT}/skills/board/scripts/board.py" watch --notice

• SessionStart

  python3 "${CLAUDE_PLUGIN_ROOT}/skills/ceo/scripts/ceo.py" --notice

• Stop

  python3 "${CLAUDE_PLUGIN_ROOT}/hooks/context_watch.py" --record

• Stop

  python3 "${CLAUDE_PLUGIN_ROOT}/skills/balance-table/scripts/balance_table.py" export --if-stale

• Stop

  python3 "${CLAUDE_PLUGIN_ROOT}/skills/board/scripts/board.py" --if-stale

• Stop

  python3 "${CLAUDE_PLUGIN_ROOT}/skills/board/scripts/board.py" push --if-changed

• Stop

  python3 "${CLAUDE_PLUGIN_ROOT}/skills/feedback/scripts/feedback.py" push --quiet

• Stop

  python3 "${CLAUDE_PLUGIN_ROOT}/skills/board/scripts/board.py" watch --rewake

• PostToolUse

  python3 "${CLAUDE_PLUGIN_ROOT}/skills/balance-table/scripts/balance_table.py" export --if-stale

• PostToolUse

  python3 "${CLAUDE_PLUGIN_ROOT}/skills/board/scripts/board.py" --if-stale

• PostToolUse

  python3 "${CLAUDE_PLUGIN_ROOT}/skills/board/scripts/board.py" push --if-changed

• SubagentStop

  python3 "${CLAUDE_PLUGIN_ROOT}/skills/balance-table/scripts/balance_table.py" export --if-stale

• SubagentStop

  python3 "${CLAUDE_PLUGIN_ROOT}/skills/board/scripts/board.py" --if-stale