clean-architecture

When to Use

• Designing a new service or module from scratch
• Deciding which layer a piece of code belongs to
• Reviewing code for architecture violations
• Onboarding someone to the project's architecture
• Evaluating whether to add a dependency to a layer

This skill defines the principles. For language-specific implementation, see:

• Go: go-microservice-scaffold skill (directory structure, naming, scaffold steps)
• Flutter: flutter-scaffold skill (feature-based structure, layers)

The Dependency Rule

This is the ONE rule that makes Clean Architecture work. Everything else follows from it.