dotnet-enterprise

Scaffold .NET API projects with Clean Architecture, CQRS, and DDD layers.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/Hung6066/IVF --skill dotnet-enterprise
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-enterprise
Source: https://github.com/Hung6066/IVF/tree/main/.agents/skills/dotnet-enterprise
Command: npx skills add https://github.com/Hung6066/IVF --skill dotnet-enterprise

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enterprise-grade patterns for .NET guide the design and implementation of scalable backends, aligning teams around a robust architectural model that supports growth and maintainability.

Core Features & Use Cases

  • Clean Architecture, CQRS, and DDD to structure complex domains with clear boundaries.
  • Minimal APIs, vertical slices, and comprehensive testing to ship production-ready services.
  • Observability, security policies, and governance to ensure reliability and compliance across services.

Quick Start

Create a new .NET API project and scaffold the Domain, Application, Infrastructure, and API layers following the described structure.

Frequently Asked Questions about dotnet-enterprise

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

FAQPage Schema
How do I structure a .NET backend with Clean Architecture and DDD?

Structure a scalable .NET backend by dividing it into Domain, Application, Infrastructure, and API layers. This enforces clear boundaries for complex domains, separating core domain logic from infrastructure concerns to support maintainability and growth.

What's the best way to implement CQRS in a .NET Minimal API project?

Implement CQRS in .NET Minimal APIs by applying vertical slices to handle commands and queries independently. This approach structures complex domain logic cleanly, ensuring production-ready services with clear boundaries without heavy controller overhead.

Does this approach support production-grade observability for .NET services?

Yes, the approach integrates production-grade observability directly into .NET backend services. It ensures reliability across services by applying governance, security policies, and comprehensive monitoring to maintain compliance and operational visibility.

How do I scaffold a scalable .NET API project with enterprise patterns?

Scaffold a new .NET API project by setting up Domain, Application, Infrastructure, and API layers. This quick start structure applies enterprise patterns like CQRS and DDD to ship production-ready, scalable backend services.

When do I need enterprise architecture patterns for a .NET API service?

You need enterprise architecture patterns when building scalable backend services that require complex domain logic, strict boundaries, and maintainability. Applying Clean Architecture, DDD, and vertical slices aligns teams around a robust model supporting growth.

Can I use vertical slices with Minimal APIs to ship production-ready .NET services?

Yes, you can use Minimal APIs with vertical slices to ship production-ready .NET services. This combination structures complex domains efficiently and enables comprehensive testing, ensuring reliability and compliance across enterprise services.