dotnet-writing-skills

You enforce clean code and C# coding conventions by applying standardized guidance covering naming conventions, language features, and architecture patterns during new code creation, refactoring, and code reviews to reduce style drift and improve maintainability.

Vertical Slice Architecture organizes code by feature rather than technical concern, working with CQRS by separating read and write operations within each slice to align code across projects and improve maintainability.

You audit an existing C# project against modern .NET coding standards by reviewing the codebase against documented checklists for naming conventions, performance tips, and architecture guidance to identify and fix deviations from clean code practices.

Yes, you can use the Result Pattern with Vertical Slice Architecture in .NET to handle errors explicitly without exceptions, supporting teams adopting modern practices by standardizing error handling across vertical slices.

The best way to standardize error handling and architecture patterns across multiple .NET projects is to establish clear guidance combining official conventions with modern practices, applying it uniformly during development to reduce style drift and align code.

You should avoid Vertical Slice Architecture in a C# application when your project relies on traditional layered architecture, as VSA organizes by feature rather than technical layers, which may not suit all team structures or domain complexities.