software-architecture

To diagnose code smells and choose a design pattern, analyze tight coupling, rigid architectures, and unclear responsibilities. Route these design problems to the best-fit GoF pattern, SOLID principle, or hexagonal architecture, and outline a concrete refactor plan with before and after guidance.

Fix hard-to-test code by applying hexagonal architecture and SOLID principles to separate core logic from external dependencies. Diagnose unclear responsibilities and tight coupling, then route them to a composable design pattern that isolates business rules for easier unit testing.

The best way to resolve tight coupling and rigid architectures is diagnosing the specific design pressures and routing them to suitable structural patterns. Apply targeted refactor steps using SOLID principles or composable designs to decouple modules and restore architectural flexibility.

You need a design pattern reference when diagnosing design problems like coupling, rigidity, or testability issues. Use it to route the identified code smell to the most suitable GoF pattern, hexagonal architecture, or SOLID principle, and generate actionable before and after refactoring guidance.

To implement a Strategy or Decorator pattern refactor, diagnose the design problem, route it to the chosen pattern reference, and follow the actionable implementation steps. Use the provided before and after guidance to replace rigid logic with composable, decoupled designs.