coding-conventions

C# naming conventions standardize types, members, variables, and parameters across projects. This Skill codifies modern .NET naming rules—PascalCase for types and public members, camelCase for parameters and local variables—and provides .editorconfig configuration to automatically enforce them in your IDE and CI/CD pipeline, eliminating style inconsistencies during code reviews.

Modern C# coding standards emphasize nullable references, pattern matching, and recent language features (C# 12–14, .NET 8–10) such as primary constructors, collection expressions, and advanced LINQ patterns. This Skill aligns your team with Microsoft's official guidelines, bans underscore-prefixed backing fields, requires explicit braces, and promotes contemporary syntax to keep codebases maintainable and performant.

Apply coding conventions in your .NET project via .editorconfig files and linting rules. This Skill provides pre-configured formatting and naming conventions that enforce consistent indentation, brace placement, and code layout, integrating directly with Visual Studio and other C# IDEs to validate style automatically during development and pull request reviews.

Primary constructors and collection expressions require C# 12+ and .NET 8+. This Skill guides adoption of these modern features where your project's target framework supports them, helping you incrementally modernize syntax in existing codebases while maintaining backward compatibility and explaining when each feature is appropriate.

Distributed teams maintain style consistency by codifying conventions in version-controlled .editorconfig and linting configuration files. This Skill provides a centralized reference for naming, layout, and modern C# patterns, ensuring every developer—regardless of IDE—follows identical rules, reducing merge conflicts and making code reviews focus on logic rather than formatting.

Modern C# conventions apply prospectively to new code and refactored sections. This Skill distinguishes between critical rules (nullable references, explicit braces) and optional modernizations (primary constructors, advanced LINQ), allowing teams to adopt conventions incrementally without requiring full codebase rewrites while still achieving uniform style over time.