The first 30 minutes.
Twelve concrete steps. Each one links to the chapter that goes deep. Tick the boxes — your progress saves locally and waits for you when you come back tomorrow.
Where projects live (folder hygiene that survives 30 days).
The first question most non-technical operators ask after installing Claude Code isn't "what does it do." It's some version of "where do I keep my projects so this isn't a mess in 30 days." Nobody covers this. Then on day 31 you have eleven half-named folders on your Desktop, three of them have a .claude/ inside, two of them are actually the same project, and you can't remember which one Claude is reading from. Decide the structure now. Five minutes here saves a Saturday in June.
Here's mine, in three lines. Code projects live at ~/Desktop/<project-or-company>/ — one folder per repo, folder name matches the GitHub repo name matches the .claude/ scope. The Obsidian vault lives at ~/Desktop/Obsidian/<vault-name>/ — separate top-level home, never inside a code repo. Nothing else lives on the Desktop. No "AI Stuff." No "experiments." No "temp." If it's a project, it gets its own folder at the right level. If it's not a project yet, it sits in your vault inbox until it earns one.
The rule is one folder, one project, one CLAUDE.md. The CLAUDE.md at the repo root is the handbook every new session reads on wake-up — see Ch 4 — the vault for the same pattern at the vault level, and the day-zero step "Drop a CLAUDE.md at your repo root" below for the file itself. Per-project context stays inside that folder. Personal context (you, your accounts, your tone) stays at ~/.claude/CLAUDE.md. They compose. They don't collide.
Two anti-patterns that bite operators about three weeks in. First: putting your Obsidian vault inside a code repo. It sounds tidy. It ruins both — git starts tracking thousands of markdown files, Obsidian sync fights with git, and Claude reads notes that belong to a different mental scope when you're trying to ship code. Second: the "AI Stuff" mega-folder. One folder, six projects, four abandoned, two active, all sharing one CLAUDE.md that contradicts itself. The agent reads context that's 70% irrelevant and you wonder why the outputs feel scrambled. Don't do this. One project per folder. Always.
If your machine is already messy: don't reorganize the world today. Pick the one or two projects you're actually working on this week, mv them into the structure above, drop a CLAUDE.md at the root of each, and leave the rest of the mess where it is. The unused folders aren't hurting you — they're just clutter. You can sweep them on a Sunday. Day zero is for the projects that matter this week.
- GitHub account2 min
If you don't have one, get one. Free. The floor of every workflow in this book lives in a repo. The rest of the day-zero setup assumes you can `git push`.
- Vercel account (linked to GitHub)3 min
Sign in with GitHub. You'll deploy your first product to Vercel by the end of the week. Free tier covers everything in this book. Netlify works too — pick one and don't argue with yourself.
- Claude Pro or Max plan2 min
Cheapest path to Claude Code + Cowork without an API budget. Pro covers the casual operator. Max if you'll burn tokens daily. You can graduate to API keys later.
- Install Claude Code5 min
One npm command, then `claude --version` to confirm. Authenticates against your Pro/Max account on first run.
- Install Cowork (desktop app)4 min
Cowork is the desktop driver for ops work — connectors to Slack, HubSpot, Stripe, your calendar. Install, connect 3 things you already pay for, ask 'what's on my plate today.'
- Install Obsidian + create your vault6 min
Local-first markdown brain. iCloud or Dropbox sync. Five folders: 00-Inbox, 01-Daily, 02-Projects, 03-People, 04-Companies. Numeric prefixes force ordering.
- Drop a CLAUDE.md at your repo root5 min
One page. Who you are, what you run, your active projects, your preferences, this week's focus. The handbook every new instance reads on wake-up.
- Run your first real prompt3 min
In Cowork: "Read CLAUDE.md and tell me what's on my plate today." In Claude Code (inside a repo): /init then ask it to summarize the codebase. If both work, the loop is live.
- Build your first skill15 min
Pick a workflow you've explained to Claude three times. Codify it. Drop the SKILL.md into ~/.claude/skills/. Test by typing the natural-language trigger phrase.
- Schedule one task10 min
The morning briefing is the highest-leverage first scheduled task. Slack DM at 7:30 AM with calendar + overnight signals + open deals. Run it for two weeks before adding a second.
- Spawn your first swarm5 min
In Claude Code: "Spawn 3 Explore subagents in parallel — one looks at X, one at Y, one at Z." Watch them work concurrently. Single-threaded work feels broken after this.
- Read the security chapter before bed8 min
Don't skip this. The 11-minute leak that cost a friend $4,200 lives in chapter 9. Set spend caps. Rotate keys. Add deny rules for Bash(rm -rf*) and Edit(.env*) tonight.
Claude FM — music for thinking and building
Operator move that doesn't fit the checklist but earns its slot — pick a soundtrack you can loop without thinking about it. Claude FM is a Vlad-curated mix for building / writing / cron-checking. Long, instrumental, low context-switch cost.