netarchtest-generator

A generator for automated architecture tests in .NET projects. These tests check rules such as which code layers may depend on each other, how types are named, and where namespaces may be used.

In plain words
What is it for?
Use it to create NetArchTest or ArchUnitNET tests for layering, dependencies, naming rules, sealed types, and project boundaries.
Why use it?
It makes structural design violations fail during the build instead of being discovered later.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/stefanthecode/dotnet-ai-toolkit/netarchtest-generator
Any agent
npx skills add StefanTheCode/dotnet-ai-toolkit --skill netarchtest-generator
Clone the repo
git clone --depth 1 https://github.com/StefanTheCode/dotnet-ai-toolkit

Made for: Claude Code, Codex.

Per session 98 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 627 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00098 $0.00627
Opus 5 $0.00049 $0.00313
Sonnet 5 $0.00020 $0.00125
Haiku 4.5 $0.00010 $0.00063

Measured 2d ago against content hash bb490048fd77, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

netarchtest-generator scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/netarchtest-generator/SKILL.md · 52 lines

How it starts

The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Architecture Tests Generator (NetArchTest)

Turn architectural rules into automated tests so violations fail the build instead of slowly rotting the codebase — layering, dependencies, naming, and boundary rules tailored to the project.

Input — point it at your project

Works on a target: a solution/project or GitHub URL. Detect the structure to enforce: find <target> -name "*.csproj", and the style (Clean layers? Vertical Slice? modules?) via folder names and references.

Setup

dotnet add package NetArchTest.Rules

Rules (tailored to the detected architecture)

Clean Architecture dependency rule:

[Fact]
public void Domain_has_no_outward_dependencies()
{
    var r = Types.InAssembly(typeof(Order).Assembly)
        .Should().NotHaveDependencyOnAny("MyApp.Application", "MyApp.Infrastructure", "MyApp.Api")
        .GetResult();
    Assert.True(r.IsSuccessful, string.Join("\n", r.FailingTypeNames ?? new()));
}

Other common fitness functions:

// Handlers must be sealed
Types.InAssembly(asm).That().HaveNameEndingWith("Handler").Should().BeSealed();
// Controllers/endpoints don't reference DbContext directly
Types.InAssembly(asm).That().HaveNameEndingWith("Controller").ShouldNot().HaveDependencyOn("MyApp.Infrastructure.Data");
// Modules don't reference each other's internals (modular monolith)
Types.InAssembly(ordersAsm).ShouldNot().HaveDependencyOn("MyApp.Modules.Billing");
// Async methods end with "Async"
Types.InAssembly(asm).That().HaveNameMatching(".*").Should()...; // naming conventions

Principles

  • Encode the rules you actually care about — every test should map to a real architectural decision.
  • Architecture tests are fitness functions: cheap, fast, run in CI, fail loudly.
  • Match the rules to the real structure (don't impose Clean rules on a Vertical Slice app).
  • A handful of high-value rules beats dozens of pedantic ones.

How to use it & best prompts

"Add architecture tests to enforce my layers", "stop controllers from using DbContext", "enforce that handlers are sealed", "guardrail tests for my modular monolith". Pairs with clean-architecture-scaffolder, modular-monolith-generator, and the dotnet-architecture-reviewer agent.

Read the full file on GitHub · 52 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 52 lines · 98 tokens per session scan A bb490048fd77

Subscribe to this mod's changes

netarchtest-generator is a skill published in the GitHub repository StefanTheCode/dotnet-ai-toolkit (19 stars, last pushed 24d ago), licensed MIT. It adds 98 tokens to every session and 627 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens