software-architecture

What problem does it solve? Writing maintainable .NET/C# code requires consistent architectural decisions, and without clear guidance teams end up with tangled business logic, generic helper dumping grounds, and reinvented wheels. This Skill provides concrete rules for structuring code with Clean Architecture and Domain-Driven Design. ## Core Features & Use Cases - Architecture Guidance: Enforces Clean Architecture and DDD principles such as separating domain entities from infrastructure and keeping business logic out of controllers and UI components. - Code Style Rules: Defines conventions for early returns, function and file length limits, naming patterns, and avoiding deep nesting. - Library-First Decision Making: Directs developers to evaluate existing NuGet packages and services (e.g., Microsoft.Extensions.Http.Resilience, MSAL) before writing custom utilities. - Use Case: When designing a new order-processing service in C#, use this Skill to structure bounded contexts, name domain-specific classes like OrderCalculator, and reuse existing libraries instead of building custom retry or authentication logic. ## Quick Start Review my C# order service code and suggest improvements based on Clean Architecture and DDD principles.