dotPilot: Skill for Codex

MCAF: .NET ArchUnitNET

Trigger On

• the repo uses or wants ArchUnitNET
• architecture testing needs richer modeling than simple dependency checks

Value

• produce a concrete project delta: code, docs, config, tests, CI, or review artifact
• reduce ambiguity through explicit planning, verification, and final validation skills
• leave reusable project context so future tasks are faster and safer

Do Not Use For

• the lightest possible architecture rule checks

Inputs

• the nearest AGENTS.md
• target assemblies
• architecture boundaries and naming conventions

Quick Start

1. Read the nearest AGENTS.md and confirm scope and constraints.
2. Run this skill's Workflow through the Ralph Loop until outcomes are acceptable.
3. Return the Required Result Format with concrete artifacts and verification evidence.

Workflow

1. Load the architecture once per test assembly where possible.
2. Encode a small number of durable, high-value architecture rules first.
3. Use the test-framework-specific integration package that matches the repo.

Bootstrap When Missing

If ArchUnitNET is not configured yet:

1. Detect existing setup:
   • rg -n "TngTech\\.ArchUnitNET" -g '*.csproj' .
2. Add packages to the architecture test project:
   • dotnet add TEST_PROJECT.csproj package TngTech.ArchUnitNET
   • add one framework bridge package: TngTech.ArchUnitNET.xUnit, TngTech.ArchUnitNET.xUnitV3, TngTech.ArchUnitNET.MSTestV2, or TngTech.ArchUnitNET.TUnit
3. Add at least one durable boundary rule test.
4. Wire architecture tests into the standard test command in AGENTS.md and CI.
5. Run dotnet test TEST_PROJECT.csproj and return status: configured or status: improved.
6. If NetArchTest already covers the same boundary policy and no gap exists, return status: not_applicable.

Deliver

• architecture tests with richer domain and type modeling
• architecture-rule commands wired into repo test flow and CI expectations

Validate