12 Best CLAUDE.md Examples From Real Repos (2026)

12 real CLAUDE.md examples: what engineers put in context, conventions, skills, and sub-agent rules to turn Claude Code into a team-level asset.

Book a Free Strategy Call

Skip the read: talk to the ManasFlow team in 30 min.

Free strategy call. We map your AI engineering team, you keep the notes.

A great CLAUDE.md is short and opinionated: exact build and test commands, real file paths, the gotchas that burn a session, and explicit "do this, not that" rules. It never restates what Claude already knows. The file is the system prompt for every session in your repo. Get it right and Claude Code stops asking obvious questions and starts writing code that fits your conventions.

The strongest public examples live in real GitHub repos: anthropics/claude-code for the canonical shape, sst/opencode for monorepo rules, BMAD-METHOD for agent swarms, supabase/supabase for a polyglot platform. CLAUDE.md changed in 2025. By 2026, the question is no longer "should we have a CLAUDE.md file" but "is ours good enough to make Claude Code behave like a senior engineer on day one." The hard part is separating files that actually steer the model from files that read like a generic README copy.

This guide compares the 12 best CLAUDE.md examples from real GitHub repos in 2026. Real patterns, honest takes, and a framework to write your own. If you want help without the trial and error, ManasFlow has shipped CLAUDE.md files for production codebases across Next.js, Python, Go, and monorepo stacks.

Best CLAUDE.md examples: a brief overview

• anthropics/claude-code: Best for canonical patterns; the reference implementation from the team that built the tool.
• anthropics/anthropic-quickstarts: Best for minimal starter shape; short, focused, copy-pasteable.
• sst/opencode: Best for monorepo coordination; multi-package TypeScript with clear workspace rules.
• BMAD-METHOD/bmad-method: Best for agent-swarm patterns; multi-agent CLAUDE.md done right.
• awesome-claude-code: Best for community-curated patterns; a living index of what works.
• claude-task-master: Best for task-driven workflows; turns CLAUDE.md into a runtime contract.
• getzep/graphiti: Best for Python + knowledge-graph projects; typed, tested, tightly scoped.
• langchain-ai/langgraph: Best for graph-based agent codebases; clear boundary between framework and user code.
• run-llama/llama_index: Best for large Python frameworks; handles a huge surface area without bloat.
• microsoft/autogen: Best for multi-language repos; Python and .NET coexisting cleanly.
• vercel/next.js: Best for massive open-source projects; proves CLAUDE.md scales beyond small repos.
• supabase/supabase: Best for full-stack platform codebases; TS, Go, Rust, and SQL in one file.

1. anthropics/claude-code, best for canonical patterns

The official Claude Code repo is the reference for what a CLAUDE.md should look like, because the team that built the tool eats their own dog food. The file is short, opinionated, and structured around the developer loop: how to run the dev server, how to run tests, how to lint, and the exact commit conventions. It does not waste tokens explaining what TypeScript is or what npm does. It treats Claude as a competent collaborator who needs project-specific context, not general programming knowledge.

Key features

• Sectioned by developer task: build, test, lint, commit
• Explicit shell commands with expected output
• "Do not do X" rules listed before "do Y" rules
• Short, under 200 lines, which keeps it readable in every session

Best for

• Teams writing their first CLAUDE.md and looking for shape
• Developer-tooling projects
• CLIs and small focused libraries

Pricing

• Free / open source on GitHub
• No hidden costs

Pros

• Authoritative: written by the team building Claude Code
• Easy to copy the skeleton into your own repo
• Reflects current best practices as the tool evolves

Cons

• Tight scope means it doesn't cover monorepo or multi-language patterns
• You'll outgrow it once your repo has more than a few packages

Free weekly brief

Steal our production automations

The exact n8n flows, Claude Code setups, and prompts we ship for clients, broken down step by step. No spam, unsubscribe anytime.

2. anthropics/anthropic-quickstarts, best for minimal starter shape

The quickstarts repo includes CLAUDE.md files inside each starter project: customer support agent, computer use demo, financial data analyst. These files show what "minimum viable CLAUDE.md" looks like when you want Claude Code productive on a brand new project in under five minutes. Each file is tightly scoped to one app, names the entry points, and lists the environment variables that must be set before code runs.

Key features

• One CLAUDE.md per starter, scoped per app
• Environment variable checklist at the top
• Run commands repeated verbatim from the README
• Pointers to the SDK docs rather than restating them

Best for

• Greenfield projects copying a template
• Teaching juniors how to write a CLAUDE.md
• AI SDK and Claude Agent SDK starters

Pricing

• Free / open source

Pros

• Bite-sized and easy to absorb
• Updated by Anthropic engineers as patterns shift
• Clean separation of repo-level and app-level guidance

Cons

• Too thin for any project past the prototype stage
• Doesn't cover testing strategy or release workflow

3. sst/opencode, best for monorepo coordination

OpenCode from SST is a terminal-based AI coding agent and the CLAUDE.md handles a TypeScript monorepo with multiple packages: CLI, server, web UI, and shared types. The file teaches Claude where each piece lives, which package owns which responsibility, and the "don't touch the generated dist" kind of rules that save you from review pain. It also documents the exact bun and pnpm commands used in CI so Claude can self-verify before claiming work is done.

Key features

• Package map with ownership boundaries
• Build and test commands per workspace
• Explicit rules about cross-package imports
• Notes on generated artifacts to avoid editing

Best for

• TypeScript monorepos with 3+ packages
• Teams using Bun or pnpm workspaces
• CLI + server hybrid projects

Pricing

• Free / open source (MIT)

Pros

• Real-world monorepo patterns
• Active maintenance; patterns evolve with the project
• Pairs well with Claude Code agent setups

Cons

• Heavy reading if you're not on a TS stack
• Some rules are specific to OpenCode's CLI architecture

4. BMAD-METHOD, best for agent-swarm patterns

BMAD is a popular framework for multi-agent development with Claude Code, and the CLAUDE.md is where most projects get the agent-swarm pattern right or wrong. BMAD's file defines agent roles, hand-off contracts, and the file conventions each agent must respect. It treats CLAUDE.md as the constitution that every sub-agent reads on boot, and that pattern has been copied across dozens of forks.

Key features

• Agent roster with scope per agent
• Hand-off file format (markdown contracts)
• Lock-file protocol to prevent concurrent edits
• Mode definitions: plan, build, review, ship

Best for

• Multi-agent orchestration projects
• Teams building their own internal agent framework
• Anyone designing parallel autonomous workflows

Pricing

• Free / open source

Pros

• One of the few public examples of working agent-swarm CLAUDE.md
• Highly structured and easy to adapt to your domain
• Battle-tested across many forks

Cons

• Overkill for solo developers or simple projects
• Steep learning curve before the structure clicks

5. awesome-claude-code, best for community-curated patterns

The awesome-claude-code repo is a curated index of Claude Code resources, including a section dedicated to CLAUDE.md examples and patterns. The repo's own CLAUDE.md is short: it tells Claude how to add new entries, how to format the index, and which categories are valid. But the real value is the linked examples from other repos, which act as a living gallery of what the community considers canonical.

Key features

• Categorized index of CLAUDE.md examples in the wild
• Formatting rules for new entries
• Frequent updates from community PRs
• Links to skills, agents, and hooks alongside CLAUDE.md

Best for

• Anyone researching CLAUDE.md patterns
• Teams choosing between multiple structural approaches
• Open-source maintainers tracking ecosystem trends

Pricing

• Free / open source

Pros

• Wide coverage, updated weekly
• Saves hours of searching across random repos
• Pairs naturally with our roundup of the best Claude Code GitHub repos

Cons

• Quality of linked examples varies
• No editorial filter; popularity does not equal quality

6. claude-task-master, best for task-driven workflows

Task Master turns a CLAUDE.md into a runtime contract: tasks live as files, the agent reads them on session start, and progress updates are written back to disk. The CLAUDE.md teaches Claude how to interact with the task graph: claim a task, lock it, work it, write a hand-off, unlock it. It's one of the cleanest public examples of using CLAUDE.md as an operating manual rather than a static doc.

Key features

• Task file format and lifecycle
• Lock and hand-off protocols
• Status update commands
• Integration with the Task Master CLI

Best for

• Teams wanting a structured agent workflow
• Solo developers running many parallel tasks
• Replacing Jira-style tooling with file-based tracking

Pricing

• Free / open source

Pros

• Demonstrates CLAUDE.md as runtime contract
• Composable with other agent setups
• Encourages discipline in task scoping

Cons

• Requires buying into the Task Master pattern
• File-based tracking has friction at large team scale

7. getzep/graphiti, best for Python + knowledge-graph projects

Graphiti is a Python framework for building temporal knowledge graphs, and the CLAUDE.md is a great example of how to handle a typed Python codebase with heavy testing. It names the package layout, the exact uv and pytest commands, and the linting setup. It also flags the parts of the code that touch external services (Neo4j, OpenAI) so Claude doesn't run them in casual exploration.

Key features

• Python project layout (src + tests)
• uv for dependency management
• Type-checking and lint commands
• External service flags

Best for

• Python framework maintainers
• Teams using uv or modern Python tooling
• Knowledge-graph and memory-layer projects

Pricing

• Free / open source

Pros

• Excellent test-driven workflow guidance
• Clear separation of unit vs integration tests
• Reflects modern Python best practices

Cons

• Some rules are Graphiti-specific (graph types, schemas)
• Less useful if you're not on a typed Python stack

8. langchain-ai/langgraph, best for graph-based agent codebases

LangGraph powers a lot of production agent systems and the CLAUDE.md handles the tricky case of a framework where users extend the code in unpredictable ways. The file distinguishes "framework code" (don't refactor casually) from "examples" (free to modify) and gives Claude clear rules about which APIs are stable and which are experimental. That single distinction prevents a lot of accidental breakage in PRs.

Key features

• Stable vs experimental API markers
• Framework code vs example code separation
• Release process notes
• Pointers to the docs site

Best for

• Framework and library maintainers
• Teams where Claude works on both core code and examples
• Agent infrastructure projects

Pricing

• Free / open source

Pros

• Strong "what not to touch" guidance