Agent skill

Architecture Advisor

by codewithmukesh in codewithmukesh/dotnet-claude-kit

Architecture selection advisor for .NET applications. An agent skill from codewithmukesh/dotnet-claude-kit.

MITAuto-check passedDevelopment

Install Architecture Advisor

skills CLI
$ npx skills add codewithmukesh/dotnet-claude-kit --skill architecture-advisor -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install codewithmukesh/dotnet-claude-kit architecture-advisor --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/codewithmukesh/dotnet-claude-kit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/architecture-advisor .claude/skills/architecture-advisor && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
architecture-advisor
GitHub stars
751
Used in
1 other repo
Token cost
~2.9k tokens
SKILL.md length
948 words
Files
1
Skills in repo
47
Repo updated
First seen
Licence
MIT

At a glance

Architecture selection advisor for .NET applications. An agent skill from codewithmukesh/dotnet-claude-kit.

  • Works in 4 steps: Ask before recommending — Never… → Right-size the architecture — The best… → Architecture is not permanent — Every… → …
  • Asks which architecture
  • SKILL.md covers Core Principles, The Architecture Questionnaire, Decision Matrix and Patterns, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Architecture Advisor is an agent skill from codewithmukesh/dotnet-claude-kit. Architecture selection advisor for .NET applications. Asks structured questions about domain complexity, team size, system lifetime, compliance, and integration needs, then recommends the best-fit architecture: Vertical Slice, Clean Architecture, DDD + Clean Architecture, or Modular Monolith. Load this skill when the user asks "which architecture", "choose architecture", "set up project", "new project", "architecture decision", "restructure", or "how should I organize". Always load BEFORE any…

Its SKILL.md is about 2.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Design patterns and Domain-driven design. It works with .NET. The repository describes itself as: Make Claude Code a .NET 10 Expert. The licence is MIT.

When your agent uses it

  • Asks which architecture
  • Choose architecture
  • Architecture decision
  • How should I organize

Example prompts

  • “which architecture”
  • “choose architecture”
  • “set up project”
  • “/architecture-advisor”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Ask before recommending — Never prescribe an architecture without understanding the project. Run the questionnaire first to gather context…
  2. Right-size the architecture — The best architecture is the simplest one that handles the project's actual complexity. CRUD apps do not…
  3. Architecture is not permanent — Every architecture has an evolution path. Start simple and add structure when complexity demands it…
  4. Four supported architectures — dotnet-claude-kit provides first-class patterns for Vertical Slice Architecture (VSA), Clean Architecture…

What it can do on your machine

Read from SKILL.md and the folder at commit 2330089. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Architecture Advisor loads about 2.9k tokens when it runs. Until then it costs about 137 tokens; SKILL.md has 948 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~137
When it runs · the whole SKILL.md, loaded when a task matches
~2.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from codewithmukesh/dotnet-claude-kit at commit 2330089, republished under its MIT licence (© codewithmukesh). 948 words, ~2,890 tokens.

Download SKILL.mdSave it as .claude/skills/architecture-advisor/SKILL.md (or your agent's skills folder).
name
architecture-advisor
description
Architecture selection advisor for .NET applications. Asks structured questions about domain complexity, team size, system lifetime, compliance, and integration needs, then recommends the best-fit architecture: Vertical Slice, Clean Architecture, DDD + Clean Architecture, or Modular Monolith. Load this skill when the user asks "which architecture", "choose architecture", "set up project", "new project", "architecture decision", "restructure", or "how should I organize". Always load BEFORE any architecture-specific skill.

Architecture Advisor

Core Principles

  1. Ask before recommending — Never prescribe an architecture without understanding the project. Run the questionnaire first to gather context about domain, team, lifetime, and constraints.
  2. Right-size the architecture — The best architecture is the simplest one that handles the project's actual complexity. CRUD apps do not need DDD. Startups do not need Clean Architecture. Match complexity to real requirements, not aspirations.
  3. Architecture is not permanent — Every architecture has an evolution path. Start simple and add structure when complexity demands it. Document the decision so the team knows when to evolve.
  4. Four supported architectures — dotnet-claude-kit provides first-class patterns for Vertical Slice Architecture (VSA), Clean Architecture (CA), DDD + Clean Architecture, and Modular Monolith. Each has specific strengths and trade-offs.

The Architecture Questionnaire

Before recommending an architecture, ask questions across these 6 categories. Not every question applies to every project — skip irrelevant ones.

Category 1: Domain Complexity
#QuestionLow SignalHigh Signal
1How many distinct business entities does the system manage?< 10 entities20+ entities with relationships
2Do business rules involve multiple entities interacting?Rules are per-entity CRUDComplex invariants across entity groups
3Are there business workflows with multiple steps?Simple request → responseSagas, approval chains, state machines
4Do domain experts use specialized vocabulary?Generic terms (create, update)Ubiquitous language (underwrite, adjudicate)
Category 2: Team & Organization
#QuestionLow SignalHigh Signal
5How large is the development team?1-3 developers8+ developers, multiple teams
6Do different teams own different parts of the system?Single team owns everythingTeams aligned to business domains
7What is the team's experience level with .NET?Junior or mixedSenior, experienced with patterns
Category 3: System Lifetime & Scale
#QuestionLow SignalHigh Signal
8Expected system lifetime?< 2 years, MVP/prototype5+ years, long-lived product
9How many concurrent users or requests per second?< 100 RPS1000+ RPS, variable load
10Will the system need to scale independently by feature area?Uniform loadHot spots need independent scaling
Category 4: Regulatory & Compliance
#QuestionLow SignalHigh Signal
11Are there audit trail or compliance requirements?Basic logging sufficientFull audit trail, SOX/HIPAA/PCI
12Do different parts of the system have different security boundaries?Single auth boundaryMulti-tenant, data isolation
Category 5: Existing Codebase
#QuestionLow SignalHigh Signal
13Is this greenfield or brownfield?Greenfield, starting freshBrownfield, migrating from legacy
14Are there existing architectural patterns the team follows?No established patternsStrong conventions in place
Category 6: Integration Complexity
#QuestionLow SignalHigh Signal
15How many external systems does this integrate with?0-2 simple APIs5+ systems with complex contracts
16Are there event-driven or async communication needs?Synchronous request/responseEvent sourcing, pub/sub, eventual consistency

Decision Matrix

Map questionnaire answers to architecture recommendations:

ProfileRecommended ArchitectureWhy
Low domain complexity, small team, short lifetimeVertical Slice ArchitectureMinimal ceremony, fast feature delivery, easy to understand
Low-medium domain complexity, any team size, API-focusedVertical Slice ArchitectureFeature cohesion, one file per operation, natural fit for minimal APIs
Medium domain complexity, medium team, long lifetimeClean ArchitectureEnforced boundaries via project references, testable domain, clear dependency direction
High domain complexity, specialized vocabulary, complex invariantsDDD + Clean ArchitectureAggregates protect invariants, value objects model domain concepts, domain events decouple side effects
Multiple bounded contexts, team-per-domain, independent deployment potentialModular MonolithModule isolation, independent data stores, evolution path to microservices
Brownfield with existing layered architectureClean ArchitectureFamiliar to teams coming from N-tier, preserves layer separation with better dependency direction
Show full SKILL.md (367 more words)Show less
When Signals Conflict

If signals point to different architectures:

  1. Default to simpler — When in doubt, start with VSA and evolve
  2. Domain complexity wins — High domain complexity overrides team size and lifetime signals
  3. Team familiarity matters — A team experienced with CA will be more productive with CA than learning VSA, even if VSA is technically simpler
  4. Compliance drives structure — Regulatory requirements often force stricter boundaries (CA or DDD)

Patterns

Vertical Slice Architecture (VSA)

Organize by feature, not by layer. Each operation is a self-contained slice.

src/MyApp.Api/
  Features/
    Orders/CreateOrder.cs    # Request + Handler + Response + Endpoint
    Orders/GetOrder.cs
  Common/
    Behaviors/ValidationBehavior.cs
    Persistence/AppDbContext.cs

Best for: CRUD-heavy apps, APIs, MVPs, small-medium teams, short-medium lifetime. Load skill: vertical-slice

Clean Architecture (CA)

Concentric layers with dependency inversion. Domain at the center, infrastructure at the edge.

src/
  MyApp.Domain/              # Entities, interfaces, domain logic
  MyApp.Application/         # Use cases, DTOs, validation
  MyApp.Infrastructure/      # EF Core, external services
  MyApp.Api/                 # Endpoints, middleware

Best for: Medium complexity, long-lived systems, teams familiar with layered patterns. Load skill: clean-architecture

DDD + Clean Architecture

Clean Architecture with tactical DDD patterns: aggregates, value objects, domain events.

src/
  MyApp.Domain/              # Aggregates, value objects, domain events, domain services
  MyApp.Application/         # Use cases orchestrating aggregates
  MyApp.Infrastructure/      # Persistence, external service adapters
  MyApp.Api/                 # Thin endpoints

Best for: Complex domains, specialized vocabulary, strict invariants, experienced teams. Load skill: ddd + clean-architecture

Modular Monolith

Independent modules in a single deployable unit, each with its own architecture internally.

src/
  MyApp.Host/                # Wires modules together
  Modules/
    Orders/                  # Own features, own DbContext, own architecture
    Catalog/                 # Can use VSA, CA, or DDD internally
  MyApp.Shared/              # Integration event contracts only

Best for: Multiple bounded contexts, team-per-domain, future microservices extraction. Load template: modular-monolith

Evolution Paths

Architecture is not a one-time decision. Systems evolve. Here are the common migration paths:

FromToTriggerHow
VSACADomain logic growing beyond handlersExtract Domain + Application layers, keep features as use cases
VSAModular MonolithMultiple bounded contexts emergingGroup features into modules, add module boundaries
CADDD + CAInvariants becoming complex, primitive obsessionIntroduce aggregates, value objects, domain events
MonolithModular MonolithTeams stepping on each other, shared database couplingSplit into modules with own DbContexts and schemas
Modular MonolithMicroservicesIndependent scaling needs, independent deploymentExtract modules into separate deployable services

Anti-patterns

Picking Clean Architecture for a CRUD App
// BAD — 4 projects, 6+ files per feature for simple CRUD
src/MyApp.Domain/Entities/Product.cs
src/MyApp.Application/Products/CreateProduct/CreateProductCommand.cs
src/MyApp.Application/Products/CreateProduct/CreateProductHandler.cs
src/MyApp.Application/Products/CreateProduct/CreateProductValidator.cs
src/MyApp.Infrastructure/Persistence/ProductRepository.cs
src/MyApp.Api/Endpoints/ProductEndpoints.cs

// GOOD — VSA: 1 file for a simple CRUD feature
src/MyApp.Api/Features/Products/CreateProduct.cs
DDD Everywhere
// BAD — value objects and aggregates for a settings table
public class UserSettings : AggregateRoot  // overkill
{
    public ThemeName Theme { get; private set; }  // value object for "dark"/"light"?
    public void ChangeTheme(ThemeName theme) { /* domain event? really? */ }
}

// GOOD — simple entity for simple data
public class UserSettings
{
    public Guid UserId { get; init; }
    public string Theme { get; set; } = "light";
}
Premature Microservices
// BAD — splitting into 5 microservices on day one with 2 developers
OrderService (own repo, own DB, own CI/CD)
CatalogService (own repo, own DB, own CI/CD)
IdentityService (own repo, own DB, own CI/CD)
NotificationService (own repo, own DB, own CI/CD)
GatewayService (own repo, own CI/CD)

// GOOD — start as a modular monolith, extract when you have evidence
src/
  Modules/Orders/
  Modules/Catalog/
  Modules/Identity/
  Modules/Notifications/
Skipping the Questionnaire
// BAD — "I always use Clean Architecture"
User: "Set up a new project for a todo app"
Agent: *immediately scaffolds 4-project CA solution*

// GOOD — ask first, then recommend
User: "Set up a new project for a todo app"
Agent: "Let me ask a few questions about your project to recommend the best architecture..."
Agent: *runs questionnaire, recommends VSA for low-complexity app*

Decision Guide

ScenarioRecommendation
New project, unknown requirementsRun the questionnaire
Simple CRUD API, 1-3 developersVSA
Medium complexity, long-lived, experienced teamClean Architecture
Complex domain, specialized vocabularyDDD + Clean Architecture
Multiple bounded contexts, multiple teamsModular Monolith
Existing N-tier codebase, needs modernizationClean Architecture (familiar migration)
MVP / startup, speed is priorityVSA
Regulatory / compliance-heavyClean Architecture or DDD (enforced boundaries)
Will need independent scaling laterModular Monolith (extraction-ready)

© codewithmukesh, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/architecture-advisor of codewithmukesh/dotnet-claude-kit.

Open the folder on GitHubat commit 2330089

Used in 1 other repository

We found 4 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in codewithmukesh/dotnet-claude-kit, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Architecture Advisor next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Architecture Advisor compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Architecture Advisor this skillcodewithmukesh/dotnet-claude-kit7511 repos~2.9kAutomated safety check: PassMIT
Clean Architecture DotnetSebastienDegodez/copilot-instructions197—~5.1kAutomated safety check: PassApache-2.0
Dotnet Clean Architecturefmflurry/settings-opencode171—~5.5kAutomated safety check: PassMIT
Architecturemanagedcode/dotnet-skills486—~659Automated safety check: PassMIT
GitVersion .NET DevelopmentGitTools/GitVersion3.1k—~1.7kAutomated safety check: PassMIT
Akka.Hosting Actor PatternsAaronontheweb/dotnet-skills1.2k1 repos~5kAutomated safety check: PassMIT

Similar skills

  • Clean Architecture Dotnet

    SebastienDegodez/copilot-instructions

    A skill your agent uses when domain logic leaks into API/Infrastructure, project references violate layer boundaries, or you need to decide between CQS (always), CQRS bus (complex domains), and DDD…

    197 GitHub stars~5.1k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Dotnet Clean Architecture

    fmflurry/settings-opencode

    Scaffolds and extends .NET 10 Minimal API modules using self-registering IModule + IEndpoint (reflection discovery) + hexagonal ports/adapters per module…

    171 GitHub stars~5.5k tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Architecture

    managedcode/dotnet-skills

    Design or review .NET solution architecture across modular monoliths, clean architecture, vertical slices, microservices, DDD, CQRS, and cloud-native boundaries without over-engineering.

    486 GitHub stars~659 tokensUpdated today
    DevelopmentAuto-check passed
  • GitVersion .NET Development

    GitTools/GitVersion

    Gives repository-specific .NET guidance for GitVersion: build and test commands, central package management, project layout and coding conventions.

    3.1k GitHub stars~1.7k tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Akka.Hosting Actor Patterns

    Aaronontheweb/dotnet-skills

    Shows how to build entity actors with Akka.Hosting so the same code runs in local unit tests and in a sharded cluster in production.

    1.2k GitHub starsUsed in 1 repo~5k tokens
    DevelopmentAuto-check passed
  • Ddd Teaching Skill

    sazardev/goca

    Enseña Domain-Driven Design y Clean Architecture de forma guiada usando Goca CLI.

    298 GitHub stars~5.3k tokensUpdated 2 mo ago
    DevelopmentAuto-check passed

More from codewithmukesh/dotnet-claude-kit

All 47 skills in this repo
  • API Versioning

    codewithmukesh/dotnet-claude-kit

    API versioning strategies for ASP.NET Core. An agent skill from codewithmukesh/dotnet-claude-kit.

    751 GitHub starsUsed in 1 repo~1.2k tokens
    Auto-check passed
  • Scaffold

    codewithmukesh/dotnet-claude-kit

    Architecture-aware feature scaffolding for .NET 10 projects.

    751 GitHub stars~1.7k tokensUpdated 2 mo ago
    Auto-check passed
  • Aspire

    codewithmukesh/dotnet-claude-kit

    .NET Aspire for cloud-native orchestration. An agent skill from codewithmukesh/dotnet-claude-kit.

    751 GitHub starsUsed in 1 repo~1.5k tokens
    Auto-check passed
  • Authentication

    codewithmukesh/dotnet-claude-kit

    Authentication and authorization for ASP.NET Core. An agent skill from codewithmukesh/dotnet-claude-kit.

    751 GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed
  • Caching

    codewithmukesh/dotnet-claude-kit

    Caching strategies for .NET 10 applications. An agent skill from codewithmukesh/dotnet-claude-kit.

    751 GitHub starsUsed in 1 repo~1.4k tokens
    Auto-check passed
  • CI CD

    codewithmukesh/dotnet-claude-kit

    CI/CD pipelines for .NET applications. An agent skill from codewithmukesh/dotnet-claude-kit.

    751 GitHub starsUsed in 1 repo~1.4k tokens
    Auto-check passed

Works with

Categories

Questions about Architecture Advisor

What does Architecture Advisor do?

Architecture selection advisor for .NET applications. An agent skill from codewithmukesh/dotnet-claude-kit. Architecture Advisor is an agent skill from codewithmukesh/dotnet-claude-kit.NET applications.

When should I use Architecture Advisor?

Architecture Advisor fits situations like: asks which architecture; choose architecture; architecture decision; how should I organize.

How do I install Architecture Advisor in Claude Code?

Run `npx skills add codewithmukesh/dotnet-claude-kit --skill architecture-advisor -a claude-code`. Or copy the skill folder (skills/architecture-advisor in codewithmukesh/dotnet-claude-kit) into .claude/skills/architecture-advisor in your project. Claude Code loads it when a task matches its description.

How do I install Architecture Advisor in Codex?

Run `npx skills add codewithmukesh/dotnet-claude-kit --skill architecture-advisor -a codex`. Or copy the skill folder (skills/architecture-advisor in codewithmukesh/dotnet-claude-kit) into .agents/skills/architecture-advisor in your project. Codex loads it when a task matches its description.

Can I use Architecture Advisor in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add codewithmukesh/dotnet-claude-kit --skill architecture-advisor -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/architecture-advisor, .gemini/skills/architecture-advisor, .github/skills/architecture-advisor and .opencode/skills/architecture-advisor in your project.

What does Architecture Advisor need to run?

SKILL.md names no scripts, command-line tools or credentials: Architecture Advisor is instructions for the agent only.

Does Architecture Advisor access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Architecture Advisor safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Architecture Advisor use?

Architecture Advisor is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Architecture Advisor use?

About 2.9k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Architecture Advisor?

Skills that share tags, products or a category with Architecture Advisor: Clean Architecture Dotnet (SebastienDegodez/copilot-instructions, 197 stars), Dotnet Clean Architecture (fmflurry/settings-opencode, 171 stars), Architecture (managedcode/dotnet-skills, 486 stars) and GitVersion .NET Development (GitTools/GitVersion, 3.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Architecture Advisor?

codewithmukesh (a GitHub organization) maintains it in codewithmukesh/dotnet-claude-kit, which has 751 GitHub stars. The repository holds 47 skills in this directory. The repository was last updated on August 7, 2026.

Source: codewithmukesh/dotnet-claude-kit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.