Templates
CLAUDE.md Templates
Production-extracted CLAUDE.md configs for different project types. Copy it, tweak it, ship.
On this page (5 sections)
Before using these templates, complete the Interactive Guide first (at minimum steps 1-5). You need Claude Code installed and a working CLAUDE.md before templates make sense. If you haven't done that yet, start here.
Template Gallery
These aren't generic starters. I pulled them from production workspaces and refined them over months of daily use. Each one reflects real decisions made in real projects.
Available Templates
| Template | Best for | Key features |
|---|---|---|
| Next.js App | Single Next.js application | App Router patterns, server actions, testing |
| Monorepo | Turborepo / multi-package | Workspace-aware, package boundaries, shared rules |
| Python Project | Python backend / data science | Poetry/uv, pytest, type checking |
| PM Workspace | Product managers | Skills, memory, meeting workflows, product brain |
How to Use
- Pick the template closest to your project
- Copy the CLAUDE.md and supporting files
- Update the communication preferences and conventions to match yours
- Add your own skills and agents as you find yourself repeating the same workflows
Templates are starting points. The best CLAUDE.md is the one shaped by three weeks of your corrections and preferences. Start here, but expect to outgrow it.
Community Templates
Real CLAUDE.md files from real users. Submitted by the community, reviewed by us.
| Template | Author | Use case | Link |
|---|---|---|---|
| Ruby on Rails API | @railsdev | Rails 8 API-only apps with RSpec and Rubocop | View template |
| Rust CLI Tool | @ferrisbuilds | Cargo workspaces with clippy and cross-compilation | View template |
| Flutter Mobile App | @flutterfan | Flutter 3.x with Riverpod, GoRouter, and integration tests | View template |
Want to see your template here? We take community submissions via GitHub Issues.
How to Submit Your Template
- Use the template in your own project for at least a week. We want configs that have survived real use, not theoretical ones.
- Open a GitHub Issue using our Template Submission form.
- Include your CLAUDE.md (or the relevant sections), a brief description of your stack, and what specifically makes your setup effective.
- We review and add it to the gallery. We may suggest edits for clarity, but the template stays yours.
The best submissions show a specific workflow others can steal. Don't just list your stack: show the rules, the session lifecycle, the skills that make your setup actually productive.
New guides, when they ship
One email, roughly weekly. CLAUDE.md templates, workflows I actually use, and the cut-for-length stuff that does not make the public guides. One-click unsubscribe.
Or follow on Substack