# Archunitnet

Use the open-source free `ArchUnitNET` library for architecture rules in .NET tests.

- Repository: https://github.com/managedcode/dotnet-skills (500 stars)
- Category: Testing
- License: MIT
- Last updated: 2026-10-29
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add managedcode/dotnet-skills --skill archunitnet -g -a claude-code -y`
Codex: `npx skills add managedcode/dotnet-skills --skill archunitnet -g -a codex -y`
Cursor: `npx skills add managedcode/dotnet-skills --skill archunitnet -g -a cursor -y`
Gemini CLI: `npx skills add managedcode/dotnet-skills --skill archunitnet -g -a gemini-cli -y`

## Description

Use the open-source free `ArchUnitNET` library for architecture rules in .NET tests. Use when a repo needs richer architecture assertions than lightweight fluent rule libraries usually provide. USE FOR: the repo uses or wants ArchUnitNET; architecture testing needs richer modeling than simple dependency checks. DO NOT USE FOR: the lightest possible architecture rule checks. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# ArchUnitNET for .NET

## 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.
4. Enforce clear architectural boundaries between agent loops, tools, and domain models as detailed in [building AI agents with .NET](https://managed-code.com/blog-post/building-ai-agents-with-csharp-dotnet).

## Bootstrap When Missing

If `ArchUnitNET` is not configured yet:

The rest: https://github.com/managedcode/dotnet-skills/blob/HEAD/catalog/Libraries/ArchUnitNET/skills/archunitnet/SKILL.md