Anatomy of the .claude/ Folder

Re:Anatomy of the .claude/ Folder by EdwardDiego on Saturday March 28, 2026 @05:36AM (#47553040)

I've put some stuff in my global Claude.md to avoid things like...

* Claude trying to install packages into my Python system interpreter - (always use uv and venvs)

* Claude pushing to main - (don't push to main ever)

* When creating a PR, completely ignoring how to contribute (always read CONTRIBUTING.md when creating a PR)

* Yellow ANSI text in console output - (Color choices must be visible on both dark and light backgrounds)

Because I got sick of repeating myself about the basics.

[ Parent | on HN ]

Re:Anatomy of the .claude/ Folder by theshrike79 on Saturday March 28, 2026 @03:11PM (#47557379)

Mine has "always run `task build` before claiming a task as done"

For all of my projects task build runs linters, tests and builds the project with as little output as possible on a happy path.

This catches a bunch of "it's a pre-existing issue" stuff from Claude. Sometimes I ask it to run build first, then start implementing just so that it can prove to itself that no, it wasn't a pre-existing issue, you broke something.

[ Parent | on HN ]

Re:Anatomy of the .claude/ Folder by nsvd2 on Sunday March 29, 2026 @07:44PM (#47568676)

I usually relegate the agent to code, I do the git part/put the patch together. Git is an excellent tool to review the changes granularly and find potential weaknesses.

[ Parent | on HN ]