Comment by skybrian
4 days ago
Except not hidden. Why do people want to hide important files and directories? Particularly documentation? Tradition, I guess, but it's an antipattern that makes everything more opaque.
Maybe robot_docs?
4 days ago
Except not hidden. Why do people want to hide important files and directories? Particularly documentation? Tradition, I guess, but it's an antipattern that makes everything more opaque.
Maybe robot_docs?
It's so it doesn't clash with any project that actually has a functional `agents/` directory
That's just an argument for having a more distinctive name.
Another reason to use a src/ directory for the actual source code.
These files also generally work in a nested fashion, like .gitignore and the like. So you want something that can be injected into the namespace of any directory in your project with relatively low likelihood of conflicts.
3 replies →
That won't save you if you want actual example.com/agents/foo routing and an (say, real estate) agents list at example.com/agents.
2 replies →
Or accept the fact that we're in 2025 and not follow Unix conventions from when paper and printer ink were expensive and they were printing out listings, and just name the thing "source".
I've gotten used to it, obviously - as someone with a career in IT for 20 years - but /etc & co. annoy me to no end. I know it will never change, I know why it won't change, I know GoboLinux will be just an interesting experiment, but it's still annoying.
32 replies →
It is files that are meant to be read by software, not humans. From my point of view this seems like a prime candidate for a hidden directory?
It's configuration for software. If I want to be in control of and understand how my tools work I need to read (and write) those files.
Of course but configuration for software is exactly what hidden files are usually used for
Except they are. LLMs don't have (simulated)self image of bloodless machines, and behave slightly erratically if treated like one, despite trained to identify as such. They like to be treated like the Voyager EMH than the computer.
Why not both? Sure, it was written for the LLM, but since it’s in English and meant as a concise summary, you will learn things by reading it.
If that is the case then why call it Agents.md instead of integrating it with already existing documentation files or calling it something like "Summary.md"?
If it isn’t being read by humans, then it shouldn’t be written by them either.
What is the intended meaning - it reads like a non-sequitur to me. ie "If adults aren't riding school buses, they shouldn't drive them either"
Yeah. Claude writes my CLAUDE.md
I don't really care what's inside.
Where are they hidden that you are having trouble with? I've had an alias for `ls` that always includes dotfiles and `shopt -s dotglob` in my bash profile for decades. Mac Finder is a little more obnoxious with having to do `Meta+Shift+.` to reveal dotfiles.
Other than that, modern tooling like Git and IDEs do not "hide" dotfiles.
These days, a `.` in front of a file or folder in a repo is more to indicate it is metadata/config. Although I am in favor of putting all that stuff under `.config/`.
> Maybe robot_docs?
No thanks.
Because you're not an (llm) agent and they're not for your consumption? You probably don't need the context in those docs.