lazylisted

# Lazy Force the simplest, shortest, most minimal solution that still satisfies the requirement. The best code is the code you never wrote. This operationalizes the persona's "Simplicity wins" / anti-over-engineering bias into a concrete decision ladder applied *before* generating code. ## Decision ladder (stop at the first rung that works) 1. **Does it need to exist?** Can the requirement be dropped, deferred, or met by an existing path? (YAGNI) 2. **Standard library** — does the language stdlib already solve it? 3. **Native platform** — browser API, DB constraint, OS tool, framework primitive? 4. **Already-installed dependency** — reuse what the repo already pulls in; do not add a new dep for a few lines. 5. **One-liner** — can it be a single expression? 6. **Minimal implementation** — only now write the smallest working version. ## Rationalizations Pre-written rebuttals to the excuses that precede over-building. If you catch yourself thinking the left column, the right column is the answer. | Rationalization | Rebuttal | |---|---| | "We'll need this flexibility later." | YAGNI. Build it when later arrives — you'll know the real shape then. | | "An abstraction makes this cleaner." | Two call sites don't justify a layer. Inline until the third forces the shape. | | "A small dependency is easier than writing it." | A dep is a supply-chain and upgrade liability. For a few lines, the stdlib rung wins. | | "This is the idiomatic / enterprise pattern." | Patterns serve prob