4 ms·
I just wish the AGENTS.md standard wasn't a single file. I have a lot of smaller context documents that aren't applicable to every task, so I like to throw them
by dgunay 1y ago
I just wish the AGENTS.md standard wasn't a single file. I have a lot of smaller context documents that aren't applicable to every task, so I like to throw them into a folder (.ai/ or .agents/) and then selectively cat them together or tell the agent to read them.
- esafak 1y agoYou can put them in subdirectories like CODEOWNERS files. https://ampcode.com/AGENT.md#multiple-agent-files https://ampcode.com/AGENT.md#multiple-agent-files
- what 1y ago>When multiple files exist, tools SHOULD merge the configurations with more specific files taking precedence over general ones. How is the tool supposed to merge multiple md files?
- esafak 1y agoThe same way it synthesizes anything else. We're talking about LLMs here; this is their bread and butter.
- yunohn 1y agoMost AI solutions make tracing the finally assembled prompt a bit difficult. However, if you look through the source code or network requests, you’ll see that merging just means naive “concatenation”.
- troupo 1y agoElixir has this idea with usage rules: https://hexdocs.pm/usage_rules/readme.html https://hexdocs.pm/usage_rules/readme.html
- dotancohen 1y agoYou could have a python script that generates the MD file on the fly, based on how you want to prompt the model. I think it's kind of funny, how deep we are getting with tools instructing tools instructing tools.