5 ms·

This suggests adding a `QWEN.md` in the repo for agents instructions. Where are we with `AGENTS.md`? In a team repo it's getting ridiculous to have a duplicate

by nnx 1y ago

This suggests adding a `QWEN.md` in the repo for agents instructions. Where are we with `AGENTS.md`? In a team repo it's getting ridiculous to have a duplicate markdown file for every agent out there.

singhrac 1y ago
I just symlink to AGENTS.md, the instructions are all the same (and gitignore the model-specific version).
drewbitt 1y ago
CLAUDE.md MISTRAL.md GEMINI.md QWEN.md GROK.md .cursorrules .windsurfrules .copilot-instructions Saw a repo recently with probably 80% of those
- falcor84 1y ago
  It would be funny to write conflicting instructions on these, and then unleash different coding agents on the same repo in parallel, and see which one of them first identifies the interference from the others and rewrites their instructions to align with its own.
  - yard2010 1y ago
    Lol you can even tell each model to maliciously and secretly sabotage other agents and see which one wins.
  - yencabulator 1y ago
    Core War NG! https://en.wikipedia.org/wiki/Core_War https://en.wikipedia.org/wiki/Core_War
sunaookami 1y ago
I just make a file ".llmrules" and symlink these files to it. It clutters the repo root, yes...
mattigames 1y ago
Maybe there could be an agent that is in charge of this and it's trained to automatically create a file for any new agent, it could even temporarily delete local copies of MD files that no agents are using at the moment to free the visual clutter when navigating the repo.
- theshrike79 1y ago
  I tried making an MCP with the common shit I need to tell the agents, but it didn't pan out. Now I have a git repo I add as a submodule and tell each tool to read through and create their own WHATEVER.md
oblio 1y ago
Can't these hyper-advanced-super-duper tools discover what UNIX tools since circa 1970 knew, and just have a flag/configuration setting pointing them to the config file location? Excuse me if they already do :-) In which case you'd have 1 markdown file and at least for the ones that are invoked via the CLI, just set up a Makefile entry point that leads them to the correct location.
czottmann 1y ago
I built https://github.com/czottmann/render-claude-context https://github.com/czottmann/render-claude-context for that exact reason. > This node.js CLI tool processes CLAUDE.md files with hierarchical collection and recursive @-import resolution. Walks directory tree from current to ~/.claude/, collecting all CLAUDE.md files and processing them with file import resolution. Saves processed context files with resolved imports next to the original CLAUDE.md files or in a specific location (configurable). I mostly use Claude Code, but every now and then go with Gemini, and having to maintain two sets of (hierarchical) instructions was annoying. And then opencode showed up, which meant yet another tool I wanted to try out and …well.
redhale 1y ago
https://github.com/intellectronica/ruler https://github.com/intellectronica/ruler Library to help with this. Not great that a library is necessary, but useful until this converges to a standard (if it ever does).
apwell23 1y ago
these files are for free publicity on github

by nnx 1y ago

singhrac 1y ago

I just symlink to AGENTS.md, the instructions are all the same (and gitignore the model-specific version).

drewbitt 1y ago

CLAUDE.md MISTRAL.md GEMINI.md QWEN.md GROK.md .cursorrules .windsurfrules .copilot-instructions Saw a repo recently with probably 80% of those

falcor84 1y ago
It would be funny to write conflicting instructions on these, and then unleash different coding agents on the same repo in parallel, and see which one of them first identifies the interference from the others and rewrites their instructions to align with its own.
- yard2010 1y ago
  Lol you can even tell each model to maliciously and secretly sabotage other agents and see which one wins.
- yencabulator 1y ago
  Core War NG! https://en.wikipedia.org/wiki/Core_War https://en.wikipedia.org/wiki/Core_War

sunaookami 1y ago

I just make a file ".llmrules" and symlink these files to it. It clutters the repo root, yes...

mattigames 1y ago

Maybe there could be an agent that is in charge of this and it's trained to automatically create a file for any new agent, it could even temporarily delete local copies of MD files that no agents are using at the moment to free the visual clutter when navigating the repo.

theshrike79 1y ago
I tried making an MCP with the common shit I need to tell the agents, but it didn't pan out. Now I have a git repo I add as a submodule and tell each tool to read through and create their own WHATEVER.md

oblio 1y ago

Can't these hyper-advanced-super-duper tools discover what UNIX tools since circa 1970 knew, and just have a flag/configuration setting pointing them to the config file location? Excuse me if they already do :-) In which case you'd have 1 markdown file and at least for the ones that are invoked via the CLI, just set up a Makefile entry point that leads them to the correct location.

czottmann 1y ago

I built https://github.com/czottmann/render-claude-context https://github.com/czottmann/render-claude-context for that exact reason. > This node.js CLI tool processes CLAUDE.md files with hierarchical collection and recursive @-import resolution. Walks directory tree from current to ~/.claude/, collecting all CLAUDE.md files and processing them with file import resolution. Saves processed context files with resolved imports next to the original CLAUDE.md files or in a specific location (configurable). I mostly use Claude Code, but every now and then go with Gemini, and having to maintain two sets of (hierarchical) instructions was annoying. And then opencode showed up, which meant yet another tool I wanted to try out and …well.

redhale 1y ago

https://github.com/intellectronica/ruler https://github.com/intellectronica/ruler Library to help with this. Not great that a library is necessary, but useful until this converges to a standard (if it ever does).

apwell23 1y ago

these files are for free publicity on github