new-feature

النجوم٢

التفرعات١

آخر تحديث٢٦ أبريل ٢٠٢٦ في ١٢:٢٤

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

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

المصدر

haterade22

haterade22/TAOM

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

مطوّرو البرمجياتمهن الحاسوب والرياضيات·SOC 15-1252

SKILL.md

readonly

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

New Feature Scaffold

Create a new feature module following TAOM 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 TAOM.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)

المزيد من هذا المستودع

نفس المستودع

native-crash-triage

haterade22/TAOM

Root-cause native Bannerlord CTDs (AccessViolation in TaleWorlds.Native.dll) via Event Log offsets, offline disassembly, and live debugger forensics. No symbols needed.

2026-07-242

codex-verify

haterade22/TAOM

Dispatch an independent Codex verification job directly via `codex exec` Bash call, then retrieve and present results

2026-07-222

commit-split

haterade22/TAOM

Inspect all changed files, group by logical concern, and guide atomic per-concern commits following TAOM's 50/72 rule and commit trailer convention.

2026-07-222

context-restore

haterade22/TAOM

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.

2026-07-222

deep-review

haterade22/TAOM

Launch parallel deep-dive agents to review completed work for quality, standards, compatibility, completeness, and cross-system data flow

2026-07-222

engine-bump

haterade22/TAOM

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.

2026-07-222

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

New Feature Scaffold

Create a new feature module following TAOM 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 TAOM.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

المزيد من هذا المستودع

المزيد من هذا المستودع

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`