dotnet-best-practices

To enforce C# best practices during code review, apply this Skill to selected code ranges. It checks SOLID-compliant design, async logging discipline, and validation to ensure your .NET solution remains maintainable and production-ready.

Adding Japanese XML documentation to public C# types requires proper inheritdoc usage for interface implementations. This Skill guides the generation of compliant documentation across application, service, and infrastructure code during refactoring.

The best way to structure MSTest unit tests in .NET is using a clear arrange-act-assert pattern. This Skill improves test quality by integrating FluentAssertions and Moq to align with consistent solution testing standards.

Yes, this dotnet best practices Skill supports primary-constructor dependency injection. It guides service registration, DI patterns, configuration, and error handling toward consistent solution standards across your application and infrastructure code.

Yes, you can use this Skill for refactoring service and infrastructure code. It applies to application, service, infrastructure, and test code, enforcing async patterns, logging discipline, and SOLID-compliant design across the entire solution.

Fixing missing XML documentation in interface implementations requires proper inheritdoc usage for public types and members. This Skill enforces Japanese XML documentation standards to reduce missing documentation and improve codebase reviewability.