excalidash-clean-architecture-reviewer

Draws and audits Clean Architecture diagrams as concentric rings enforcing the Dependency Rule.

2|Updated Jun 17, 2026
One-click install
npx skills add https://github.com/gabedsam01/excalidash-v2 --skill excalidash-clean-architecture-reviewer-gabedsam01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: excalidash-clean-architecture-reviewer
Source: https://github.com/gabedsam01/excalidash-v2/tree/main/skills/excalidash/excalidash-clean-architecture-reviewer
Command: npx skills add https://github.com/gabedsam01/excalidash-v2 --skill excalidash-clean-architecture-reviewer-gabedsam01

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? It produces or reviews Clean (Onion) architecture diagrams for a single system as four concentric rings — Entities, Use Cases, Interface Adapters, Frameworks & Drivers — and proves the Dependency Rule by ensuring every cross-ring dependency arrow points inward, catching outward-pointing edges and framework leaks into the core. ## Core Features & Use Cases - Diagram generation: Create Clean Architecture diagrams from a prompt, a template, an existing layered drawing, or by reverse-engineering a repository's package structure into the four rings. - Dependency Rule validation: Run architecture validation to confirm zero outward-pointing edges, correct port ownership, and a framework-free core, then apply suggested improvements. - Quality loop: Lint, score, repair, and polish the drawing until it reaches a score of at least 95 with zero hard blockers, with rollback to checkpoints on regression. - Use Case: Ask for a Clean Architecture view of your order service — Order and Money entities, a PlaceOrder use case owning repository and payment ports, Express controllers, and Postgres/Stripe on the outer ring — and get a validated diagram with a shareable link and export. ## Quick Start Ask the assistant to draw your system in Clean Architecture with its entities, use cases, adapters, and frameworks, and to prove every dependency arrow points inward.

Frequently Asked Questions about excalidash-clean-architecture-reviewer

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

FAQPage Schema
How do I draw a Clean Architecture diagram from a description?

Describe your system's entities, use cases, adapters, and frameworks, and the skill generates four concentric rings via the clean architecture preset. Ports sit on the inner edge of the owning ring and every cross-ring arrow points inward.

How do I check if my diagram violates the Dependency Rule?

Run validate_architecture on the drawing; it reports any outward-pointing edges where an inner ring depends on an outer ring. Fix violations by introducing a port in the inner ring and having the outer adapter implement it inward.

Can I generate a Clean Architecture view from an existing repository?

Yes, create_from_repo_analysis maps your package structure into the four rings, for example domain to Entities and infra to Frameworks & Drivers. You then re-classify packages and run the lint-score-repair loop before validating.

When should I use the hexagonal pattern instead of Clean Architecture rings?

Use the hexagonal preset when the request is ports-and-adapters with an explicit hexagon and named driving/driven ports. Concentric Clean rings are a different visual contract focused on the Dependency Rule across four layers.

Why does my architecture diagram score below 95?

Common causes are hard blockers like arrows crossing text, ring titles overlapping, or nodes straddling ring boundaries, plus density and small-font penalties. Run repair_drawing and re-lint until the score reaches 95 with no blockers.

How are secrets like database URLs handled in diagrams?

Connection strings, API keys, and tokens are redacted to typed placeholders before any tool call, and the outer ring is labeled by concept such as Postgres Gateway. Exports are re-scanned as a backstop to confirm no credentials leak.