Two modes. One kit.
Claude operating templates for code and content modes.
The scaffolding solo devs end up rebuilding on every project, packaged once. Code mode rules. Content mode editorial discipline. Plus the universal patterns that hold both together.
Drop it into any project. No rebuild.
Free sample first.
The starter CLAUDE.md the kit is built around. Working file in your inbox in 30 seconds.
Why this exists
Every solo dev using Claude Code rebuilds the same scaffolding.
A CLAUDE.md from scratch. A rules folder from scratch. A ticket system from scratch.
Six weeks in, half of what you built doesn't survive a Claude update. You start over on the next project.
The kit is the alternative. Operating patterns that hold up across model releases. Not tool tutorials.
The two modes
Code mode
Layered .claude/rules/ and .claude/reference/ structure with conditional @import composition. Turns Claude Code from smart autocomplete into a junior engineer with standing instructions. For any project where Claude is writing or modifying code.
Content vault mode
Editorial discipline, framing locks, and read-before-write rules. For writing-heavy projects where Claude generates long-form content and consistency matters more than fluency.
Pipeline mode · v2
Lessons-format CLAUDE.md, verification protocols, and the tool fallback ladder. For workflows where Claude orchestrates multi-step processes. Ships with v2 at no additional cost to v1 buyers.
The universal layer
The patterns that span all modes.
- Discovery Loop Format — how Claude inventories a project before suggesting changes
- Hub Fix Prompts — five-part structure for getting Claude to fix something specific without breaking adjacent things
- Notion MCP gotcha catalog — the failure modes already hit so you don't have to
- Operating Instructions five-tier architecture — the hierarchy that keeps long projects from collapsing into chaos
These ship as a separate layer because they apply regardless of mode.
What's in the bundle
34 files. One zip. No login wall.
- Code mode pack — full
.claude/rules/+.claude/reference/structure - Content vault mode pack — editorial discipline files, framing locks, read-before-write rules
- Universal patterns layer — Discovery Loop, Hub Fix Prompts, MCP gotcha catalog, five-tier architecture
- Migration guide — how to bring an existing project onto the kit
- Quickstart README — running in under 15 minutes
- Pipeline mode pack ships with v2 (free upgrade for v1 buyers)
Who this is for
This is for
- Solo devs running Claude Code daily
- Indie hackers shipping with Claude as a co-engineer
- Agency owners standardizing how their team uses Claude
This is not for
- Anyone who hasn't used Claude Code yet — start there first
- Large engineering orgs with established AI tooling
- Anyone looking for "10 best Claude prompts" — this is operating infrastructure, not a prompt pack
About
Lucky. Solo dev.
The kit is the credential. Open the files, run them, see if they hold up. Not a course. Not a curated link list. The actual scaffolding, packaged so you stop rebuilding it.
FAQ
Is this a Claude Code tutorial?
No. It's the operating layer that sits on top of Claude Code. You should already know how to install and run Claude Code. The kit makes your usage of it stop feeling ad-hoc.
Will this become outdated as Claude evolves?
The kit is workflow methodology, not tool-specific syntax. Patterns like verification protocols and tool fallback ladders survive model updates because they're about how you operate Claude, not about Claude's current feature set.
The other reason it stays current: you customize it. Templates are starting points. Every file gets adjusted to your project's stack, your team's voice, your own preferences. The discipline holds across versions because the discipline is yours, not the tool's.
Do I need both modes?
No. Most buyers lean on one heavily and reference the other. The bundle is priced at one mode's worth — the second is upside.
How is this different from ClaudeKit / GStack / the other kits?
Mode-based organization. ClaudeKit covers code and marketing. GStack is role-based. Ron Yang's PM OS is profession-specific. This is the only kit organized around what mode you're operating Claude in, regardless of role or industry.
Refunds?
30 days. No questions, no forms. Email and it's done.
Or grab the free starter first.
Working file in your inbox in 30 seconds. No further emails unless you want them.