C# Coding Guidelines

C# Coding Guidelines

Apply these rules whenever writing or reviewing C# code.

Severity: Must = always enforce · Should = follow unless there is a clear reason not to · May = optional good practice.

Consult the references/ files for the full set of rules per category:

• General (AV0100) — KISS, YAGNI, DRY, OOP pillars, AI code
• Class Design (AV1000) — SRP, LSP, LoD, coupling
• Member Design (AV1100) — properties, methods, parameters, null rules
• Miscellaneous Design (AV1200) — exceptions, events, generics, LINQ
• Maintainability (AV1500) — method size, var, control flow, naming files
• Testability (AV1600) — test naming, builders, public API testing
• Naming (AV1700) — casing, prefixes, abbreviations, async suffix
• Performance (AV1800) — async/await, Task, ValueTask
• Framework Usage (AV2200) — idiomatic C#, dynamic, LINQ syntax
• Documentation (AV2300) — XML docs, inline comments
• Layout (AV2400) — indentation, member order, regions