菜单
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.
用 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.
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).
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".
| name | new-character |
| description | 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. |
Prime rule: docs are the map, anchors are the territory — never edit a hook/case you haven't read in full.
docs/GAME-DESIGN.md — the systems the new kit touches (fight math §4, score §6, Вред §7, pipeline §8; forced fights / kills / swaps have established carve-out patterns).docs/ARCHITECTURE.md §3 (hook execution order + which hook fires when) and §7 (the 14-file per-character pattern).docs/CHARACTERS.md and read their actual code end to end (state class → PassivesClass fields → every CP case → DTO → mapper → signalr.ts → PlayerCard widget). They are the living template; copy their shapes, not fragments from memory.docs/INTERACTION-MATRIX.md — every table the new kit will touch (does it force fights? kill? move positions? steal/copy? intercept moral/psyche/Harm? is anything Standalone: true and therefore Ziggurat-copyable?).*_update files or Game/GameDesign.txt), treat them as the spec alongside characters.json descriptions.DataBase/characters.json — exact-string PassiveNames (they are identifiers), Visible, Standalone only if safe to Ziggurat-copy. PassiveDescriptions are the designer's voice: use their wording from the intent notes verbatim; keep them vague/flavorful — never write technical spec into them (that goes in docs/CHARACTERS.md).Game/Characters/<Name>.cs — state classes.Game/Classes/PassivesClass.cs — owner state + per-player marks (follow the SellerMark naming pattern).Game/MemoryStorage/CharactersPhrases.cs — phrases.Game/GameLogic/CharacterPassives.cs — case "…": per hook; add immunity checks for transferred passives; use the round-10 ban carve-out pattern (CheckIfReady.cs:1270) for any forced action.
6–9. Only if needed: DoomsdayMachine.cs (core fight mechanics), CheckIfReady.cs (turn injection), GameReactions.cs (level-up override), BotsBehavior.cs (bot moral + targeting + the Name-keyed cases — use the exact JSON Name).GameUpdateMess.cs — leaderboard icons.
11–14. Web: DTO (GameStateDto.cs), mapper (GameStateMapper.cs — gate by character Name if the passive name is shared), signalr.ts, PlayerCard.vue/SkillsPanel.vue (+ sound.ts if audio; compare the Name against the exact JSON string — see finding m22 for how that goes wrong).docs/CHARACTERS.md — full entry with file:line anchors, ⚠ on any known deviation.docs/INTERACTION-MATRIX.md — a row in every applicable table.docs/BALANCE-CONSTANTS.md — every tunable number.bash tools/audit-passives.sh — every new passive must appear as ok (no ORPHAN unless intentionally name-keyed; then whitelist with a comment), zero new GHOST/BAD-NAME.dotnet build + pnpm build (type-check is broken in this environment) + bash tools/audit-passives.sh + bash tools/verify-docs.sh --changed; then a targeted play-test plan (which rounds/actions exercise each passive). Write the commit message to docs/commit-messages/<date>.md (-2, -3 on same-day collisions); never git commit.