Software Design Principles

Favor small, focused, composable pieces that each do one thing well. This applies at every level -- functions, modules, APIs, systems.

See references/patterns.md for the full before/after catalog when you need a concrete refactoring model for a specific pattern (bloated config, deep inheritance, hidden side effects, etc.).

Start Minimal

Every piece of code exists to serve someone -- a caller, a user, a future maintainer. Write code that earns its place. If a function, class, or module doesn't serve a clear need, it shouldn't exist yet. Resist speculative abstractions.