clean-code-principles

Fundamental software design principles, SOLID, design patterns, and clean code practices. Language-agnostic guidelines for writing maintainable, scalable software.

| 1 | SOLID Principles | CRITICAL | solid- | | 2 | Core Principles | CRITICAL | core- | | 3 | Design Patterns | HIGH | pattern- | | 4 | Code Organization | HIGH | org- | | 5 | Naming & Readability | MEDIUM | name- | | 6 | Functions & Methods | MEDIUM | func- | | 7 | Comments & Documentation | LOW | doc- |

| Single Responsibility | A class should have only one reason to change | | Open/Closed | Open for extension, closed for modification | | Liskov Substitution | Subtypes must be substitutable for base types | | Interface Segregation | Don't force clients to depend on unused interfaces | | Dependency Inversion | Depend on abstractions, not concretions |