Sources and leaks from Amazon, Adobe, Atlassian, Citi, and more show what is really happening with AI right now: companies are trying to rein in AI use as costs spiral out of control.
My CLAUDE.md file bloated significantly. It tried to load unnecessary skills and would retain throughout the whole session. Fixing that, maintaining good wikis and using clear often really helped fixed my personal token burn.
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.
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
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.
My CLAUDE.md file bloated significantly. It tried to load unnecessary skills and would retain throughout the whole session. Fixing that, maintaining good wikis and using clear often really helped fixed my personal token burn.
What do you use that file for? I see Claude.md thrown around and I’m a bit curious.
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
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.