netarchtest
FeaturedUse the open-source free `NetArchTest.Rules` library for architecture rules in .NET unit tests. Use when a repo wants lightweight, fluent architecture assertions for namespaces, dependencies, or layering. USE FOR: the repo uses or wants NetArchTest.Rules; architecture rules should be enforced in automated tests. DO NOT USE FOR: very rich architecture modeling that needs a heavier DSL. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
Install
Quality Score: 92/100
Skill Content
Details
- Author
- managedcode
- Repository
- managedcode/dotnet-skills
- Created
- 6 months ago
- Last Updated
- 6 days ago
- Language
- C#
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
archunitnet
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.
arch-encode
Turn an architectural mistake into a durable, enforceable rule. Use right after catching drift, a repeated bad pattern, or a review finding you want to stop recurring — or whenever someone says "add a rule so this never happens again." Writes the rule as a specific negative code example in the correct file (the nearest scoped AGENTS.md, or the repo's decisions.md), wires it into the mechanical gate when it is mechanically checkable, then proves the rule holds by reverting the bad change, clearing context, and re-running the original task. Also prunes bloated or contradictory rule files.
arch-enforce
Verify-phase gate that enforces Clean Architecture MECHANICALLY (not by vibes) with a dependency linter: dependency-cruiser (JS/TS), import-linter (Python), ArchUnit (JVM), or the language's equivalent. Use in the verify phase, when setting up a new repo's guardrails, or when the user says "enforce architecture", "dependency rules", "layering check", "dependency-cruiser".