skills.rest
managedcode
managedcodeOFFICIAL
Explore all skills by this author →
WebsiteGitHub

dotnet-architecture

Guide .NET solution architecture design and review across modular monoliths, microservices, and DDD.

466|35|Updated Mar 15, 2026
Search Tags:#architecture#design patterns#microservices#ddd#clean architecture#dotnet#cqrs
One-click install
npx skills add https://github.com/managedcode/dotnet-skills --skill dotnet-architecture-managedcode
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dotnet-architecture
Source: https://github.com/managedcode/dotnet-skills/tree/main/skills/dotnet-architecture
Command: npx skills add https://github.com/managedcode/dotnet-skills --skill dotnet-architecture-managedcode

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps .NET developers make informed decisions about their solution architecture, avoiding common pitfalls and ensuring maintainability and scalability.

Core Features & Use Cases

  • Architecture Guidance: Provides strategies for modular monoliths, clean architecture, vertical slices, microservices, DDD, CQRS, and cloud-native designs.
  • Pattern Selection: Helps choose the right architectural approach based on business needs and complexity.
  • Anti-Pattern Avoidance: Identifies and explains common architectural mistakes to prevent them.
  • Use Case: When starting a new .NET project, use this Skill to explore different architectural options and understand the trade-offs between modular monoliths and microservices.

Quick Start

Use the dotnet-architecture skill to explore options for designing a new .NET solution.

Frequently Asked Questions about dotnet-architecture

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

FAQPage Schema
How do I choose between a modular monolith and microservices for a new .NET solution?▼

Implementing clean architecture in .NET involves separating domain logic from infrastructure using vertical slices and dependency inversion. This Skill reviews your solution boundaries and guides the placement of domain-driven design principles to ensure maintainability and scalability.

When should I apply domain-driven design and CQRS in my .NET architecture?▼

Apply domain-driven design and CQRS when business complexities require distinct boundaries between read and write models. This Skill facilitates decision-making by analyzing your domain capabilities and change frequency to determine if these patterns are necessary or if they introduce over-engineering.

What are common anti-patterns to avoid when designing .NET microservices?▼

Common .NET microservices anti-patterns include incorrect boundary definition and unnecessary complexity from over-engineering. This Skill identifies and explains architectural mistakes, helping you avoid inappropriate service splits and ensuring your distributed design remains maintainable.

Can I use vertical slice architecture instead of traditional layered design for .NET projects?▼

Designing a cloud-native .NET architecture requires evaluating microservices boundaries and scalability requirements before writing code. This Skill provides strategies for cloud-native designs, ensuring your solution architecture aligns with business capabilities and avoids common structural pitfalls.

Related Skills

Explore More Software Engineering Skills→
TonyQ-AITonyQ-AI
9

domain-modeling

Extract core business concepts, entity relationships, and domain rules from requirement specifications.

Community
Intermediate
ronnythedevronnythedev
69

dotnet-clean-architecture

Scaffold a layered .NET solution with Clean Architecture boundaries.

Community
Advanced
markus41markus41
18

project-fingerprinting

Analyze codebases to detect technology stacks, architecture, and quality signals.

Community
Advanced
ryanthedevryanthedev
60

designing-deep-modules

Generate design approaches and evaluate trade-offs for new modules.

Community
Advanced