.NET Software Design Review

Scope And Precedence

• Treat software design principles as contextual heuristics, not automatic mandates.
• Prefer maintainable, testable, intention-revealing local designs over pattern-heavy code, hypothetical abstractions, or premature optimization.
• Apply project conventions first.
• Use csharp-readable-code for language-level member naming, nullability, guards, factories, static members, and test-only production APIs.
• Use dotnet-testing for ordinary test design and maui-ui-testing for device/emulator UI automation.
• Use dotnet-domain-clarification before changing unclear domain-sensitive behavior.
• Use dotnet-clean-architecture and dotnet-ddd-architecture only when the main project instructions explicitly activate them. Do not move code across those boundaries as incidental cleanup.

Principle Reference

For design, non-trivial implementation, self-review, or an explicit code/architecture/design review, read references/design-principles.md. It defines the canonical names, review signals, counterexamples, positive examples, and trade-offs for the shared principle set.