software-design-complexity

What problem does it solve?

Software systems suffer from escalating complexity due to deep vs shallow modules, information leakage, and inconsistent architecture decisions. This Skill provides a practical framework to assess, discuss, and reduce complexity by emphasizing depth, information hiding, and strategic design choices.

Core Features & Use Cases

• Deep vs shallow module evaluation
• Information hiding and leakage detection
• Strategy-based vs tactical programming guidance
• Use-case oriented design audits and refactoring prompts
• Guidance for creating meaningful interface comments and documentation Example: When reviewing a module boundary, apply the depth ratio to decide whether to merge or split the module.

Quick Start

Perform an architectural review to identify depth, leakage, and refactoring opportunities, then apply the guidance to consolidate responsibilities.