Anatomy of the .claude/ Folder

Summary

Most teams have adopted AI in some form, but the gap between “using AI” and “getting measurable ROI from AI” is larger than people realize.Postman released a cost savings analysis that looks at six common API development workflows and benchmarks the actual time and cost difference when AI is built into the platform versus bolted on externally.It’s a short, data-driven read that helps engineering leads make the case for where AI-native tooling actually moves the needle.You can grab the guide for free here →Thanks to Postman for partnering today!Claude Code users typically treat the .claude folder like a black box. They know it exists. They’ve seen it appear in their project root. But they’ve never opened it, let alone understood what every file inside it does.That’s a missed opportunity.The .claude folder is the control center for how Claude behaves in your project.It holds your instructions, your custom commands, your permission rules, and even Claude’s memory across sessions. Once you understand what lives where and why, you can configure Claude Code to behave exactly the way your team needs it to.This newsletter walks you through the entire anatomy of the folder, from the files you’ll use daily to the ones you’ll set once and forget.Before diving in, one thing worth knowing upfront: there are actually two .claude directories, not one.The first lives inside your project, and the second lives in your home directory:The project-level folder holds team configuration. You commit it to git. Everyone on the team gets the same rules, the same custom commands, the same permission policies.The global ~/.claude/ folder holds your personal preferences and machine-local state, like session history and auto-memory.This is the most important file in the entire system. When you start a Claude Code session, the first thing it reads is CLAUDE.md. It loads it straight into the system prompt and keeps it in mind for the entire conversation.Simply put: whatever you write in CLAUDE.md,...