---
Parse, Don’t Validate
I only just ran across this - along with this article ‘the bloat of edge-case first libraries’, which both tackle a similar problem: littering your code with validation everywhere. These are the kind of articles that really help me to articulate the kind of code I’m looking for in my LLM instructions. Similar to the kind of great advice found in John Ousterhout’s book.
I like to keep these instructions in a docs directory next to commands and
agents, then pull in docs to the specific agents that next them. (For
instance, having docs/software-design.md in the planning agent.) You can also
just include them in the relevant projects.