The operator's manual Anthropic doesn't ship — a protocol, an interactive network, and three drop-in templates for solo founders and small teams who feel session-to-session friction with AI assistants.
Most "how to prompt Claude" guides solve the wrong problem. The pain isn't phrasing. The pain is operating without discipline across sessions, projects, and surfaces. Read these symptoms before the pitch.
A system, not a stack. Each piece has a job — the protocol breaks if you remove one.
The protocol is a system. Reading it linearly takes about 25 minutes. Living it takes weeks. This track orders what to install when, so you build discipline before you exhaust enthusiasm.
No. Prompt phrasing is a small lever. The protocol is about operating discipline across sessions, projects, and surfaces. If you've already read Anthropic's prompt engineering docs, this is the layer they don't cover — what to do between prompts.
The protocol is generic. The surfaces (Web chat, Claude Code, Cowork, API) are Claude-specific names, but the routing principle applies to any assistant ecosystem with multiple surfaces. The journaling, audit, and cadence layers are platform-agnostic.
If you primarily use a different assistant, expect to rename the surfaces. Everything else applies.
The free preview gives you the philosophy — qualifier, reader track, and most of the 16 sections. That's enough to decide whether the discipline maps to your work.
The paid bundle gives you the implementation — the working audit ritual, worked examples, operator profiles, templates that drop into a real repo, the printable cheat sheet, and the interactive network. Paying $49 is a commitment device. People who pay run the audit. People who download free guides read once and close the tab.
Notion and Obsidian are tools for storing notes. The bundle is a set of artifacts for governing how you work with an AI assistant. Different layer.
That said: if you operate primarily out of Notion or Obsidian, the three templates and the protocol content port cleanly. You'd be giving up the interactive audit and the network visualization, which is the trade-off.
Anthropic ships features fast. Sections referencing specific surfaces (Cowork, Claude Code, API) may need updates as the products evolve. The protocol commits to a semver-versioned public changelog — re-download to get the current version. Major updates within the same year are included.
The discipline layer — journaling, audit, cadence — does not change. Those principles long-outlive any specific tooling.
Designed for individuals first. The protocol scales to small teams (2–5 people) by treating each team member as an operator and using shared CLAUDE.md plus a shared journal. For larger teams, the discipline still applies but you'll want to add team-coordination layers the protocol doesn't cover.
Personal use is one purchase per operator. If you want to roll this out to a team of more than a few, reach out about a team license — we can work something out that doesn't feel punitive.
7 days, no questions. If the protocol doesn't fit your work, the friction wasn't real to you yet — that's fine, refund and revisit later.
If three or more symptoms matched, the protocol gives you something you can install this weekend. If they didn't, save the URL for when they do.