noahbutcher97

Verify KatanaCombat changes with the right Unreal build, automation test, log parsing, static inspection, and diff review. Use when the user asks to verify, validate, run tests, check build health, confirm a fix, prepare a final report, or finish any KatanaCombat code/config/docs change.

Diagnose KatanaCombat bugs from evidence before fixes. Use when the user reports crashes, failing tests, broken combat behavior, animation timing issues, parry/combo/hold regressions, asset wiring problems, or unclear Unreal Editor/runtime failures.

Plan and implement KatanaCombat feature work safely. Use when the user asks to add, implement, extend, refactor, or wire gameplay, combat, paired-animation, editor-tool, data-asset, test, or documentation behavior in this Unreal Engine 5.6 project.

Use when adding a new tool to an existing UEMCP toolset (offline, TCP:55558, or HTTP:30010) — scaffolds the tools.yaml entry, the handler/executor case, and the test, then verifies the rotation assertion count grew. Triggers on "add a tool", "new UEMCP tool", "add a tool to the <X> toolset", "scaffold a tool".