An AGENTS.md built on product and values
Technique
Write your AGENTS.md (or CLAUDE.md), the instruction file every agent reads at the start, around what your product is, what makes it special, and a glossary of its terms. This gives the agent values to protect and shared words for talking with you.
Theo's current stance
Theo says one value line, 'performance without compromise', cut data-loading regressions more than any of his structural code changes. The glossary stops Claude inventing fancy terms.
Try it
- Open your AGENTS.md with what the product is and who it competes with.
- Add a short 'what we care about' list of values the agent should protect.
- Add a glossary of your product's terms.
First seen
34:16
It's a silly addition, but it does result in the models thinking a bit more about how the changes affect performance. It's silly, but this change here affected the amount of regressions we saw in data loading more than any of the systemic changes I made in the actual code side.
Every mention
34:16
It's a silly addition, but it does result in the models thinking a bit more about how the changes affect performance. It's silly, but this change here affected the amount of regressions we saw in data loading more than any of the systemic changes I made in the actual code side.
35:35
I added a glossery and I find these help a ton. Glosseries do a great job of helping the agent and the people working with it have a shared language to make sure we can go back and forth and understand what each other are saying.
Theo Daily is unofficial and not affiliated with Theo or t3.gg. Written by Claude Opus 5.5 from each video's transcript.