The Claude Anatomy Library
21 anatomies. One system. Endless improvement.
Your complete blueprint for building, operating, and continuously improving AI-powered software teams with Claude Code.
New here? Jump straight to Project Structure → or browse all /posters.
What you'll learn
- Ship faster with high quality — structured AI workflows that don't cut corners
- Lower cost & higher efficiency — optimize token usage, batching, and reuse patterns
- Reduce risk & increase trust — safeguards, governance, and observability baked in
- Better onboarding & knowledge retention — new engineers productive in days, not months
- A self-improving engineering system — feedback loops that continuously refine outcomes
The Library at a Glance
Ten themes. Twenty-one anatomies. One self-improving loop.
The 21 Anatomies — Browse by Theme
Foundation — The building blocks
The structural blueprint for any AI-augmented codebase.
Reusability — Make expertise repeatable
Orchestration — Coordinate complex work
Workflows — Day-to-day execution
Management — Rhythm, quality & efficiency
People — Get your team productive
Quality — Ship with confidence
Operations — Run & improve
Trust — Govern with care
Meta — The system that makes the library better
How to use this library
- Pick your starting point — use the roadmap below. Start small.
- Read the anatomy — concepts, patterns, examples.
- Implement incrementally — adopt one pattern at a time. Ship small.
- Measure & iterate — use the loops. Improve continuously.
- Share & teach — document learnings. Help others grow.
The roadmap below is opinionated for a reason — each phase builds on the last.
Recommended Adoption Roadmap
Phase 1 — Foundation (Weeks 1–2)
Adopt anatomies 1 · 2 · 3 · 5 (and a starter 4).
Goal: a working .claude/ setup with project memory, one subagent, one MCP server.
Phase 2 — Core Workflows (Weeks 3–4)
Adopt 6 · 7 · 8 · 9 · 10 · 11 · 12. Goal: reusable skills/plugins + daily dev-loop rhythm + clean context management.
Phase 3 — Quality & Efficiency (Month 2)
Adopt 13 · 14 · 16 · 17. Goal: prompt patterns at scale, cost guardrails, PR-quality system, observability baseline.
Phase 4 — People & Operations (Months 2–3)
Adopt 15 · 18 · 19. Goal: new hires productive week 1; incidents and postmortems become learning fuel.
Phase 5 — Trust & Continuous Learning (Month 3+)
Adopt 20 · 21. Goal: regulated-team trust + the self-improving Knowledge Loop.
Three ways to start right now
I'm a solo developer
Start with CLAUDE.md and Slash Commands. Skip MCP and subagents until you feel the friction.
I'm leading a small team (2–10)
Lay down **---|
| Docusaurus 3.10.1 | Last v3.x line; future-flag ready for v4 |
| future.v4: true | All v4 breakers enabled — zero-effort migration when v4 ships |
| experimental_faster: true | SWC + Lightning CSS + Rspack → 2–5× faster rebuilds |
| Mermaid native | Every anatomy diagrams its own loop |
| GitHub Pages CI | Auto-deploy on push to main with build-cache preserved |
The README.md has the full Docusaurus 3.10.1 + GH Pages walkthrough, including the --v4 modes and Faster pipeline.
Golden Rules
- Be specific in prompts
- Keep context lean & relevant
- Automate with hooks
- Review everything
- Document as you go
- Measure & iterate
- Share & learn together
What's next
Begin with Anatomy #1 — Claude Code Project Structure →
Or skim the full poster gallery first.
Closing thought
The goal is not perfection. The goal is a system that improves every day.
The mantra: Observe → Analyze → Improve → Validate → Share → Repeat