dotnet-writing-skills

Enforce modern .NET coding standards across C# projects.

Updated Oct 7, 2025

Search Tags:#csharp #dotnet #cqrs #coding-conventions #clean-code #vertical-slice-architecture

Ready to run

npx skills add https://github.com/TanaChu0409/book-keeper --skill dotnet-writing-skills

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dotnet-writing-skills
Source: https://github.com/TanaChu0409/book-keeper/tree/main/.github/skills/dotnet-writing-skills
Command: npx skills add https://github.com/TanaChu0409/book-keeper --skill dotnet-writing-skills

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides clear, standardized guidance for writing high-quality .NET C# code by combining Microsoft official coding conventions with Milan Jovanovic's modern .NET practices, helping teams reduce style drift and improve maintainability.

Core Features & Use Cases

Establishes naming conventions, language features, architecture patterns (VSA/CQRS), performance tips, and testing approaches to align code across projects.
Use during new code creation, refactoring, and code reviews to ensure consistency and modern practices; supports teams adopting Vertical Slice Architecture and Result Pattern.
Real-world guidance and checklists for applying clean-code standards in daily development.

Quick Start

Audit an existing C# project against the documented standards to identify and fix deviations.

Frequently Asked Questions about dotnet-writing-skills

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

FAQPage Schema

How do I enforce clean code and C# coding conventions in a .NET project?▼

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.

What is Vertical Slice Architecture and how does it work with CQRS in C#?▼

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.

How do I audit an existing C# project against modern .NET coding standards?▼

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.

Can I use the Result Pattern with Vertical Slice Architecture in .NET?▼

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.

What's the best way to standardize error handling and architecture patterns across multiple .NET projects?▼

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.

When should I not use Vertical Slice Architecture in a C# application?▼

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.