Shameless plug, if you ever need to parse ~/.claude/projects use claude-code-types [1].
Anatomy of the .claude/ folder
151–160 of 312 posts
Re: Anatomy of the .claude/ folder
#152Feel little like this is generated and not based on experience. Claude.md should be short. Typescript strict mode isnt a gotcha, itll figure that out on its own easily, imo omit things like that. People put far too much stuff in claude, just a few lines and links to docs is all it needs. You can also @Agents.md and put everything there instead. Dont skills supercede commands? Subagents are good esp if you specify mod…
The intro paragraph sounds exactly like Claude’s phrasing. So much so that I couldn’t read the rest of the article because I assumed I could just ask Claude about the topic.
Re: Anatomy of the .claude/ folder
#153Building your AI agent "toolkit" is becoming the equivalent of the perfect "productivity" setup where you spend your time reading blog posts, watching YouTube videos telling you how to be productive and creating habits and rituals...only to be overtaken by a person with a simple paper list of tasks that they work through. Plain Claude, ask it to write a plan, review plan, then tell it to execute still works the best…
Re: Anatomy of the .claude/ folder
#154I’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.
> empty AGENTS.md, zero skills
which is basically every setup because claude sucks at calling skills and forget everything in claude.md with a few seconds.
Re: Anatomy of the .claude/ folder
#155I’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.
This matters for big engineering teams who want to put _some_ kind of guardrails around Claude that they can scale out. For example, I have a rule [^0] that instructs Claude to never start work until some pre-conditions are met. This works well, as it always seems to check these conditions before doing anything, every turn. I can see security teams wanting to use this approach to feel more comfortable about devs doin…
NO EXCEPTIONS!!!!!!!!!!!!!!!!!!!!!!!!
cute that you think cluade gives a rat ass about this.
Re: Anatomy of the .claude/ folder
#156are agents/ still relevant after we got skills? I am genuinely confused on why I would need custom system prompts for specific agents, what should I use them for?
Re: Anatomy of the .claude/ folder
#157Earlier quoted context omitted.
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…
Are there any good guides on how to write prompt files tailored to different agents? Would also be interested in examples of a CLAUDE.md file that works well in Claude, but works poorly with Codex.
Why would you settle for a guide when you can get a claude skill to do it for you?
Re: Anatomy of the .claude/ folder
#158I’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.
Seriously, just use plan mode first and you get like 90% of the way there, with CC launching subagents that will generally do the right thing anyway. IMHO most of this “customize your config to be more productive” stuff will go away within a year, obsoleted by improved models and harnesses. Just like how all the lessons for how to use LLMs in code from 1-2 years ago are already long forgotten.
I loved all the dumb prompt “hacks” back then like “try saying please”
Re: Anatomy of the .claude/ folder
#159Completely tangential, but can we please stop putting one million files at the root of the project which have nothing to do with the project? Can we land on a convention like, idk, a `.meta` folder (not the meta company, the actual word), or whatever, in which all of these Claude.md, .swift-version, Code-of-Conduct.md, Codeowners, Contributing.md, .rubocop.yml, .editorconfig, etc. files would go??
I was glad when linux went with the .config standard for most dotfiles.
Now if only it would be respected more often!
Re: Anatomy of the .claude/ folder
#160I’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.
2 months ago I built (with Claude) a quite advanced Python CLI script and Claude Skill that searches and filters the Claude logs to access information from other sessions or from the same session before context compaction. But today Claude Code has a builtin feature to search its logs and will readily do it when needed.
My point is, these custom things are often short lived band-aids, and may not be needed with better default harnesses or smarter future models.