$ cat ./playbooks/*.md

Playbooks

These are the actual processes behind the build logs, written step by step so you can run them on your own business. If a step is vague, that's a bug — tell me on X and I'll fix it.

01

My exact Claude Code setup

Claude Code is only as useful as what it can reach. This is the exact setup I run on Windows 11: one install, two CLIs, eleven connectors, and persistent memory, in the order that gets you to a working system fastest. Every connector listed here is one I actually have wired in, with what each one does for me.

⏱ An afternoon for install, auth, and connectors. Memory and the first real project take the week that follows.9 steps
02

Shipping an MVP with Claude Code

This is the exact process I used to build Career That Lasts, an AI career-planning app that is live at careerthatlasts.com. Git shows 18 commits: 17 in one overnight session and one follow-up two nights later. The short version: cut scope to demo mode, scaffold with the official generator, run a tight loop with Claude Code, deploy to Vercel immediately, and keep monetization behind a feature flag so shipping never waits on a business model.

⏱ One long overnight session for the core (first commit 2:09am, last commit that morning 7:54am), plus a follow-up evening. Call it a weekend with sleep.8 steps
03

How I audit a website with Claude (the exact process)

This is the exact process I used to audit a live WordPress lead-gen site with Claude: inventory from the sitemap, crawl every URL, build a per-page SEO table, test tracking two ways, submit a real test lead, probe security from the outside, then fix the safe stuff the same day with verification. No tool did this for me. Claude did the fetching, parsing, and verifying; I made the judgment calls.

⏱ A full day for the audit itself. The fixes that need owner decisions stretch out over the following weeks.10 steps
04

Wiring Claude into your actual business tools (MCP)

Most MCP content stops at 'look, Claude can connect to things.' This is what I actually do with it: six workflow patterns from my real setup, where Claude reads and proposes across ClickUp, Gmail, Slack, Notion, Calendar, Fireflies, and Semrush, and I stay the one who hits send. Every pattern includes the prompt shape, what the connector does under the hood, and exactly where the human checkpoint sits.

⏱ An afternoon to connect and test the basics. Give it a week of real use before you trust Claude with write operations.8 steps
05

Putting Claude on a schedule

Recurring agents that do real work while you are away from the keyboard. This playbook covers how to set up scheduled tasks in Claude Code for three patterns I use and recommend, a morning digest, a weekly SEO check, and a content-draft generator, plus the rule I use for when Make.com is the better tool. No theoretical use-case lists. Just the setup, the guardrails, and the failure modes.

⏱ An afternoon for your first scheduled agent, then under an hour for each one after that9 steps