Is this skill compatible with Mediator?

Yes, it utilizes the Mediator pattern for use cases to decouple the API layer from business logic, ensuring each command or query remains a distinct, testable unit of work.

Does this skill work with .NET 10 features?

Yes, it is specifically optimized for .NET 10, utilizing modern C# features like primary constructors, version 7 Guids, and the latest Minimal API patterns.

How does it handle business logic?

Business logic is encapsulated within Domain Entities as methods or specifications to avoid anemic models, while the Application layer orchestrates these through single-purpose Use Case handlers.

Why use IAppDbContext instead of the Repository pattern?

This skill favors IAppDbContext because EF Core's DbSet already acts as a repository; adding an extra abstraction layer often introduces unnecessary indirection without added value.

What project structure does this skill follow?

It follows a standardized 4-project layout consisting of Domain, Application, Infrastructure, and the API layer to ensure strict separation of concerns and dependency inversion.

Clean Architecture for .NET

Name: Clean Architecture for .NET
Author: codewithmukesh

bycodewithmukesh

•

189

•

API Development

Implements robust, maintainable .NET 10 applications using Clean Architecture principles, domain-driven design, and decoupled use-case patterns.

The Clean Architecture skill transforms Claude into a specialized architect for .NET 10 development, focusing on the highly scalable four-project layout: Domain, Application, Infrastructure, and API. It enforces strict dependency inversion where the domain layer remains pure, business logic is encapsulated within behavior-rich entities, and use cases serve as the primary unit of work via Mediator patterns. This skill is essential for developers looking to build enterprise-grade backends that are decoupled from specific frameworks, easy to test, and resistant to architectural rot.

Key Features

01Infrastructure-as-plugin implementation for EF Core and external services

02Minimal API auto-discovery via IEndpointGroup and thin controllers

03MediatR-based use case handlers for Commands and Queries

04Standardized 4-project layout (Domain, Application, Infrastructure, Api)

05189 GitHub stars

06Domain-driven design with behavior-rich entities and business rules

Use Cases

01Enforcing architectural boundaries and dependency inversion in existing C# projects.

02Refactoring 'Fat Controllers' or anemic domain models into clean use-case handlers.

03Bootstrapping a new enterprise .NET 10 web API with a scalable architecture.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add codewithmukesh/dotnet-claude-kit clean-architecture

For use in Claude.ai and ChatGPT

Download Skill