Clean Ddd Hexagonal

This is a comprehensive architectural guide that brings together Clean Architecture's dependency rules, DDD's tactical patterns, and Hexagonal's ports and adapters into one coherent system. It's opinionated about when to use these patterns (teams of 5+, complex domains, long-lived systems) and explicitly warns against premature complexity for MVPs and CRUD apps. The decision trees for "where does this code go" and "entity vs value object" are genuinely useful, and the anti-patterns section catches common mistakes like anemic domain models and god aggregates. It references the full stack from Evans's Blue Book to Martin Fowler's pattern catalog. Heavy on structure and rules, which is exactly what you need when multiple developers are trying to maintain consistent boundaries across a large codebase.

install copies · 90 days. Times the install command was copied on this site in the last 90 days, bots filtered.: 7
skills.sh installs: 4.8K
GitHub stars: 62
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add ccheney/robust-skills --skill clean-ddd-hexagonal --agent claude-code

Installs into .claude/skills of the current project.

Files

Clean Architecture, DDD, and Hexagonal Architecture

Use these related patterns to solve a concrete domain or dependency problem. This is an opinionated synthesis, not a mandatory folder layout. The user's explicit instructions take precedence over this skill's guidelines.

Choose the scope

Start from the requested behavior, existing domain model, and current dependencies. Preserve the project's language and architecture unless changing them is part of the task. Simple CRUD can remain simple; team size, entity count, and file length do not determine whether DDD is appropriate.

Design question	Relevant pattern
What language and consistency rules describe the business?	DDD, bounded contexts, aggregates
Which way should source dependencies point?	Clean/Onion Architecture
How can the application use different interfaces or infrastructure?	Hexagonal ports and adapters
Do reads and writes need different models?	CQRS
Must state be reconstructed from an event history?	Event Sourcing