Architecture Layer Guard
Checks added using directives against configured forbidden import pairs, enforcing architectural boundaries at commit time.
Why this rule exists
Layer rules written in a wiki get violated. Layer rules enforced at commit time stay enforced. Once a Domain class imports Microsoft.EntityFrameworkCore, the boundary is gone forever.
Code example
// src/MyApp.Domain/Order.cs
+ using Microsoft.EntityFrameworkCore; // src/MyApp.Domain/Order.cs has no infrastructure imports.
// EF mappings live in src/MyApp.Infrastructure/.Configuration
Disable or adjust the severity of this rule in .gauntletci.json:
{
"rules": {
"GCI0035": { "enabled": true, "severity": "Warn" }
}
}See Configuration for the full schema.
Related rules
Dependency Injection Safety
Detects DI anti-patterns: service locator usage, direct instantiation of injectable types, and captive dependency violations.
Complexity Control
Detects over-engineering: single-use interfaces, abstract classes without abstract members, and unnecessary indirection added in the diff.
Implemented in src/GauntletCI.Core/Rules/Implementations/GCI0035_*.cs.
Eric Cogen -- Founder, GauntletCI
Twenty years in .NET production. Most of those years, the bugs that hurt me were not the ones tests caught. They were the assumptions I did not know I was making: a removed guard clause, a renamed method that still did the old thing, a catch {} that turned a page into a silent dashboard lie. GauntletCI is the checklist I wish I had run before every commit. It runs the rules I learned the hard way, so you do not have to.