architecture-advisor

Select a .NET architecture pattern from questionnaire inputs.

224|87|Updated Dec 15, 2018
One-click install
npx skills add https://github.com/Resgrid/Core --skill architecture-advisor-resgrid
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-advisor
Source: https://github.com/Resgrid/Core/tree/main/.opencode/skills/architecture-advisor
Command: npx skills add https://github.com/Resgrid/Core --skill architecture-advisor-resgrid

SYSTEM DOCUMENTATION & REQUIREMENTS

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?”

Frequently Asked Questions about architecture-advisor

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

FAQPage Schema
How do I choose the right .NET architecture for a new project?

Choosing the right .NET architecture pattern requires evaluating domain complexity, team organization, system scale, compliance needs, and integration complexity. A structured questionnaire maps these conflicting project signals into a best-fit recommendation among Vertical Slice, Clean Architecture, DDD, or Modular Monolith.

What is the difference between Vertical Slice and Clean Architecture in .NET?

Vertical Slice architecture organizes code feature-first for lower domain complexity, while Clean Architecture enforces stricter boundary separation. DDD + Clean Architecture adds complex domain modeling, and Modular Monolith isolates modules for scaling within a single deployable unit.

When should I use Domain-Driven Design with Clean Architecture?

Use DDD with Clean Architecture when your .NET project exhibits high domain complexity, strict regulatory constraints, and a long system lifetime. This pattern provides strict boundary enforcement and complex domain modeling for large-scale, evolving systems.

How do I refactor a .NET codebase when architecture requirements are uncertain?

Refactoring a .NET codebase with uncertain or conflicting requirements involves evaluating domain complexity, existing patterns, and team organization. Structured decision rules map these inputs to a target architecture like Modular Monolith and outline practical migration paths as complexity grows.

Does a Modular Monolith fit a small .NET team with complex integrations?

A Modular Monolith fits a small .NET team handling complex integrations by encapsulating domain boundaries within isolated modules. It provides scalable architecture without the operational overhead of distributed microservices while maintaining strict internal separation.