clean-architecture

42 Clean Architecture rules organized by priority for designing maintainable, testable software systems. 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. Reference these guidelines when: Read individual reference files for detailed explanations and code examples: - Covers 8 rule categories from dependency direction and entity design (critical) through testing architecture (low-medium), each with specific guidance and code examples - Dependency rules enforce inward-pointing dependencies, interface ownership, and acyclic component graphs to prevent architectural decay - Entity and use case rules isolate business logic from frameworks, persistence, and presentation concerns through clear boundaries and explicit ports - Includes practical patterns like humble objects, anti-corruption layers, and partial boundaries for phased architectural improvements - 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 - dep-inward-only - Source dependencies point...