cc-routine-and-class-design

To evaluate class design quality, run a design checklist in CHECKER mode to surface LSP violations, containment defaults, and parameter limits with severity labels like VIOLATION, WARNING, or PASS.

Decide between inheritance versus containment by using APPLIER mode, which guides interface design decisions and cohesion improvements to ensure long-term maintainability and adherence to LSP.

Refactor a legacy class with deep inheritance by invoking the skill to evaluate whether to extract routines or refactor interfaces, applying strict containment defaults and checking for empty overrides.

A routine design checklist assesses interface maintainability by enforcing strict adherence to LSP, containment defaults, parameter limits, and the avoidance of empty overrides during code reviews.

Yes, you can use APPLIER mode during the design phase to guide interface design decisions, evaluate inheritance versus containment, and improve cohesion before implementation begins.

Your class design fails the cohesion check because the evaluation identifies violations of LSP, excessive parameter counts, or empty overrides, flagging them as WARNING or VIOLATION severity issues.