You certainly can do this for code, and it’ll give you great answers. But I find that, for whatever reason, info that I consume this way has a much shorter TTL in my brain than something I wrote myself.

I’ve been experimenting with writing a living spec — API endpoints, schemas, how things work at a low enough level that the LLM can fill in the details - and that’s been working well.

It also forces me to do the hammock-driven development necessary to build the right thing, and as a byproduct it keeps the design in my head longer.

I think over time our memory is worse than we think it is and writing things down is good for your own function as well as human groups you work with and AI. Like I do not care a lot for the AGENTS.md but if there is a certain kind of task like “write a test which mocks things in a certain way” or “implement a DAO object” it is very much worth picking one as a case study and adding a lot of inline comments that explain theory or reasoning or the steps involved in doing something and when you want it to write something say “take a look at A as an example, but I know there will be these differences…” and the same is good for you siz months later or another team member.

Doing sports ohotography I might got to a certain indoor track meet once a year and there is a lot to know about the order of events and how to move around in the space and where the good backgrounds are that I will have to rediscover unless I write a “runbook” which again lets me share that knowledge.

A coven has a “book of shadows” and for me it is mostly a runbook, like there are a lot of ways you can cast a circle and I like some liturgy better than others so if you get consensus on things you can write it down, even the Greeks thought writing things down impaired your ability to remember things but it’s easier to stay consistent and you do memorize it over time though…. It is annoying that a lot of people are reading off their phones in ritual spaces.