software-design-philosophy
Installation
SKILL.md
Software Design Philosophy
Reduce the cost of understanding and changing a module, following Ousterhout's A Philosophy of Software Design with Brooks' conceptual integrity as the second anchor. Return a named design or fix, its reason, and the next move.
Use clean-code for local naming or structure with no boundary decision, architecture-lens for system style and service boundaries, tdd for test-first execution, and the Connascence Pass in simplify-changes for coupling inside a diff.
Leitwörter
Use these by name to explain an actual decision:
- strategic versus tactical: invest a little design now so the next change is cheaper. A tactical special case is how systems rot.
- deep module: a simple interface hiding a lot. A shallow module costs about as much to learn as to inline.
- information leakage: one design decision reflected in two or more modules. That is a change ownership failure; give the decision one owner.
- design it twice: for a consequential unresolved interface, compare two or three meaningfully different shapes before coding. Reuse a settled interface unless new evidence challenges it.
- stay strategic: when modifying code, don't tack on a special case that makes the design worse. Fit the change, or improve the design, or say why you won't.
- decide what matters: name the few invariants, error behaviors, and compatibility needs the situation depends on, give that knowledge one owner, emphasize it, hide the rest.
- reader, not writer: complexity is judged by the next person to change the code. If a caller needs a fact absent from the interface, that is leakage or obscurity.
- smallest coherent shape: one model, no larger than the problem.