Imported from Postpartum-genushyacinthus29/dotnet-skills (skills/dotnet-architecture/SKILL.md). Install upstream with npx skills add Postpartum-genushyacinthus29/dotnet-skills --skill dotnet-architecture. Copyright stays with the author.

.NET Architecture

Name: dotnet-architecture
Author: Postpartum-genushyacinthus29

Trigger On

choosing architecture for a new or evolving .NET system
reviewing layer boundaries, domain boundaries, or service decomposition
deciding whether clean architecture, vertical slices, CQRS, or microservices are justified

Workflow

Start from business capability boundaries and change frequency, not from a preferred diagram style.
Use simple modular monolith patterns by default, and move to microservices only when team autonomy, scale, or deployment boundaries justify the added operational cost.
Apply DDD and CQRS where business rules are genuinely complex; avoid forcing aggregates and command pipelines into CRUD-heavy code with no payoff.
Keep dependencies flowing inward when using clean architecture, but avoid creating extra projects that add ceremony without ownership clarity.
Make integration boundaries explicit: contracts, storage ownership, messaging, consistency model, and observability expectations.
Use dotnet-aspire when local orchestration, service discovery, and developer observability are part of the architecture story.

Deliver

an architecture direction that matches system complexity
clear project and dependency boundaries
migration notes or tradeoffs when changing an existing structure

Validate

the proposed structure reduces rather than increases accidental complexity
data ownership and integration paths are explicit
the architecture is testable and operable, not just diagram-friendly

References

references/patterns.md - detailed implementations of Clean Architecture, Vertical Slices, DDD, CQRS, Modular Monolith, and Microservices with C# 12+ examples
references/anti-patterns.md - common architectural mistakes including over-abstraction, anemic domain models, premature microservices, and cargo cult patterns

{ "ocm": "1", "id": "postpartum-genushyacinthus29-dotnet-skills-dotnet-architecture", "kind": "skill", "name": "dotnet-architecture", "description": "Design or review .NET solution architecture across modular monoliths, clean architecture, vertical slices, microservices, DDD, CQRS, and cloud-native boundaries without over-engineering.", "publisher": "Postpartum-genushyacinthus29", "version": "1.0.0", "capabilities": { "domains": [ "general" ], "tags": [ "skill-md", "github" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Design or review .NET solution architecture across modular monoliths, clean architecture, vertical slices, microservices, DDD, CQRS, and cloud-native boundaries without over-engineering." ], "primary": false, "metadata": { "source": { "provider": "github", "repository": "https://github.com/Postpartum-genushyacinthus29/dotnet-skills", "path": "skills/dotnet-architecture/SKILL.md", "ref": "86190efe7d6076d85a153506b21b770e7c049aae", "url": "https://github.com/Postpartum-genushyacinthus29/dotnet-skills/blob/86190efe7d6076d85a153506b21b770e7c049aae/skills/dotnet-architecture/SKILL.md", "key": "Postpartum-genushyacinthus29/dotnet-skills/skills/dotnet-architecture/SKILL.md" }, "compatibility": "Best when project structure, service boundaries, or long-term maintainability are in scope." }, "instructions": "# .NET Architecture\n\n## Trigger On\n\n- choosing architecture for a new or evolving .NET system\n- reviewing layer boundaries, domain boundaries, or service decomposition\n- deciding whether clean architecture, vertical slices, CQRS, or microservices are justified\n\n## Workflow\n\n1. Start from business capability boundaries and change frequency, not from a preferred diagram style.\n2. Use simple modular monolith patterns by default, and move to microservices only when team autonomy, scale, or deployment boundaries justify the added operational cost.\n3. Apply DDD and CQRS where business rules are genu", "cost": { "context_tokens": 474 } }

dotnet-architecture

About

.NET Architecture

Trigger On

Workflow

Deliver

Validate

References

Use it

Manifest

Reviews