4 ms·

Is there a recommended way to construct .md files for such a system? For instance when I make them for human consumption they'd have lots of markup for readabi

Is there a recommended way to construct .md files for such a system? For instance when I make them for human consumption they'd have lots of markup for readability but that may or may not be consumable by an llm. Can you create a .md the same as for human consumption that doesn't hinder an llm?

sothatsit 1y ago
Just writing a clear document, like you would for a person, gets you 95% of the way there. There are little tweaks you can do, but they don't matter as much as just being concise and factual, and structuring the document clearly. You just don't want the documentation to get too long.
golergka 1y ago
I've had very good experience with building a very architecture-conscious folder structure and putting AGENTS.md in every folder (and, of course, instruction to read _and_ update those in the root prompt). But with Agent-written docs I also have to run doc maintainer agent pretty often.
- troupo 1y ago
  > and putting AGENTS.md in every folder (and, of course, instruction to read _and_ update those in the root prompt). For me, Claude Code completely ignores the instruction to read and follow AGENTS.md, and I have to remind it every time. The joys of non-deterministic blackboxes.
artpar 1y ago
I am using these files (most of them are llm generated based on my prompt to reduce its lookups when working on a codebase) https://gist.github.com/artpar/60a3c1edfe752450e21547898e801bb7 https://gist.github.com/artpar/60a3c1edfe752450e21547898e801... (specially the AGENT.knowledge is quite helpful)
- HumanOstrich 1y ago
  Can you provide any form of demonstration of an LLM reading these files and acting accordingly? Do you know how each item added affects its behavior? I'd also be interested in your process for creating these files, such as examples of prompts, tools, and references for your research.
  - artpar 1y ago
    claude doesn't read them reliably and has to be reminded across sessions. I ususally do @AGENT.main and @AGENT.knowledge and it figures out the rest. Over the period of doing this claude is able to maintain the "project management" part itself, as in terms of "whats the current state of the project" and "what are the next ideal todos and how to go about them". > Can you provide any form of demonstration of an LLM reading these files and acting accordingly claude does update them at the end of the session (i say wrap up on prompt). the ones you are seeing in that gist are original forms, they evolve with each commit.

sothatsit 1y ago

Just writing a clear document, like you would for a person, gets you 95% of the way there. There are little tweaks you can do, but they don't matter as much as just being concise and factual, and structuring the document clearly. You just don't want the documentation to get too long.

golergka 1y ago

I've had very good experience with building a very architecture-conscious folder structure and putting AGENTS.md in every folder (and, of course, instruction to read _and_ update those in the root prompt). But with Agent-written docs I also have to run doc maintainer agent pretty often.

troupo 1y ago
> and putting AGENTS.md in every folder (and, of course, instruction to read _and_ update those in the root prompt). For me, Claude Code completely ignores the instruction to read and follow AGENTS.md, and I have to remind it every time. The joys of non-deterministic blackboxes.

artpar 1y ago

I am using these files (most of them are llm generated based on my prompt to reduce its lookups when working on a codebase) https://gist.github.com/artpar/60a3c1edfe752450e21547898e801bb7 https://gist.github.com/artpar/60a3c1edfe752450e21547898e801... (specially the AGENT.knowledge is quite helpful)

HumanOstrich 1y ago
Can you provide any form of demonstration of an LLM reading these files and acting accordingly? Do you know how each item added affects its behavior? I'd also be interested in your process for creating these files, such as examples of prompts, tools, and references for your research.
- artpar 1y ago
  claude doesn't read them reliably and has to be reminded across sessions. I ususally do @AGENT.main and @AGENT.knowledge and it figures out the rest. Over the period of doing this claude is able to maintain the "project management" part itself, as in terms of "whats the current state of the project" and "what are the next ideal todos and how to go about them". > Can you provide any form of demonstration of an LLM reading these files and acting accordingly claude does update them at the end of the session (i say wrap up on prompt). the ones you are seeing in that gist are original forms, they evolve with each commit.