Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Anatomy of the .claude/ folder

blog.dailydoseofds.com

Post reply on HN
Print view View original

101–110 of 312 posts

Re: Anatomy of the .claude/ folder

#101

Post by matheusmoreira »

sroussey wrote: post #72
Fishkins wrote: post #52

Earlier quoted context omitted.

I agree with most of this, with one important exception: you should have some form of sandboxing in place before running any local AI agent. The easiest way to do that is with .claude/settings.json[0]. This is important no matter how experienced you are, but arguable the most important when you don't know what you're doing. 0: or if you don't want to learn about that, you can use Claude Code Web

Do people really run claude and other clis like this outside a container??

How did you contain Claude Code? Did you virtualize it? I just set up a simple firejail script for it. Not completely sure if it's enough but it's at least something.

Re: Anatomy of the .claude/ folder

#102

Post by nunez »

exitb wrote: post #17

I’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 doing things with agentic tools without worrying _as much_ about them wreaking havoc (or what they consider "havoc").

As well, as someone who's just _really_ getting started with agentic dev, spending time dumping how I work into rules helped Claude not do things I disapprove of, like not signing off commits with my GPG key.

That said, these rules will never be set in stone, at least not at first.

[^0]: https://github.com/carlosonunez/bash-dotfiles/blob/main/ai/c...

Re: Anatomy of the .claude/ folder

#104

Post by stronglikedan »

exitb wrote: post #17

I’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.

Seems maybe you're just not the target audience for this article.

Re: Anatomy of the .claude/ folder

#106

Post by ontouchstart »

ontouchstart wrote: post #99
phyzix5761 wrote: post #28

Is there a completely free coding assistant agent that doesn't require you to give a credit card to use it? I recently tried IntelliJ for Kotlin development and it wanted me to give a credit card for a 30 day trial. I just want something that scans my repo and I tell it the changes I want and it does it. If possible, it would also run the existing tests to make sure its changes don't break anything.

https://news.ycombinator.com/item?id=47533611 It is fun to use.

Just found out this and will watch myself:

https://www.youtube.com/watch?v=0RLIlNWv1xo

Re: Anatomy of the .claude/ folder

#107

Post by stefans »

matheusmoreira wrote: post #101
sroussey wrote: post #72

Earlier quoted context omitted.

Do people really run claude and other clis like this outside a container??

How did you contain Claude Code? Did you virtualize it? I just set up a simple firejail script for it. Not completely sure if it's enough but it's at least something.

I‘m using https://www.docker.com/products/docker-sandboxes/

Better isolation than running it in a container.

Re: Anatomy of the .claude/ folder

#108

Post by gck1 »

exitb wrote: post #17

I’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.

I'd also go even further and say that you likely should never install ANY skill that you didn't create yourself (i mean, guided claude to create it for you works too), or "forked" an existing one and pulled only what you need.

Everyone's workflow is different and nobody knows which workflow is the right one. If you turn your harness into a junk drawer of random skills that get auto updated, you introduce yet another layer of nondeterminism into it, and also blow up your context window.

The only skill you should probably install instead of maintaining it yourself is playwright-cli, but that's pretty much it.

Post reply on HN