cleanddd-dotnet-coding

Enforces coding standards for building scalable, secure apps.

33|4|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/netcorepal/cleanddd-skills --skill cleanddd-dotnet-coding
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cleanddd-dotnet-coding
Source: https://github.com/netcorepal/cleanddd-skills/tree/main/skills/cleanddd-dotnet-coding
Command: npx skills add https://github.com/netcorepal/cleanddd-skills --skill cleanddd-dotnet-coding

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill codifies the coding guidelines to implement modeled CleanDDD requirements (aggregates, commands, queries, API endpoints, events, repositories, configurations, and tests) within CleanDDD projects, enabling consistent, maintainable code across teams.

Core Features & Use Cases

  • Centralizes conventions for naming, layered architecture, and strong-typed IDs to promote consistency across .NET CleanDDD implementations.
  • Guides end-to-end workflows from domain modeling to endpoint implementation, data access, and testing.
  • Provides a repeatable blueprint for adding new modules and maintaining code quality in a CleanDDD system.

Quick Start

Follow these guidelines when implementing CleanDDD components in a .NET project to ensure consistent structure and naming.

Frequently Asked Questions about cleanddd-dotnet-coding

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

FAQPage Schema
How do I structure CleanDDD domain models in .NET?

Implement CleanDDD commands and queries in .NET by following standardized rules for layered architecture and strong-typed IDs. The guidelines enforce async repository calls and prohibit SaveChanges in command handlers to maintain data consistency.

How do I add API endpoints and repositories in a CleanDDD .NET project?

Add API endpoints and repositories in a CleanDDD .NET project by following a repeatable blueprint for module creation. This workflow standardizes endpoint implementation and enforces async repository calls for data access to maintain code quality.

Do I need strong-typed IDs for CleanDDD .NET coding?

CleanDDD .NET coding distinguishes itself by codifying end-to-end workflows from domain modeling to endpoint implementation. It enforces strict layering, strong-typed IDs, and non-SaveChanges in command handlers unlike general DDD approaches.

Are there limitations on using SaveChanges in CleanDDD command handlers?

Yes, a key limitation is that SaveChanges is explicitly prohibited in CleanDDD command handlers. The guidelines enforce async repository calls and strict layering to maintain consistent data access and transactional boundaries.