[dead]
Anatomy of the .claude/ folder
231–240 of 312 posts
Re: Anatomy of the .claude/ folder
#232Earlier quoted context omitted.
> I'd also go even further and say that you likely should never install ANY skill that you didn't create yourself Ignore original comment below, as the post is technical so is the parent comment: for techies --- That applies to tech users only. Non-tech users starting to use Claude code and won't care to get the job done Claude introduced skills is to bring more non-tech users to CLI as a good way to get your feet we…
what? non techies are most at risk. There are a huge number of malicious skills. Not knowing or caring how to spot malicious behavior doesn’t mean someone shouldn’t be concerned about it, no matter how much they can’t or don’t want to do it. I am an adminstrator of this stuff at my company and it’s an absolute effing nightmare devising policies that protect people from themselves. If I heard this come out of someone’…
[flagged]
Re: Anatomy of the .claude/ folder
#233I look forward to the death of this hype machine.
Re: Anatomy of the .claude/ folder
#234Earlier quoted context omitted.
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…
I'm also thinking on how we can put guardrails on Claude - but more around context changes. For example, if you go and change AGENTS.md, that affects every dev in the repo. How do we make sure that the change they made is actually beneficial? and thinking further, how do we check that it works on every tool/model used by devs in the repo? does the change stay stable over time?
Given the scope that AGENTS has, I would use PRs to test those changes and discuss them like any other large-impact area of the codebase (like configs).
If you wanted to be more “corporate” about it, then assuming that devs are using some enterprise wrapper around Claude or whatever, I would bake an instruction into the system prompt that ensures that AGENTS is only read from the main branch to force this convention.
This is harder to guarantee since these tools are non-deterministic.
Re: Anatomy of the .claude/ folder
#235Earlier quoted context omitted.
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.
Claude won’t do me wrong; that’s what the exclamation marks are for!
Re: Anatomy of the .claude/ folder
#236[flagged]
Re: Anatomy of the .claude/ folder
#237I’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.
.claude has become the new dotfiles. And what do people do when they want to start using dotfiles ? they copy other’s dotfiles and same is happening here :)
.claude is likely to contain secrets and also contains garbage like cache etc, if it is shared, it should only be partially shared.
Re: Anatomy of the .claude/ folder
#238I’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.
Yep, it regularily ignores CLAUDE.md files. It seems these files are not weighted high enough vs. the prompt.
Re: Anatomy of the .claude/ folder
#239Building 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…
Reminds me of the days spent optimizing Jira
Re: Anatomy of the .claude/ folder
#240[flagged]