菜单
Map a new failure path to the canonical FailureReason enum, keeping it in 1:1 sync with the error-taxonomy spec (enforced by a drift test). Use when code needs a failure classification that does not yet exist.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Debugging workflow for BloogBot/WWoW codebase. Use when investigating bugs, errors, unexpected behavior, or service failures.
Add or generate compiled activity-catalog rows (ActivityDefinition) from the leveling-guide source and keep them passing the catalog invariant tests + MaNGOS cross-validation. Use when adding an Activity to the catalog.
Creating or modifying WoW class/spec combat profiles. Use when adding a new class profile, fixing combat rotations, or adjusting bot behavior for a specific specialization.
Add an IBotTask behavior-tree task that orchestrates Actions to drive one minute state change, with FG+BG parity, tests, and live-validation. Use when implementing a new bot behavior (move/loot/interact/cast/gather/etc.) as a Task on the LIFO task stack.
Add an IConfigSubscriber for a new reloadable config section so a running service applies changes without restart, with ACK/rollback. Use when a config section must hot-reload (the feature-flag / live-tunable path).
Author a new activity coordinator (Dungeon/Raid/BG/Quest/Economy/etc.) in WoWStateManager that orchestrates multiple bots through an Activity by emitting Objectives from snapshot state. Use when a multi-character Activity needs server-side coordination.
| name | failure-reason-mapping |
| description | Map a new failure path to the canonical FailureReason enum, keeping it in 1:1 sync with the error-taxonomy spec (enforced by a drift test). Use when code needs a failure classification that does not yet exist. |
| trigger | add a FailureReason, error taxonomy, classify a failure, new failure code, FailureReasonCatalogTests, map a failure path |
Add a new failure classification so a Task/coordinator/service can report why it
failed, keeping the FailureReason enum a faithful mirror of the error-taxonomy
spec — the enum and the spec are kept 1:1 by a drift test.
Exports/GameData.Core/Enums/FailureReason.cs.docs/Spec/12_ERROR_TAXONOMY.md (snake_case reasons
grouped by category: pathfinding, transport, socket, bot lifecycle, physics,
task execution, activity legality, inventory, server, catalog, …).Tests/BotRunner.Tests/Spec/FailureReasonCatalogTests.cs
(asserts enum ⇄ spec parity)..github/instructions/shared-libraries.instructions.md.FailureReason already fits (search the enum + spec first).dotnet build is green.docs/Spec/12_ERROR_TAXONOMY.md
under the correct category section.Exports/GameData.Core/Enums/FailureReason.cs,
keeping the category grouping aligned.FailureReason.<Value> at the failure site (task completion, metrics,
logging) — never invent an ad-hoc string.FailureReasonCatalogTests.cs deliberately.dotnet test Tests/BotRunner.Tests/BotRunner.Tests.csproj --filter "FullyQualifiedName~FailureReasonCatalogTests"
— must pass (enum and spec in sync)..\scripts\test-fast.ps1 for no broader regression.docs/Spec/12_ERROR_TAXONOMY.md and FailureReason.cs.FailureReason on failure.FailureReason.docs/Spec/12_ERROR_TAXONOMY.md.