LowFile-scopeC# Plug & play

Avoid Excessively Deep Namespaces

Ensure that titlespace structures are not overly deep. Favor a flat, organized structure to enhance readability and navigation.

Why this matters

Deeply nested titlespaces increase code complexity, making navigation and maintenance more difficult.

Side-by-side examples engineers can pattern-match during review.

Avoid

titlespace Company.Project.Module.Component.Subcomponent.Feature {}

Prefer

titlespace Company.Feature {}

Bad

titlespace Company.Project.Module.Component.Subcomponent.Feature {}

Good

titlespace Company.Feature {}

From the same buckets as this rule.

Critical
Require an ADR for any architectural or cross-team decision
For changes that affect architecture, data models, external APIs, security posture, deployment topology, or cost (>10%), create an ADR in docs/adr/ using the standard template (Context, Decision, Consequences) and link the PR and issue IDs.
docs-adrsmodule-architecture+1
Critical
Use Factory Method Injection in `@Configuration` Classes
Ensure that factory method injection is used in `@Configuration` classes instead of `@Autowired` field injection.
module-architecturestyle-conventions
High
A module should not import itself
Identify cases where a module imports itself. Self-imports are usually unintentional and can cause confusion or unnecessary dependencies. Suggest removing them.
module-architecture