Menú
Scaffold a new DOTS feature module with IoC, services, adapters, and tests following project conventions
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Author a culture's armor items and swap troop equipment rosters via the generator + validation pipeline. Use when adding/revamping armor. Enforces the canonical-folder + cover-attribute rules.
Give DOTS lords lore-driven skill values and traits via the DOTS SkillSet system. Use when a canonical lord has wrong stats or a culture roster needs a balance pass.
Author or revamp a DOTS culture's armor set, troop tree, and recruitment wiring end-to-end. Use for new cultures or troop-tree revamps. Follows docs/ai-includes/new-culture-authoring.md.
Use when reviewing an external repo or article to adopt practices into DOTS — security-vet first, map novel vs duplicative, port (never install), review, commit your changes.
Structured 4-phase self-debug for failing agent runs (looping, drifting, burning tokens). Capture, diagnose, contained recovery, report. Complements /investigate (which is for code bugs); this skill is for harness/agent failures.
Incrementally fix dotnet build errors with minimal diffs, one error at a time
| name | new-feature |
| description | Scaffold a new DOTS feature module with IoC, services, adapters, and tests following project conventions |
| argument-hint | ["FeatureName"] |
Create a new feature module following DOTS 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 DOTS.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)