Two developers on the same team. Same project, same codebase, same Claude Code subscription. Dev A types a prompt and Claude asks permission for every file read, every git command, every test run. Every session starts from zero — no memory of conventions, no formatting standards, no safety rails.
Dev B types the same prompt. Claude reads files freely, formats code automatically after every edit, remembers that the team uses kebab-case for API routes, and refuses to touch .env files. No permission dialogs. No re-explaining conventions.
The difference? Dev B spent 10 minutes setting up a .claude/ directory. Dev A is fighting the tool instead of using it.
Today you learn what lives inside .claude/ — the configuration layer that turns Claude from a generic AI into your team's specialized assistant.