design-principles

Code design audits evaluate your repository against established design principles like SOLID, DRY, and KISS. The process detects principle violations, scores findings by impact and effort, and generates a prioritized DESIGN_AUDIT.md report for remediation.

Assessing code design health before a refactor requires auditing the codebase against core design principles. This surfaces structural issues missed by linters, scores findings by impact and effort, and outputs a prioritized DESIGN_AUDIT.md to guide remediation efforts.

Yes, you can run a design principles audit on an unfamiliar codebase during onboarding. It evaluates code against well-known principles like SOLID and Separation of Concerns, running adversarial debates on contested violations to generate a prioritized DESIGN_AUDIT.md.

Yes, the design audit checks for Law of Demeter and Separation of Concerns violations. It audits codebases against SOLID, DRY, YAGNI, KISS, Composition over Inheritance, and the code-relevant 12-Factor subset to surface design health issues.

Contested design principle violations are evaluated through an adversarial debate mechanism during the audit. This process scores findings by impact and effort, resolving disputes to generate a prioritized DESIGN_AUDIT.md with clear remediation recommendations.

Use a design principles audit instead of standard static analysis tools when reviewing code quality beyond what linters catch. It evaluates architectural design health against principles like SOLID and DRY, providing impact and effort scores for prioritized remediation.