CLAUDE.md Master Template Pack
The two-file architecture from the 1000+ sessions blog post, in 10 role variants. Global file (who the agent is) + project file (what it does) + memory, skills, errors, and lessons support layer. Install in 5 minutes.
LIBRARY
Included with the yearly Digital Thoughts pass
These are not on sale one at a time any more. They still work, they still download, and everyone who already bought one keeps it. The yearly Digital Thoughts pass opens all of them.
Monthly subscribers claim one kit per billing cycle. Bundles are yearly only.
This kit was current as of 2026-05-11.
Already bought this one? Your download link still works.
Best for
- +Claude Code users with a messy or absent CLAUDE.md who want a clean two-file structure
- +Developers who read the "1000+ sessions" blog post and want the exact files from it
- +Teams onboarding onto Claude Code and want consistent, role-appropriate defaults from day one
- +Anyone switching roles or projects who wants the agent to stop guessing about context
Not for
- -People who have never tried Claude Code: start with the free official docs first
- -Teams on Cursor, Windsurf, or other tools: these files are Claude Code-specific
What you get
Package includes
- •10 role pairs: each with a global-CLAUDE.md, project-CLAUDE.md, and role README (30 files total)
- •architecture.md: the two-file model + six surviving sections (Core Values, Capabilities Matrix, Behavioral Rules, Communication Style, Memory and Rollover, Decision Rules)
- •migration-guide.md: 3 concrete examples of moving from a single-file CLAUDE.md to the two-file architecture
- •support-files/: memory.md template (three-tier working memory), errors.json (error registry with examples), lessons.md (lessons log with examples)
- •skills-reference.md: skill framework with 3 worked examples (image-generation, web-research, deployment)
- •quick-pick.md and START-HERE.html for fast onboarding
FAQ
Can I combine role variants?
Yes. Many users start with Solo Developer for the global file and pull project-side rules from DevOps Engineer or Content Creator. See quick-pick.md for the combining patterns.
Where do the two files go?
The global file goes to ~/.claude/CLAUDE.md (it controls Claude Code across every project). The project file goes to your repo root as ./CLAUDE.md (it controls behavior in that specific repo).
How is this different from the Workshop and the Blueprint?
The Workshop teaches you how Claude Code works end-to-end. The Blueprint is a full agent stack with memory, skills, and self-improvement scripts. This pack is the focused, copy-paste version of the architecture from the blog post: 10 role-tuned variants plus the support files, ready to install in 5 minutes.
How long should each CLAUDE.md be?
Every file in the pack is under 150 lines. The blog post argues longer is not better. The agent reads CLAUDE.md every session, so precision beats volume.
You might also like:
Every past kit, included with the yearly pass