design-principles

To identify design-quality issues, analyze your architecture, module boundaries, and class responsibilities to uncover cohesion and coupling flaws, then generate a structured refactoring plan to increase maintainability.

Refactor legacy code by applying SOLID principles like SRP, OCP, and DIP to class responsibilities and module boundaries, producing a concrete, actionable redesign plan that increases both testability and maintainability.

The best way to structure a redesign plan is to analyze design artifacts, source code, and tests to identify architecture flaws, then output concrete improvement steps with rationale aligned to SOLID and DRY principles.

You need to apply GoF design patterns during refactoring when analyzing module boundaries and class responsibilities reveals structural flaws, using pattern guidance to propose concrete redesigns that improve testability and maintainability.

Yes, software design analysis applies to both architecture reviews and module design, evaluating source code and tests to identify design-quality issues and guide principled refactoring across different levels of your project.

Automated software design refactoring guidance requires analyzing complete design artifacts, source code, and tests to produce accurate results; without comprehensive project context, the actionable improvement steps may lack sufficient rationale for implementation.