Menu
Scaffold a new TAOM feature module with IoC, services, adapters, and tests following project conventions
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | new-feature |
| description | Scaffold a new TAOM feature module with IoC, services, adapters, and tests following project conventions |
| argument-hint | ["FeatureName"] |
Create a new feature module following TAOM architecture from @docs/ai-includes/architecture.md
$ARGUMENTSCreate the following files under Main/Features/$ARGUMENTS/:
{FeatureName}IoC.cs — Static Register{FeatureName}Feature(IContainer container) methodReuse.SingletonMain/IoC.cs by calling from Configure()I{FeatureName}Service.cs — Interface defining the feature's public API{FeatureName}Service.cs — Implementation with constructor-injected dependenciesIHeroAdapter, etc.), NEVER sealed TaleWorlds types (ADR-007)Hooks/{PatchName}Patch.cs — Harmony patches (thin, delegate to service)I{TypeName}Adapter.cs + {TypeName}Adapter.cs under Main/Adapters/Follow @docs/ai-includes/tdd-enforcement.md
Create under TAOM.Tests/Features/$ARGUMENTS/:
{FeatureName}ServiceTests.cs — 100% service coverageMethodName_StateUnderTest_ExpectedBehaviorBefore scaffolding, suggest /freeze to the user with the new feature dir as the boundary — prevents drift into adjacent code while the feature is taking shape. Widen the boundary (or /unfreeze) only when wiring Main/IoC.cs or Main/SubModule.cs for integration.
Main/IoC.cs#region, [Obsolete], or #if DEBUG./build.ps1 -RunTests — if it fails, route to /build-fix; if structural, /investigate/deep-review clean before commit (per CLAUDE.md Critical Rules)Root-cause native Bannerlord CTDs (AccessViolation in TaleWorlds.Native.dll) via Event Log offsets, offline disassembly, and live debugger forensics. No symbols needed.
Dispatch an independent Codex verification job directly via `codex exec` Bash call, then retrieve and present results
Inspect all changed files, group by logical concern, and guide atomic per-concern commits following TAOM's 50/72 rule and commit trailer convention.
Load a snapshot saved by /context-save and present it so this session can pick up where the last one left off without re-deriving decisions.
Launch parallel deep-dive agents to review completed work for quality, standards, compatibility, completeness, and cross-system data flow
Respond to a Bannerlord engine update (Steam force-bump or deliberate migration) — preserve the decompile baseline, regen, diff, re-verify bindings and creature data, control-battle.