tenet-solidlisted

# Tenet SOLID — Design Principles Audit > Evaluates adherence to the five SOLID design principles across the codebase. Identifies god classes, type-switching anti-patterns, contract violations, fat interfaces, and misplaced concrete dependencies. ## Purpose This skill assesses whether the codebase follows the SOLID design principles — five guidelines that, when followed, produce code that is easier to extend, test, and maintain: 1. **S — Single Responsibility Principle (SRP):** A class should have one reason to change 2. **O — Open/Closed Principle (OCP):** Software entities should be open for extension but closed for modification 3. **L — Liskov Substitution Principle (LSP):** Subtypes must be substitutable for their base types without breaking correctness 4. **I — Interface Segregation Principle (ISP):** No client should be forced to depend on methods it does not use 5. **D — Dependency Inversion Principle (DIP):** High-level modules should depend on abstractions, not concrete implementations SOLID violations make code rigid, fragile, and resistant to change. They are leading indicators of future bugs when requirements evolve. ## Language Support Matrix ```yaml support: native: [typescript, javascript, python, java] heuristic: [go, rust, kotlin, swift, ruby, php, c#, all others] note: > Native support uses AST-level understanding of class definitions, inheritance, interfaces/protocols, and import graphs. Heuristic support uses pattern matching on ke