菜单
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%".
用 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.
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).
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 | balance |
| description | 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%". |
Prime rule: docs are the map, anchors are the territory — never edit a hook/case you haven't read in full.
docs/BALANCE-CONSTANTS.md (grep the character or mechanic). If it's not there, treat that as a docs gap: find it in code via the CHARACTERS.md entry, then add the row.case/method containing the constant, not just the line. Check whether the same number appears in sibling cases (some constants repeat across attack/defense branches — e.g. goblin death % exists in two places; change all occurrences or none).characters.json descriptions — they are deliberately vague player-facing text (AGENTS.md rule). If the old number is spelled out in the RU description ("+2 очка", "50%"), flag it in your summary so the designer can decide whether to reword; the exact new value goes into docs/CHARACTERS.md and docs/BALANCE-CONSTANTS.md only.docs/BALANCE-CONSTANTS.md row (value + anchor if lines shifted); update the number in the docs/CHARACTERS.md entry; touch docs/INTERACTION-MATRIX.md only if a threshold changes an interaction rule (e.g. a range that gates forced fights or Harm).dotnet build (+ pnpm build if a widget shows the number), bash tools/audit-passives.sh (must stay clean), bash tools/verify-docs.sh --changed.docs/commit-messages/<date>.md (-2, -3 on same-day collisions) stating old → new values; never git commit.For sweeping balance passes (many numbers), work top-down through BALANCE-CONSTANTS.md sections and batch the verification.