Start a fresh conversation. Replace the highlighted placeholders.
Use dotnet-best-practices to review and improve [C# project or selection] for project conventions, XML documentation, validated configuration, secure data access, and resource disposal.
Required inputs
[C# project or selection]
User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗
SKILL.md
name: dotnet-best-practicesdescription: 'Ensure .NET/C# code meets best practices for the solution/project.'
.NET/C# Best Practices
Your task is to ensure .NET/C# code in ${selection} meets the best practices specific to this solution/project. This includes:
Documentation & Structure
Create comprehensive XML documentation comments for all public classes, interfaces, methods, and properties
Include parameter descriptions and return value descriptions in XML comments
Follow the established namespace structure: {Core|Console|App|Service}.{Feature}
Design Patterns & Architecture
Use primary constructor syntax for dependency injection (e.g., public class MyClass(IDependency dependency))
Implement the Command Handler pattern with generic base classes (e.g., CommandHandler<TOptions>)
Use interface segregation with clear naming conventions (prefix interfaces with 'I')
Follow the Factory pattern for complex object creation.
Dependency Injection & Services
Use constructor dependency injection with null checks via ArgumentNullException
Register services with appropriate lifetimes (Singleton, Scoped, Transient)
Use Microsoft.Extensions.DependencyInjection patterns
Implement service interfaces for testability
Resource Management & Localization
Use ResourceManager for localized messages and error strings
Separate LogMessages and ErrorMessages resource files
Access resources via _resourceManager.GetString("MessageKey")
Async/Await Patterns
Use async/await for all I/O operations and long-running tasks
Return Task or Task from async methods
Use ConfigureAwait(false) where appropriate
Handle async exceptions properly
Testing Standards
Use MSTest framework with FluentAssertions for assertions
Follow AAA pattern (Arrange, Act, Assert)
Use Moq for mocking dependencies
Test both success and failure scenarios
Include null parameter validation tests
Configuration & Settings
Use strongly-typed configuration classes with data annotations