Individual skill

clean-architecture

Clean Architecture principles and best practices from Robert C. Martin's book. This skill should be used when designing software systems, reviewing code structure, or refactoring applications to achieve better separation of concerns. Triggers on tasks involving layers, boundaries, dependency direction, entities, use cases, or system architecture.

skills/.experimental/clean-architecture/SKILL.md

Read pinned source

Source commit cf93c57cac89d6fc3e4194686000411567f5caf3

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Not checked yet
Last checked: Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 222
Repository last updated: Aug 15, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 7,397 bytes
assets/templates/_template.mddoc · 1,045 bytes
metadata.jsonasset · 1,050 bytes
references/_sections.mddoc · 1,832 bytes
references/adapt-anti-corruption-layer.mddoc · 3,799 bytes
references/adapt-controller-thin.mddoc · 3,313 bytes
references/adapt-gateway-abstraction.mddoc · 3,476 bytes
references/adapt-mapper-translation.mddoc · 2,795 bytes
references/adapt-presenter-formats.mddoc · 3,446 bytes
references/bound-boundary-cost-awareness.mddoc · 3,127 bytes
references/bound-defer-decisions.mddoc · 3,071 bytes
references/bound-humble-object.mddoc · 3,229 bytes
references/bound-main-component.mddoc · 3,029 bytes
references/bound-partial-boundaries.mddoc · 3,057 bytes
references/bound-service-internal-architecture.mddoc · 5,808 bytes
references/comp-common-closure.mddoc · 2,171 bytes
references/comp-common-reuse.mddoc · 2,140 bytes
references/comp-reuse-release-equivalence.mddoc · 2,290 bytes
references/comp-screaming-architecture.mddoc · 2,302 bytes
references/comp-stable-dependencies.mddoc · 3,570 bytes
references/dep-acyclic-dependencies.mddoc · 2,388 bytes
references/dep-data-crossing-boundaries.mddoc · 1,963 bytes
references/dep-interface-ownership.mddoc · 1,965 bytes
references/dep-inward-only.mddoc · 2,004 bytes
references/dep-no-framework-imports.mddoc · 2,160 bytes
references/dep-stable-abstractions.mddoc · 2,177 bytes
references/entity-encapsulate-invariants.mddoc · 2,816 bytes
references/entity-no-persistence-awareness.mddoc · 2,515 bytes
references/entity-pure-business-rules.mddoc · 1,946 bytes
references/entity-rich-not-anemic.mddoc · 3,250 bytes
references/entity-value-objects.mddoc · 2,419 bytes
references/frame-di-container-edge.mddoc · 3,123 bytes
references/frame-domain-purity.mddoc · 3,564 bytes
references/frame-logging-abstraction.mddoc · 3,232 bytes
references/frame-orm-in-infrastructure.mddoc · 3,213 bytes
references/frame-web-in-infrastructure.mddoc · 3,558 bytes
references/test-boundary-verification.mddoc · 3,432 bytes
references/test-layer-isolation.mddoc · 3,377 bytes
references/test-testable-design.mddoc · 3,387 bytes
references/test-tests-are-architecture.mddoc · 3,926 bytes
references/usecase-explicit-dependencies.mddoc · 3,291 bytes
references/usecase-input-output-ports.mddoc · 2,738 bytes
references/usecase-no-presentation-logic.mddoc · 3,168 bytes
references/usecase-orchestrates-not-implements.mddoc · 2,956 bytes
references/usecase-single-responsibility.mddoc · 3,084 bytes
references/usecase-transaction-boundary.mddoc · 2,694 bytes

Read excerpt


# Clean Architecture Best Practices

Comprehensive guide to Clean Architecture principles for designing maintainable, testable software systems. Based on Robert C. Martin's "Clean Architecture: A Craftsman's Guide to Software Structure and Design." Contains 42 rules across 8 categories, prioritized by architectural impact.

## When to Apply

Reference these guidelines when:
- Designing new software systems or modules
- Structuring dependencies between layers
- Defining boundaries between business logic and infrastructure
- Reviewing code for architectural violations
- Refactoring coupled systems toward cleaner structure

## Rule Categories by Priority