.NET Conventions

Standardize C# coding practices for the Exceptionless codebase.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/tedtv1007-ctrl/milk-skills-library --skill net-conventions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: .NET Conventions
Source: https://github.com/tedtv1007-ctrl/milk-skills-library/tree/main/net-conventions
Command: npx skills add https://github.com/tedtv1007-ctrl/milk-skills-library --skill net-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses inconsistencies in C# codebase maintenance by providing a unified set of rules for naming, formatting, async patterns, and logging, ensuring high-quality, maintainable code.

Core Features & Use Cases

  • Standardized Formatting: Enforces consistent indentation, naming conventions, and file-scoped namespaces to minimize diff noise.
  • Best Practice Patterns: Provides templates for async method naming, structured logging with ExceptionlessState, and proper resource disposal.
  • Use Case: When refactoring a legacy service or onboarding a new developer, use this Skill to verify that constructor injection, nullable reference types, and validation patterns align with the project's architectural standards.

Quick Start

Apply the .NET conventions to the current C# project to ensure all naming and logging patterns meet the established style guide.

Frequently Asked Questions about .NET Conventions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize C# coding practices for async patterns and structured logging?

Standardizing C# coding practices involves enforcing consistent naming conventions, async patterns, and structured logging to minimize diff noise and maintain architectural consistency across your codebase.

What is the best way to enforce .editorconfig rules and nullable reference types in .NET?

Enforcing .editorconfig rules and nullable reference types requires applying standardized formatting and domain validation patterns to align your C# project with modern .NET architectural standards.

How do I implement constructor injection and domain validation in a C# backend service?

To implement constructor injection and domain validation, apply templates that ensure proper resource disposal and verify that validation patterns align with your project's architectural standards during onboarding or refactoring.

Does this approach work for refactoring legacy C# codebases to use file-scoped namespaces?

Refactoring legacy C# codebases with this approach enforces file-scoped namespaces and consistent indentation, minimizing diff noise while ensuring adherence to modern .NET development standards.

When do I need standardized formatting for a .NET codebase?

Standardized formatting for a .NET codebase is needed when onboarding new developers or refactoring legacy services to ensure constructor injection, nullable reference types, and validation patterns align with architectural standards.

Why does my C# codebase have inconsistent async patterns and naming conventions?

Inconsistent async patterns and naming conventions in your C# codebase stem from missing unified rules for formatting and best practices, which standardizing .NET conventions resolves to ensure maintainable code.