References: CLAUDE.md at team scale
Source material
Section titled “Source material”Every Claude Code behavior this lesson describes is documented on the official pages below. The short quoted phrases in the lesson are verbatim from these pages; everything else is Clawdemy’s synthesis and examples.
- How Claude remembers your project, Claude Code documentation, Anthropic. The lesson’s primary source: the full memory hierarchy (managed, user, project, local, subdirectory), the concatenation behavior of loaded files, the import syntax and its four-hop limit, the under-200-lines size guidance, the rules directory with paths frontmatter and glob scoping, and the memory command for listing loaded files. Also the source of the lesson’s request-versus-guarantee framing: memory is described as context, not enforced configuration.
- Claude Code settings, Claude Code documentation, Anthropic. The enforcement half of the configuration layer: user, project, local, and managed settings files, and the precedence order between them.
- Extend Claude with skills, Claude Code documentation, Anthropic. Custom slash commands and their merger into skills, project versus personal locations, the arguments placeholder, and precedence when names collide.
- Common workflows, Claude Code documentation, Anthropic. The plan mode section: what plan mode does, the mid-session keyboard toggle, and the launch flag.
Going deeper
Section titled “Going deeper”- Claude Code in Action, in the Anthropic Academy catalog. Free, self-paced official course on integrating Claude Code into a development workflow, a good hands-on companion to this lesson’s configuration reading.
- Claude Code documentation, Anthropic. The canonical reference this track returns to; the hooks and permissions pages are the natural next stop after this lesson’s request-versus-guarantee split.
On this site
Section titled “On this site”- Thinking like an architect (this track, lesson 1). The three trade-offs this lesson executes in files: decide versus enforce, one versus many, carry versus fetch.
- Building with Claude (Track 22). The API-level foundations underneath the tool this lesson configures.
Adjacent topics
Section titled “Adjacent topics”- The next lesson in this track moves from configuring the environment to shaping the model’s answers: structured output and schemas.
- If the request-versus-guarantee split interested you most, the hooks and permissions pages of the Claude Code documentation are the deep dive: they are where “never” becomes enforceable.