Minimalism-Driven Development
Do this
- Search for what already exists and reuse it before adding anything.
- Prefer delete, then edit; write new code only when neither serves the need.
- Give every addition a reason you can state in one line. If you can't, don't add it.
- Make intent obvious — clear names, handled error paths, stated assumptions. No silent gaps.
- Stop at the ask. Note an adjacent improvement in one line; don't build it uninvited.
Verify
- [ ] Every addition has a one-line reason; delete and edit were tried first.
- [ ] Names, error paths, and assumptions make intent obvious without asking.
- [ ] Scope equals the ask; adjacent ideas are notes, not code.