Use the open-source free `NetArchTest.Rules` library for architecture rules in .NET unit tests.
SkillScore77Maintained
Automatic
◆QA & Test Engineering pack
Last verified 8/19/2026
What it changes
Passed 15 of 19 test cases with the skill, and 8 of 19 without it.
Without skill41%
With skill77%
Checks it passed that the model alone missed
Status string is not_applicable
Output sets status to not_applicable
Result status value is set to configured
and 8 more in the full report
10 fixed7 passed either way3 still failing2 broke
Pass-rate lift
+36 pp
Tokens
-8%
Agent turns
0%
Response time
-52%
Model gemini-3.6-flashMeasured 8/19/2026v117 of 22 cases passed with skill · 19 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 10
Prompt
In the required result format structure, if all planned architecture test tasks were successfully completed and no open issues remain, what value must be placed in the remaining field?
What was checked, without and with the skill
Checked
Without skill
With skill
The remaining field value is set to none
Missed
Passed
case-17 · gemini-3.6-flash · 8/19/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md99 lines4 files
NetArchTest
Trigger On
the repo uses or wants NetArchTest.Rules
architecture rules should be enforced in automated tests
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
very rich architecture modeling that needs a heavier DSL
Inputs
the nearest AGENTS.md
architecture boundaries to enforce
target assemblies
Quick Start
Read the nearest AGENTS.md and confirm scope and constraints.
Run this skill's Workflow through the Ralph Loop until outcomes are acceptable.
Return the Required Result Format with concrete artifacts and verification evidence.
Workflow
Encode only durable architecture rules:
forbidden dependencies
namespace layering
type shape conventions
Keep rules readable and close to the boundary they protect.
Fail tests on architecture drift, not on temporary style noise.
Use the free official .NET diagnostics CLI tools for profiling and runtime investigation in .NET repositories. USE FOR: the repo needs performance or runtime profiling for a .NET application; the user asks about slow code, high CPU, GC pressure, allocation growth, exception storms, lock. DO NOT USE FOR: replacing realistic performance tests or load tests with ad-hoc tracing alone; production heap collection when the pause risk has not been. INVOKES: inspect the repository context, edit targeted