What problem does it solve?
This Skill helps teams avoid costly architecture misalignment by guiding them through structured requirements gathering before selecting a .NET architecture pattern.
Core Features & Use Cases
- Architecture selection via questionnaire: Asks targeted questions on domain complexity, team organization, system lifetime/scale, compliance needs, existing patterns, and integration complexity.
- Actionable recommendation mapping: Converts questionnaire “low vs high signal” inputs into one of four recommended approaches: Vertical Slice Architecture, Clean Architecture, DDD + Clean Architecture, or Modular Monolith.
- Guidance for conflicting signals and evolution: Provides decision rules when inputs conflict and outlines practical migration paths as complexity grows.
Use case example: Starting a new .NET service with unknown domain complexity and integrations, it helps you choose between a feature-first vertical slice vs stronger boundary enforcement with Clean Architecture or DDD.
Quick Start
Ask the AI: “Which architecture should we use for a new .NET project, and which pattern fits our domain, team size, compliance, and integrations?”