new-feature

スター0

フォーク0

更新日2026年6月10日 17:39

Scaffold a new DOTS feature module with IoC, services, adapters, and tests following project conventions

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

ソース

haterade22

haterade22/DOTS

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

New Feature Scaffold

Create a new feature module following DOTS architecture from @docs/ai-includes/architecture.md

Feature Name: `$ARGUMENTS`

Required Structure

Create the following files under Main/Features/$ARGUMENTS/:

1. IoC Registration

{FeatureName}IoC.cs — Static Register{FeatureName}Feature(IContainer container) method
Register all services as Reuse.Singleton
Wire into Main/IoC.cs by calling from Configure()

2. Service Layer

I{FeatureName}Service.cs — Interface defining the feature's public API
{FeatureName}Service.cs — Implementation with constructor-injected dependencies
Services MUST use adapter interfaces (IHeroAdapter, etc.), NEVER sealed TaleWorlds types (ADR-007)

3. Entry Points (if needed)

Hooks/{PatchName}Patch.cs — Harmony patches (thin, delegate to service)
Entry points MUST be <150 lines (ADR-002)

4. Adapters (if needed)

I{TypeName}Adapter.cs + {TypeName}Adapter.cs under Main/Adapters/
Only create if wrapping a new sealed TaleWorlds type not already adapted

5. Tests (MANDATORY — TDD)

Follow @docs/ai-includes/tdd-enforcement.md

Create under DOTS.Tests/Features/$ARGUMENTS/:

{FeatureName}ServiceTests.cs — 100% service coverage
Use MSTest + NSubstitute
Naming: MethodName_StateUnderTest_ExpectedBehavior
Write tests FIRST (RED), then implement (GREEN), then refactor

Scope-lock recommendation

Before 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.

Checklist

Tests written first (RED state verified)
All services use adapter interfaces, not sealed types
IoC registered in Main/IoC.cs
Entry points <150 lines
No #region, [Obsolete], or #if DEBUG
Build passes: ./build.ps1 -RunTests — if it fails, route to /build-fix; if structural, /investigate
/deep-review clean before commit (per CLAUDE.md Critical Rules)

このリポジトリの他の Skills

同じリポジトリ

author-armor

haterade22/DOTS

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.

2026-06-130

lord-skills

haterade22/DOTS

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.

2026-06-130

new-culture

haterade22/DOTS

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.

2026-06-130

adopt-external

haterade22/DOTS

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.

2026-06-100

agent-introspection-debugging

haterade22/DOTS

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.

2026-06-100

build-fix

haterade22/DOTS

Incrementally fix dotnet build errors with minimal diffs, one error at a time

2026-06-100

name	new-feature
description	Scaffold a new DOTS feature module with IoC, services, adapters, and tests following project conventions
argument-hint	["FeatureName"]

New Feature Scaffold

Create a new feature module following DOTS architecture from @docs/ai-includes/architecture.md

Feature Name: `$ARGUMENTS`

Required Structure

Create the following files under Main/Features/$ARGUMENTS/:

1. IoC Registration

{FeatureName}IoC.cs — Static Register{FeatureName}Feature(IContainer container) method
Register all services as Reuse.Singleton
Wire into Main/IoC.cs by calling from Configure()

2. Service Layer

I{FeatureName}Service.cs — Interface defining the feature's public API
{FeatureName}Service.cs — Implementation with constructor-injected dependencies
Services MUST use adapter interfaces (IHeroAdapter, etc.), NEVER sealed TaleWorlds types (ADR-007)

3. Entry Points (if needed)

Hooks/{PatchName}Patch.cs — Harmony patches (thin, delegate to service)
Entry points MUST be <150 lines (ADR-002)

4. Adapters (if needed)

I{TypeName}Adapter.cs + {TypeName}Adapter.cs under Main/Adapters/
Only create if wrapping a new sealed TaleWorlds type not already adapted

5. Tests (MANDATORY — TDD)

Follow @docs/ai-includes/tdd-enforcement.md

Create under DOTS.Tests/Features/$ARGUMENTS/:

{FeatureName}ServiceTests.cs — 100% service coverage
Use MSTest + NSubstitute
Naming: MethodName_StateUnderTest_ExpectedBehavior
Write tests FIRST (RED), then implement (GREEN), then refactor

Scope-lock recommendation

Checklist

Tests written first (RED state verified)
All services use adapter interfaces, not sealed types
IoC registered in Main/IoC.cs
Entry points <150 lines
No #region, [Obsolete], or #if DEBUG
Build passes: ./build.ps1 -RunTests — if it fails, route to /build-fix; if structural, /investigate
/deep-review clean before commit (per CLAUDE.md Critical Rules)

new-feature

New Feature Scaffold

Feature Name: $ARGUMENTS

Required Structure

1. IoC Registration

2. Service Layer

3. Entry Points (if needed)

4. Adapters (if needed)

5. Tests (MANDATORY — TDD)

Scope-lock recommendation

Checklist

このリポジトリの他の Skills

このリポジトリの他の Skills

New Feature Scaffold

Feature Name: $ARGUMENTS

Required Structure

1. IoC Registration

2. Service Layer

3. Entry Points (if needed)

4. Adapters (if needed)

5. Tests (MANDATORY — TDD)

Scope-lock recommendation

Checklist

Feature Name: `$ARGUMENTS`

Feature Name: `$ARGUMENTS`