メニュー
Implement manual edits made to docs/ into the game code — docs as the editing surface. Use for "apply the docs changes", "я поменял числа в BALANCE-CONSTANTS", "make the game match the docs", "implement what I changed in CHARACTERS.md".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Review King of the Garbage Hill replay bugs from a replay ID, player-facing replay URL, or replay API URL. Use when troubleshooting a replay, checking what players saw, comparing replay state with raw JSON, or investigating a reported replay discrepancy; always derive and inspect both the anonymous Web UI and REST API forms from any one input.
Drive the rendered King of the Garbage Hill replay page in a real browser and collect screenshots, visible gameplay text, DOM state, interaction inventory, layout-overflow findings, console errors, and failed requests. Use for replay links, replay UI/UX review, player-perspective or round/fight inspection, visual regressions, and gameplay bug reports where the displayed cards, leaderboard, fights, passives, or logs must be examined instead of relying only on replay JSON.
Change a tunable game number (buff/nerf/rebalance a chance, threshold, cooldown, cost, multiplier, stat) for King of the Garbage Hill. Use for "buff X", "nerf Y", "change Z from 3 to 5", "сделай шанс 20%".
Fix any game bug — by audit finding ID ("fix M9 M11") OR from a free-form bug report ("Тигр получает халявные очки на старте"). Triages against docs/AUDIT-FINDINGS.md, catalogues new bugs as findings automatically, reads ALL related code before editing, updates docs in the same change, verifies, writes the commit message.
Implement a NEW King of the Garbage Hill character, or add a brand-new passive/widget to an existing one, following the verified 14-file pattern with docs updated in the same change. Use for "add character X", "new passive/widget". Changing how an EXISTING passive works is /rework-passive.
Change how an existing passive/ability works (mechanics rework per designer intent) — e.g. "переделай Огурчик Рик так, чтобы…", "rework Butcher's marks", implementing a *_update intent note. Not for bugs (/fix-finding), brand-new passives (/new-character) or pure number tweaks (/balance).
| name | sync-docs |
| description | Implement manual edits made to docs/ into the game code — docs as the editing surface. Use for "apply the docs changes", "я поменял числа в BALANCE-CONSTANTS", "make the game match the docs", "implement what I changed in CHARACTERS.md". |
The user edits docs/ by hand as a way of specifying changes; this skill makes the code match. Direction matters: here the doc is the spec and the code is wrong — the opposite of normal verification.
git diff docs/ (working tree) is the primary source. If docs/ is untracked or the diff is empty, ask the user what they changed (or accept it from the prompt).docs/PASSIVE-MAP.md, docs/commit-messages/.BALANCE-CONSTANTS.md row (number change) → follow the /balance procedure: the row's own anchor points at the code; read the whole case/method, check for sibling-case duplicates of the same constant, implement. Remember characters.json descriptions stay untouched (design-voice rule) — flag if the old number is spelled out there.CHARACTERS.md behavior prose (mechanics change) → follow the /rework-passive procedure: the edited sentence is the intent note; load the passive's whole world (all cases, bots, widgets), implement, run the leftover sweep.INTERACTION-MATRIX.md cell (rule change, e.g. a missing carve-out marked as required) → implement the rule at the referenced site; mirror the established patterns (e.g. the round-10 ban carve-out CheckIfReady.cs:1270).AUDIT-FINDINGS.md / DESIGNER-REVIEW.md verdict edits → that's /fix-finding territory: treat filled-in verdicts as go-signals for those IDs.GAME-DESIGN.md / ARCHITECTURE.md edits → system-level change; stop and confirm scope before touching the pipeline/fight math (these are the highest-blast-radius files).After implementing: update the other docs that cite the same fact (a number lives in both BALANCE-CONSTANTS and the CHARACTERS entry); refresh anchors that shifted (bash tools/verify-docs.sh --changed); the user's edited text itself is kept — only made consistent, never reverted.
dotnet build (+ pnpm build if web touched) + bash tools/audit-passives.sh + bash tools/verify-docs.sh --changed. Commit message to docs/commit-messages/<date>.md listing each doc-edit → code-change pair; never git commit.
If a doc edit is ambiguous ("faster", "чуть реже") — ask for the concrete value; never guess numbers into the game.