Who this is for. Who it's not.
FOR
+ Solo devs running Claude Code daily
+ Indie hackers shipping with Claude as a co-engineer
+ Agency owners standardizing how their team uses Claude across client projects
NOT FOR
– Anyone who hasn't actually used Claude Code yet — start there first
– Large engineering orgs with established AI tooling — your needs are different
– Anyone looking for "10 best Claude prompts" — this is operating infrastructure, not prompt packs
solo operator
the scaffolding solo devs rebuild on every project,
packaged once. drop it into any project. no rebuild.
Every solo dev 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. Content. One universal layer.
MODE 01
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.
MODE 02
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.
MODE 03 · SHIPS WITH V2
Pipeline mode
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.
free for v1 buyers
// THE UNIVERSAL LAYER
The patterns that span all modes.
These ship as a separate layer because they apply regardless of mode.
u1
Discovery Loop Format
How Claude inventories a project before suggesting changes.
u2
Hub Fix Prompts
Five-part structure for getting Claude to fix something specific without breaking adjacent things.
u3
Notion MCP gotcha catalog
The failure modes already hit so you don't have to.
u4
Operating Instructions five-tier architecture
The hierarchy that keeps long projects from collapsing into chaos.
// WHAT'S IN THE BUNDLE
Single download. No login wall.
unzip solo-operator-kit-v1.zip
✓ done
solo-operator-kit-v1/
├─ code-mode/ full .claude/rules/ + .claude/reference/ structure
├─ content-vault-mode/ editorial discipline + framing locks + read-before-write
├─ universal-patterns/ discovery loop · hub fix prompts · MCP gotchas · five-tier
├─ MIGRATION.md bring an existing project onto the kit
├─ README.md running in under 15 minutes
└─ pipeline-mode/ ships with v2 — free upgrade for v1 buyers
solo-operator-kit-v1.zip
Two modes.
One kit.
Every Project
Buy the kit — $99
Lucky. Solo dev.
Open the files, run them, and see if they hold up for you project. Any questions? Shoot me an email.
Questions
Is this a Claude Code tutorial?
+
Will this become outdated as Claude evolves?
+
Do I need both modes?
+
How is this different from ClaudeKit / GStack / the other kits?
+
Refunds?
+
Sent. The starter is on its way to your inbox.
Free sample first.
The starter CLAUDE.md the kit is built around. Working file in your inbox in 30 seconds.