skills.rest
yeeehaooo
yeeehaoooCOMMUNITY
Explore all skills by this author →
GitHub

clean

Enforce clean architecture boundaries in .NET projects with vertical-slice organization.

Updated Feb 20, 2026
Search Tags:#architecture#modularity#dotnet#cqrs#clean-architecture#vertical-slice#layered-architecture
One-click install
npx skills add https://github.com/yeeehaooo/WorkSpace --skill clean-yeeehaooo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clean
Source: https://github.com/yeeehaooo/WorkSpace/tree/main/skills/dotnet/structures/clean
Command: npx skills add https://github.com/yeeehaooo/WorkSpace --skill clean-yeeehaooo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Layered architecture with vertical slice organization following Clean Architecture principles. This structure helps teams maintain clear boundaries between API, application, domain, and infrastructure layers, enabling easier testing, maintenance, and scalability.

Core Features & Use Cases

  • Four-layer architecture: API, Application, Domain, and Infrastructure sections with clear responsibilities.
  • Vertical-slice organization: Modules grouped by feature/use-case to improve cohesion and testability.
  • Guidance for dependency direction: Enforces that Domain remains framework-agnostic and outer layers depend on inner layers.
  • CQRS-ready patterns: Supports command/query separation and cross-cutting concerns.

Quick Start

Organize your project with API, Application, Domain, and Infrastructure layers and structure modules under Modules/{ModuleName}/{UseCase}/ following vertical slices.

Frequently Asked Questions about clean

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

FAQPage Schema
How do I enforce clean architecture boundaries in a .NET backend project?▼

Enforce clean architecture in .NET by organizing code into API, Application, Domain, and Infrastructure layers. This establishes clear dependency direction rules, keeping Domain framework-agnostic while outer layers depend on inner layers.

What is vertical slice architecture and how does it organize .NET modules?▼

Vertical slice architecture organizes .NET modules by grouping feature use-cases under Modules/{ModuleName}/{UseCase}/. This structure improves cohesion and testability compared to traditional horizontal layering.

Can I use CQRS patterns within a layered .NET clean architecture project?▼

Yes, CQRS patterns are supported within this clean architecture structure. It provides command and query separation guidance alongside cross-cutting concerns within the Application layer boundaries.

How do I structure my .NET solution to keep the Domain layer framework-agnostic?▼

Keep the Domain layer framework-agnostic by enforcing dependency direction rules where outer layers depend on inner layers. The four-layer structure isolates Domain logic from API, Application, and Infrastructure dependencies.

Does this clean architecture approach work for large .NET projects requiring high scalability?▼

Yes, this clean architecture approach suits large .NET projects by maintaining clear boundaries between API, Application, Domain, and Infrastructure layers. The vertical-slice organization enables easier testing, maintenance, and scalability.

Related Skills

Explore More Software Engineering Skills→
tmalcolm-0607tmalcolm-0607

lens-aspnet-structure

Enforce 5-layer architecture and dependency rules in LENS ASP.NET Core services.

Community
Advanced
michaelalbermichaelalber
2

shared-kernel-generator

Generate standardized .NET shared domain modules as NuGet packages.

Community
Advanced
dimsourdimsour
2

testing

Automate unit and integration testing for .NET applications with xUnit, NUnit, and MSTest.

Community
Intermediate
ArogyaReddyArogyaReddy

architecture-patterns

Apply Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to backend systems.

Community
Advanced