coding-conventions

C# naming conventions standardize identifiers using PascalCase for types and members, CamelCase for local variables and parameters. This Skill enforces Microsoft official guidelines across your entire .NET codebase, ensuring consistency in naming patterns that improve readability and reduce cognitive load when reviewing code.

C# 12 and later introduce Primary Constructors, Collection Expressions, Default Lambda Parameters, and the field keyword for backing fields. This Skill guides adoption of these features to make code more concise, readable, and maintainable while enforcing their correct usage across .NET 8+ projects.

Yes. This Skill enforces comprehensive .NET/C# coding conventions by checking naming rules, formatting (Allman-style braces, indentation), prohibition of underscore-prefixed backing fields, and usage of modern C# features, automatically validating code quality across your entire codebase.

Modern C# coding standards prohibit underscore prefixes for private fields to keep naming patterns consistent and leverage newer features like the field keyword instead. This Skill enforces this convention to align with Microsoft guidelines and promote cleaner, more maintainable code structure.

This Skill applies to all codebases targeting .NET 8 and later. It can validate both new and existing code against modern C# conventions, helping teams incrementally adopt modern standards and features while maintaining consistent quality across the entire project.

C# code formatting enforces Allman-style braces (opening braces on new lines), proper indentation, and mandatory braces for all control structures—no omission allowed. This Skill checks these rules automatically, ensuring uniform layout and preventing subtle bugs caused by missing braces.