Clean Architecture Guide
Implement Uncle Bob's Clean Architecture to create systems where business rules are isolated from infrastructure concerns. Dependencies point inward, and the inner layers know nothing about the outer layers.
Usage
Ask about organizing your codebase with Clean Architecture, defining use case boundaries, or managing dependencies between layers.
Examples
- "How do I structure a Python project with Clean Architecture?"
- "What belongs in the use case layer vs the entity layer?"
- "How do I handle database access in Clean Architecture?"
Guidelines
- Dependencies must always point inward toward higher-level policies
- Entities encapsulate enterprise-wide business rules
- Use cases encapsulate application-specific business rules
- Interface adapters convert data between use cases and external formats
- Frameworks and drivers are details that belong in the outermost layer