Dotnet Patterns

This one loads Claude up with modern C# conventions: records over classes, explicit nullability, async all the way down with CancellationToken, dependency injection through interfaces, and the options pattern for configuration. It's opinionated about immutability and includes concrete patterns like Result types for expected failures, proper EF Core repository implementations, and minimal API route groups. Use it when you want Claude to write C# that looks like it came from a senior .NET developer who cares about maintainability. The examples are solid, from parallel async operations with Task.WhenAll to custom middleware that actually logs useful metrics. It won't teach you .NET from scratch, but it will keep Claude from generating mutable DTOs with public setters.

install copies · 90 days. Times the install command was copied on this site in the last 90 days, bots filtered.: 5
skills.sh installs: 3.7K
GitHub stars: 229.1K
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/everything-claude-code --skill dotnet-patterns --agent claude-code

Installs into .claude/skills of the current project.

Files

.NET Development Patterns

Idiomatic C# and .NET patterns for building robust, performant, and maintainable applications.

When to Activate

Writing new C# code
Reviewing C# code
Refactoring existing .NET applications
Designing service architectures with ASP.NET Core

Core Principles

1. Prefer Immutability

Use records and init-only properties for data models. Mutability should be an explicit, justified choice.

// Good: Immutable value object
public sealed record Money(decimal Amount, string Currency);

// Good: Immutable DTO with init setters
public sealed class CreateOrderRequest
{
    public required string CustomerId { get; init; }
    public required IReadOnlyList<OrderItem> Items { get; init; }
}

// Bad: Mutable model with public setters
public class Order
{
    public string CustomerId { get; set; }
    public List<OrderItem> Items { get; set; }
}

2. Explicit Over Implicit

Be clear about nullability, access modifiers, and intent.

// Good: Explicit access modifiers and nullability
public sealed class UserService
{
    private readonly IUserRepository _repository;
    private readonly ILogger<UserService> _logger;

SKILL.md on GitHub