python-oop-designer

To design SOLID-compliant Python OOP class hierarchies, define clear interfaces using Protocols or ABCs, favor composition over inheritance where appropriate, and apply established design patterns to ensure robust and maintainable class structures.

Use Python Protocols for structural subtyping when you want flexible interface definition without explicit inheritance, and use ABCs when you need strict enforcement and shared implementation logic across a class hierarchy.

The best way to refactor tangled Python class hierarchies is to perform an architecture review, identify SOLID principle violations, extract interfaces, and restructure dependencies using composition and established design patterns.

Yes, you can use this during Python module architecture reviews to evaluate existing structures, identify SOLID drift, and recommend appropriate design patterns to resolve brittle interfaces and tangled dependencies.

Yes, this approach guides decisions between composition and inheritance by evaluating your domain requirements against SOLID principles, ensuring your Python OOP design avoids brittle hierarchies and promotes flexible code reuse.

Python OOP architecture becomes brittle when adding new features because class structures drift from SOLID principles, leading to tangled hierarchies and rigid interfaces that violate dependency inversion and open-closed guidelines.