[SeriousM]

Yes. In my case (and I guess everyones usecase is subjective) my system prompt states to read the AGENT.md file when possible.

On a new project I usually set up the context of the model (language to use, reason of the product/prototype, etc.) and then I tell the LLM to write a AGENT.md, STATE.md and ROADMAP.md. I don't tell the LLM what's in there because the model has it's own directive and flavor what should be in these files. The models already know the purpose of these files by themself! On a new session, I let the agent read the markdown files in order to continue with the work. Before a session ends, I let the LLM update the markdown files. Maybe one word of caution: don't switch models - it's like putting another person on a working station and ask them to continue the work of others.

Easy setup, really good outcome!

[lousclues]

I do something similar. I don’t necessarily call it AGENT or STATE and every project has its own files. I have architecture documents that accompany change log descriptions that load technical knowledge that the agent can readily use.

I find it also necessary to have a principles document outlining the particular problems that the software is supposed to solve and guard rails to not cross. I call it promise driven development.