skills.rest
AndresJQCode
AndresJQCodeCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

dotnet-ddd-architecture

Enforce DDD and CQRS patterns in .NET Core applications with MediatR.

Updated Aug 23, 2026
Search Tags:#architecture#ddd#cqrs#ef core#dapper#mediatr#.net core
One-click install
npx skills add https://github.com/AndresJQCode/template-net-core-9-DDD --skill dotnet-ddd-architecture
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dotnet-ddd-architecture
Source: https://github.com/AndresJQCode/template-net-core-9-DDD/tree/main/.claude/skills/dotnet-ddd-architecture
Command: npx skills add https://github.com/AndresJQCode/template-net-core-9-DDD --skill dotnet-ddd-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill enforces strict Domain-Driven Design (DDD) and CQRS architectural patterns in .NET Core applications, ensuring maintainable, scalable, and well-structured codebases.

Core Features & Use Cases

  • Architectural Enforcement: Guarantees adherence to DDD principles, CQRS with MediatR, Minimal APIs, and clear layer separation.
  • Layered Structure: Enforces distinct responsibilities for Domain, Application, Infrastructure, and API layers.
  • CQRS Implementation: Mandates the use of Commands for state modification (EF Core) and Queries for read operations (Dapper).
  • Use Case: A new .NET Core project needs to be built following best practices for Domain-Driven Design and Command Query Responsibility Segregation to ensure long-term maintainability and scalability.

Quick Start

Use the dotnet-ddd-architecture skill to generate a new .NET Core project structure that strictly follows DDD and CQRS principles.

Frequently Asked Questions about dotnet-ddd-architecture

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

FAQPage Schema
How do I enforce Domain-Driven Design and CQRS patterns in a .NET Core application?▼

To enforce DDD and CQRS in .NET Core, mandate strict layer separation using MediatR for command and query handling, Minimal APIs for the API layer, EF Core for commands, and Dapper for queries.

What is the correct architecture for separating read and write operations in .NET Core?▼

Correct CQRS architecture in .NET Core separates read and write operations by using EF Core for state modification commands and Dapper for optimized read queries, coordinated via MediatR.

Can I use Minimal APIs with MediatR for enterprise-grade .NET Core architecture?▼

Yes, you can use Minimal APIs with MediatR in .NET Core to handle command and query dispatching, ensuring a clean API layer while maintaining strict DDD and CQRS architectural boundaries.

When do I need strict Domain, Application, Infrastructure, and API layer separation in .NET Core?▼

You need strict Domain, Application, Infrastructure, and API layer separation in .NET Core when building enterprise-grade software to prevent architectural drift and ensure long-term maintainability.

Why does my .NET Core project structure experience architectural drift without DDD enforcement?▼

Architectural drift occurs in .NET Core projects without DDD enforcement because strict layer responsibilities and CQRS patterns are not mandated, leading to mixed concerns and degraded code quality.

Related Skills

Explore More Software Engineering Skills→
gerardogarnicagerardogarnica

unit-testing

Generate deterministic unit tests for .NET Clean Architecture Domain and Application layers.

Community
Advanced
nesbonesbo
53

bdd-dotnet

Implements BDD-style unit tests for .NET domain handlers using in-memory EF Core databases.

Community
Advanced
bbolek-apbbolek-ap

cqrs-mediatr

Coordinate CQRS components in .NET apps using MediatR with Autofac and FluentValidation.

Community
Advanced
FaysilAlshareefFaysilAlshareef
4

repository-patterns

Implement repository and Unit of Work patterns for .NET with Entity Framework Core.

Community
Intermediate