this post was submitted on 03 Jul 2026
427 points (99.3% liked)
Technology
86074 readers
2965 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
What do you use that file for? I see Claude.md thrown around and I'm a bit curious.
When you use the /init command in claude code, it'll scan your whole project and write a CLAUDE.md, which is basically an overview of the project contents and architecture that it uses as context when responding to queries.
Consider each session with Claude a new employee. Your Claude.md file is what it knows and how it acts out the gate. You can save memory to it or save directory links so it knows where or how to look for something.
LLMs generally work in one way. They get the prompt and give an answer. CLAUDE.md, system promp, rules, memory, tool defintions, mcps are different ways to prefix your prompt with extra information or context.
Skills, or plugins, are a way to inject less information until is needed (you can think about them as prefixing your prompt with "if you are asked about pizzas, add to context separate file pizza.md").
What you could add to CLAUDE.md depends on what you're doing. Generally it should be context LLM cannot infer relevant to all/most task performed in given project.
It's added in every chat you start with Claude for that project. It's useful for including context specific to your project that it couldn't otherwise know. High level stuff like what it's for, but also details about how the folders are organized. This saves time and tokens from rescanning the whole thing every time.
Oh, thanks! That's kind of neat, like not having to type "I'm on godot 4, c#" every time you ask about some quirk.
That's exactly what it's perfect for. If you go further and detail the intent of the project and give a high level overview of the architecture, it's even better at inferring what needs to be done without a bunch of expensive file reads and asking you repetitive questions