Software Design Philosophy

wondelai/skills/plugins/code-craftsmanship/skills/software-design-philosophy

作者 wondelaic172996495bed0fcd26896a9416b2093fd7073f0MIT2.3K 個星標收錄於 2026年10月9日更新於 2026年10月9日儲存庫4 週前更新

Manage software complexity through deep modules, information hiding, and strategic programming. Use when the user mentions "module design", "API too complex", "shallow class", "complexity budget", "strategic vs tactical", "deep module", "information leakage", "pass-through method", "this code is over-engineered", or "simplify this design". Also trigger when reviewing an interface for simplicity, evaluating whether an abstraction is pulling its weight, deciding whether a comment is worth writing, or choosing between general-purpose and special-purpose approaches. Covers deep vs shallow modules, red flags for complexity, and comments as design documentation. For code quality, see clean-code. For architecture boundaries, see clean-architecture.