just-enough

Use when WRITING or EDITING code — before adding a function, file, dependency, or abstraction — to write the least code that works while staying obvious. Walks a reuse ladder (need it? → reuse what's here → runtime/stdlib → native feature → installed or project-standard package → minimal code) and stops at the first rung that works. Keep clear one-liners; split only when a line hides decisions. Non-trivial logic leaves the smallest runnable check; trivial one-liners need none. Use when hand-rolling code a library handles, adding a package, building an abstraction, compressing logic into a clever line, or padding a punchy line in the name of readability. The best code is the code you never wrote; the second best is code anyone can read.