The article starts off really weak: >Claude Code users typically treat the .claude folder like a black box. They know it exists. They’ve seen it appear in their project root. But they’ve never opened it, let alone understood what every file inside it does. I know we are living in a post-engineering world now, but you can't tell me that people don't look at PRs anymore, or their own diffs, at least until/if they decid…
Anatomy of the .claude/ folder
31–40 of 312 posts
Re: Anatomy of the .claude/ folder
#32> Simply put: whatever you write in CLAUDE.md, Claude will follow. No. CLAUDE.md is just prompt text. Compaction rewrites prompt text. If it matters, enforce it in other ways.
Re: Anatomy of the .claude/ folder
#33Here's a question that I hope is not too off-topic. Do people find the nano-banana cartoon infographics to be helpful, or distracting? Personally, I'm starting to tire seeing all the little cartoon people and the faux-hand-drawn images. Wouldn't Tufte call this chartjunk?
Re: Anatomy of the .claude/ folder
#34The article starts off really weak: >Claude Code users typically treat the .claude folder like a black box. They know it exists. They’ve seen it appear in their project root. But they’ve never opened it, let alone understood what every file inside it does. I know we are living in a post-engineering world now, but you can't tell me that people don't look at PRs anymore, or their own diffs, at least until/if they decid…
You’re assuming most people using Claude code are senior engineers.
Re: Anatomy of the .claude/ folder
#35I wish all model providers would converge on a standard set of files, so I could switch easily from Claude to Codex to Cursor to Opencode depending on the situation
Issue is that both harness and specific model matters a lot in what type of instruction works best, if you were to use Anthrophic's models together with the best way to do prompting with Codex and GPT models, you'd get a lot worse results compared to if you use GPT models with Codex, prompted in the way GPTs react best to them. I don't think people realize exactly how important the specific prompts are, with the same…
Re: Anatomy of the .claude/ folder
#36The .claude folder structure reminds me of how Terraform organizes state files. Smart move putting conversation history in Json rether than some propiertary format, makes it trivial to grep through old conversations or build custom analysis tools.
Re: Anatomy of the .claude/ folder
#37Here's a question that I hope is not too off-topic. Do people find the nano-banana cartoon infographics to be helpful, or distracting? Personally, I'm starting to tire seeing all the little cartoon people and the faux-hand-drawn images. Wouldn't Tufte call this chartjunk?
Re: Anatomy of the .claude/ folder
#38So that's what "software engineering" has become nowadays ? Some cargo cult basically. Seriously all of this gives red flag. No statements here are provable. It's just like langhchain that was praised and then everyone realized it's absolute dog water. Just like MCP too. The job in 2026 is really sad.
I think I'm finding a pretty good niche for myself honestly. IMO, Software engineering is more so splitting into different professions based on the work is produces. This sort of "prompt and pray" flow really works for people, as in they can make products and money, however, I do think the people that succeed today also would've reached for no-code tools 5 years ago and seen similar success. It's just faster and more…
It shouldn’t be, but it’s going to take some catastrophic events to convince people that we have to work to make sure we understand the systems we’re building and keep everything from devolving into vibe coded slop.
Re: Anatomy of the .claude/ folder
#39I’m seeing this more and more, where people build this artificial wall you supposedly need to climb to try agentic coding. That’s not the right way to start at all. You should start with a fresh .claude, empty AGENTS.md, zero skills and MCP and learn to operate the thing first.