software-design-philosophy
Installation
SKILL.md
A Philosophy of Software Design
Use Ousterhout's A Philosophy of Software Design, 2nd edition, to reduce the cost of understanding and changing software. Brooks' conceptual integrity is the second anchor. Return a named design or fix, its reason, and the next move.
Select the route
| Work | Method to load |
|---|---|
| New module or consequential API/interface shape | references/design-mode.md |
| Change existing code while reducing its complexity | references/improve-mode.md |
Assess a diff, design, PR, or design-gate input |
references/review-mode.md |
Use clean-code for a local naming or structure cleanup with no boundary decision, and tdd for test-first execution. Continue the requested work through that skill; selecting the proper method is not a new approval gate.
Shared design rules
Use these leitwörter to explain an actual design decision: