Architecture Review
Review Clean Architecture boundaries, dependency direction, layering decisions, and abstraction quality in .NET solutions. Use when evaluating project structure, new dependencies, service boundaries, or architectural drift.
Install
npx skills add DIL8654/claude-code-dotnet-template --skill architecture-reviewgit clone --depth 1 https://github.com/DIL8654/claude-code-dotnet-template.git /tmp/claude-code-dotnet-template
mkdir -p ~/.claude/skills
cp -r /tmp/claude-code-dotnet-template/.claude/skills/architecture-review ~/.claude/skills/architecture-reviewPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Architecture Review Skill Audit a .NET solution for boundary integrity, dependency direction, and long-term maintainability. ## When to Use - Reviewing a new solution or template - Evaluating pull requests that add new projects or references - Checking whether business logic is in the wrong layer - Investigating architectural drift in an existing codebase --- ## Quick Reference: Common Issues | Issue | Symptom | Impact | |-------|---------|--------| | Inward dependency violation | Domain references Infrastructure or WebApi | Business logic becomes framework-coupled | | Thin abstraction with no value | Interface with one trivial implementation and no boundary role | Extra indirection with no payoff | | Fat controller | Controllers performing orchestration, validation, and persistence | Harder testing, duplicated behavior | | Infrastructure leakage | Azure SDK types or EF Core entities appear in Application | Vendor and persistence coupling | | Anemic boundary | Application layer just forwards calls without use-case logic | Layering exists on paper only | --- ## Target Layer Responsibilities | Layer | Owns | Must Avoid | |------|------|------------| | Domain | Entities, value objects, domain rules | EF Core, HTTP, Azure SDKs, controllers | | Application | Use cases, DTOs, interfaces, orchestration | Database-specific code, transport models | | Infrastructure | EF Core, repositories, SDK clients, file/storage integrations | Core business rules |
Details
- Skill name
architecture-review- Repository
- DIL8654/claude-code-dotnet-template
- Path
.claude/skills/architecture-review/SKILL.md- License
- GPL-3.0
- Repo updated
- 24 March 2026
FAQ
What does the Architecture Review skill do?
Review Clean Architecture boundaries, dependency direction, layering decisions, and abstraction quality in .NET solutions. Use when evaluating project structure, new dependencies, service boundaries, or architectural drift.
How do I install the Architecture Review skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add DIL8654/claude-code-dotnet-template --skill architecture-review. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Architecture Review popular?
It lives in DIL8654/claude-code-dotnet-template, which has 9 GitHub stars and 5 forks.
Related skills
API Contract Review
9DIL8654/claude-code-dotnet-template
Review ASP.NET Core Web API contracts for HTTP semantics, versioning, backward compatibility, and response consistency. Use when the user asks to review an API, check endpoints, validate REST behavior, or before releasing contract changes.
Azure Integration
9DIL8654/claude-code-dotnet-template
Add Azure services to .NET applications with Managed Identity, typed options, infrastructure isolation, and production-safe configuration. Use when wiring Key Vault, App Configuration, Storage, Service Bus, or Azure Identity patterns.
Clean Code
9DIL8654/claude-code-dotnet-template
Prefer small, explicit, readable C# code and pragmatic refactoring. Use for cleanup, maintainability reviews, naming improvements, duplication removal, and simplifying overly complex implementations.
Adobe Express Cors and Backend
9Sandgrouse/adobe-express-dev-skill
Diagnose and fix CORS errors between Adobe Express add-on UI and backend APIs across local development, private listing, and public listing stages. Use when browser requests fail with preflight, Access-Control-Allow-Origin, Access-Control-Allow-Headers, or OPTIONS issues; when moving from localhost to hosted add-on URL; when deciding where network calls belong (iframe vs sandbox); or when hardening backend origin policy for production.
Token Efficiency
9prangishviliAbe/agent-skills
Make responses and agent work cheaper to read and to run without losing correctness: concise answers, TL;DR, brief status updates and final summaries, just-the-code replies, and lean tool use that avoids rereading files, dumping logs, and repeating checks. Use whenever the user asks to be brief, short, or concise, says "less text", "just the code", "TLDR", or "save tokens", complains about limits or cost, or runs a long session where context is filling up. Puts the answer first, keeps the evidence, failures, and caveats that change decisions, replies in the user's language, and never trades co
Scylladb Alternator
9scylladb/agent-skills
Guide users building against ScyllaDB's DynamoDB-compatible API (Alternator). Use this skill when a user is porting a DynamoDB application to ScyllaDB, using boto3/AWS SDK clients against ScyllaDB, or asking about Alternator setup, write isolation, or load balancing. CQL schema design goes to scylladb-data-modeling. Triggers on "Alternator", "DynamoDB API", "DynamoDB compatible", "boto3 with ScyllaDB", "migrate from DynamoDB", "aws-sdk against ScyllaDB", "alternator_port", "alternator_write_isolation".
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.