nesbo/dotnet-claude-code-skills

Claude Code Skills for .NET developers.

This repository also configures its own agents. See what dotnet-claude-code-skills tells them →

53Stars on the repository
9Mods indexed here, across every type
8mo agoLast push, which is what freshness is scored on
noneNo LICENSE: all rights reserved, so bodies are not copied

add-serena

01

nesbo/dotnet-claude-code-skills

Plugin Claude Code

Bundles 1 skill · 0 tokens together

Complete integration guide for adding Serena MCP to any software project. Provides IDE-like semantic code understanding through LSP integration, symbol-level navigation, and precise code editing. Includes prerequisites checking, installation steps, configuration templates for C#, Python, TypeScript and more…

not rated 53 8mo ago A tokens not measured

bdd-dotnet

02

nesbo/dotnet-claude-code-skills

Plugin Claude Code

Bundles 1 skill · 0 tokens together

BDD-style unit testing patterns for domain handlers with in-memory database, TestDataBuilder pattern, fluent builders, and fake implementations - no mocking frameworks. Shown with NUnit examples; patterns apply to any testing framework.

not rated 53 8mo ago A tokens not measured

data-dotnet

03

nesbo/dotnet-claude-code-skills

Plugin Claude Code

Bundles 1 skill · 0 tokens together

Complete guide to implementing data persistence as an adapter in hexagonal architecture with entity mappings, repositories, Unit of Work, and migration workflows. Demonstrates one ORM approach; patterns apply to any data access technology.

not rated 53 8mo ago A tokens not measured

ddd-dotnet

04

nesbo/dotnet-claude-code-skills

Plugin Claude Code

Bundles 1 skill · 0 tokens together

Comprehensive guide to implementing DDD patterns with CQRS, Hexagonal Architecture, aggregates, entities, command/query handlers, and domain best practices. Explained using C# and .NET, but patterns apply to any OOP language.

not rated 53 8mo ago A tokens not measured

At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: