2 ms·
I have a legacy codebase of around 300k lines spread across 1.5k files, and have had amazing success with the agents.md file. It just prevents hallucinations a
by CrzyLngPwd 8mo ago
I have a legacy codebase of around 300k lines spread across 1.5k files, and have had amazing success with the agents.md file.
It just prevents hallucinations and coerces the AI to use existing files and APIs instead of inventing them. It also has gold-standard tests and APIs as examples.
Before the agents file, it was just chaos of hallucinations and having to correct it all the time with the same things.
- OutOfHere 8mo agoYou might have better luck with more focused task-specific instructions if you can be bothered to write them.
- CrzyLngPwd 8mo agoI do write them, but without the agents file, I would end up pasting the same contents each time I start work on something, which seems like a waste of time.
- OutOfHere 8mo agoWhat that tells me is that you don't narrow the focus of the LLM to the task at hand. Instead of giving it a hundred pages of information for every task, if you give it a single page that is both relevant and required, your result could be tighter.
- derefr 8mo agoNo? What you’re looking for here are project-specific agent skill files. Which don’t need to be “pointed at” by AGENTS.md for the agent to find them and use them when/where applicable; and nor do they take up undue context when not in use. (I believe internally the agentive coding frameworks RAG on skills and then search this RAG for applicable skills to pull temporarily into context at the beginning of each planning step.)