backend-conventions

C# backend coding conventions separate naming by layer: French ubiquitous language for domain code and English for infrastructure code. This boundary separation ensures clear architectural alignment and consistent communication across domain, application, and infrastructure layers.

Handle time and null values in C# domain design by using DateTimeOffset for all timestamps and TimeProvider for time abstraction. Apply a strict no-null domain design to eliminate null reference exceptions and enforce robust domain invariants.

Structure test doubles for TDD in C# clean architecture by using fakes and stubs rather than mocks. This test double convention supports global error handling strategies and ensures reliable, maintainable unit tests across domain and application layers.

Yes, this C# coding standard supports CQRS architectural patterns by providing strict CQRS guidance. It defines specific conventions for creating commands, queries, and repositories to maintain clear separation between read and write operations.

The best way to document architectural decisions in C# projects is through ADR documentation practices. This skill establishes ADR conventions to record design choices, ensuring traceability and consistent architectural alignment across backend development teams.