Install the "architecture-advisor" agent skill from https://github.com/codewithmukesh/dotnet-claude-kit/tree/main/skills/architecture-advisor into .claude/skills/architecture-advisor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture-advisor", then confirm the skill loads.
Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
skills CLI
$ npx skills add codewithmukesh/dotnet-claude-kit --skill architecture-advisor -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "architecture-advisor" agent skill from https://github.com/codewithmukesh/dotnet-claude-kit/tree/main/skills/architecture-advisor into .agents/skills/architecture-advisor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture-advisor", then confirm the skill loads.
Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add codewithmukesh/dotnet-claude-kit --skill architecture-advisor -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "architecture-advisor" agent skill from https://github.com/codewithmukesh/dotnet-claude-kit/tree/main/skills/architecture-advisor into .cursor/skills/architecture-advisor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture-advisor", then confirm the skill loads.
Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add codewithmukesh/dotnet-claude-kit --skill architecture-advisor -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "architecture-advisor" agent skill from https://github.com/codewithmukesh/dotnet-claude-kit/tree/main/skills/architecture-advisor into .gemini/skills/architecture-advisor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture-advisor", then confirm the skill loads.
Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
skills CLI
$ npx skills add codewithmukesh/dotnet-claude-kit --skill architecture-advisor -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "architecture-advisor" agent skill from https://github.com/codewithmukesh/dotnet-claude-kit/tree/main/skills/architecture-advisor into .github/skills/architecture-advisor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture-advisor", then confirm the skill loads.
GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add codewithmukesh/dotnet-claude-kit --skill architecture-advisor -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "architecture-advisor" agent skill from https://github.com/codewithmukesh/dotnet-claude-kit/tree/main/skills/architecture-advisor into .opencode/skills/architecture-advisor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture-advisor", then confirm the skill loads.
OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
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.
1Ask before recommending — Never prescribe an architecture without understanding the project. Run the questionnaire first to gather context…
2Right-size the architecture — The best architecture is the simplest one that handles the project's actual complexity. CRUD apps do not…
3Architecture is not permanent — Every architecture has an evolution path. Start simple and add structure when complexity demands it…
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.
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
Ask before recommending — Never prescribe an architecture without understanding the project. Run the questionnaire first to gather context about domain, team, lifetime, and constraints.
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.
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.
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
#
Question
Low Signal
High Signal
1
How many distinct business entities does the system manage?
< 10 entities
20+ entities with relationships
2
Do business rules involve multiple entities interacting?
Rules are per-entity CRUD
Complex invariants across entity groups
3
Are there business workflows with multiple steps?
Simple request → response
Sagas, approval chains, state machines
4
Do domain experts use specialized vocabulary?
Generic terms (create, update)
Ubiquitous language (underwrite, adjudicate)
Category 2: Team & Organization
#
Question
Low Signal
High Signal
5
How large is the development team?
1-3 developers
8+ developers, multiple teams
6
Do different teams own different parts of the system?
Single team owns everything
Teams aligned to business domains
7
What is the team's experience level with .NET?
Junior or mixed
Senior, experienced with patterns
Category 3: System Lifetime & Scale
#
Question
Low Signal
High Signal
8
Expected system lifetime?
< 2 years, MVP/prototype
5+ years, long-lived product
9
How many concurrent users or requests per second?
< 100 RPS
1000+ RPS, variable load
10
Will the system need to scale independently by feature area?
Uniform load
Hot spots need independent scaling
Category 4: Regulatory & Compliance
#
Question
Low Signal
High Signal
11
Are there audit trail or compliance requirements?
Basic logging sufficient
Full audit trail, SOX/HIPAA/PCI
12
Do different parts of the system have different security boundaries?
Single auth boundary
Multi-tenant, data isolation
Category 5: Existing Codebase
#
Question
Low Signal
High Signal
13
Is this greenfield or brownfield?
Greenfield, starting fresh
Brownfield, migrating from legacy
14
Are there existing architectural patterns the team follows?
No established patterns
Strong conventions in place
Category 6: Integration Complexity
#
Question
Low Signal
High Signal
15
How many external systems does this integrate with?
0-2 simple APIs
5+ systems with complex contracts
16
Are there event-driven or async communication needs?
Synchronous request/response
Event sourcing, pub/sub, eventual consistency
Decision Matrix
Map questionnaire answers to architecture recommendations:
Profile
Recommended Architecture
Why
Low domain complexity, small team, short lifetime
Vertical Slice Architecture
Minimal ceremony, fast feature delivery, easy to understand
Low-medium domain complexity, any team size, API-focused
Vertical Slice Architecture
Feature cohesion, one file per operation, natural fit for minimal APIs
Medium domain complexity, medium team, long lifetime
Clean Architecture
Enforced boundaries via project references, testable domain, clear dependency direction
High domain complexity, specialized vocabulary, complex invariants
DDD + Clean Architecture
Aggregates protect invariants, value objects model domain concepts, domain events decouple side effects
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
Architecture is not a one-time decision. Systems evolve. Here are the common migration paths:
From
To
Trigger
How
VSA
CA
Domain logic growing beyond handlers
Extract Domain + Application layers, keep features as use cases
VSA
Modular Monolith
Multiple bounded contexts emerging
Group features into modules, add module boundaries
CA
DDD + CA
Invariants becoming complex, primitive obsession
Introduce aggregates, value objects, domain events
Monolith
Modular Monolith
Teams stepping on each other, shared database coupling
Split into modules with own DbContexts and schemas
Modular Monolith
Microservices
Independent scaling needs, independent deployment
Extract 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*
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.
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
Skill
Stars
Used in
Tokens
Auto-check
Licence
Repo updated
Architecture Advisor this skillcodewithmukesh/dotnet-claude-kit
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…
Scaffolds and extends .NET 10 Minimal API modules using self-registering IModule + IEndpoint (reflection discovery) + hexagonal ports/adapters per module…
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.