solid-principles

To enforce SOLID design principles during refactoring, walk a candidate class through five sequential gating phases (SRP, OCP, LSP, ISP, DIP) that verify single responsibility, extension points, substitutability, interface segregation, and dependency direction to prevent architectural drift.

Decomposing a god class requires applying the single responsibility gate to identify overlapping duties, then iterating through the remaining SOLID gates to split responsibilities, abstract dependencies, and establish a cohesive, plug-in extension-friendly architecture.

The LSP gating phase checks substitutability by verifying that derived classes can replace their base types without altering program correctness, ensuring behavioral consistency and preventing architectural drift during design reviews.

Yes, you can use the phased SOLID gating approach to review existing code modules by applying each gate check to validate single responsibility, appropriate extension points, and directed dependencies, ensuring current systems remain maintainable and extensible.

You need to apply interface segregation when clients are forced to depend on methods they do not use, using the ISP gate to split bloated interfaces into cohesive, client-specific contracts during design reviews and refactoring.

Dependency inversion matters for plug-in architectures because the DIP gate directs high-level modules to depend on abstractions rather than concrete implementations, enabling flexible extensions and preventing tightly coupled architectural drift.