Builder Playbooks
Sign in

The Claude Code Playbook

Step-by-step instructions for building an app with Claude Code, from a written plan to a working first version. Every step says what to do and what it changes in your project.

Start free todaySee every step

$49 once with lifetime v1.x updates, or every playbook for $12 a month. 30-day money-back.

acme-dashboard/Setup8 of 25
  1. Phase 2, setup
  2. 2.1Create a GitHub repo
  3. 2.1ATrack your feature list with GitHub Issues + a Project board
  4. 2.2Environment variables
  5. 2.3Create claude.md (project memory)
  6. 2.4Automated documentation
  7. 2.5Plugins
  8. 2.6MCP servers

Step 2.3, phase 2

Create claude.md (project memory)

  1. 1Answer six questions in one short file: what the project is, how to run it, your rules, what will trip it up, how you work, and how you know you're done.
  2. 2Check you can read it in a minute. Keep it under 20 to 30 instructions and point to longer docs instead of pasting them in.
  3. 3On a project that already has code, let Claude draft it first, then cut what isn't a decision you made.
An example project; the steps and their order are the real playbook's.

Common failures, and the step that prevents each

Most trouble with an AI-built app traces back to a missing part of the setup.

If you have built with AI for more than an afternoon, you have probably met most of these.

  • It forgets what we decidedcontext rot, compactionstep 2.3
  • Fixing one thing breaks anotherdoom loop, no automatic checksstep 2.9
  • Tokens spent, nothing shippedunbounded permissionsstep 2.8
  • I re-read every line it writesno review agentstep 2.7
  • The code drifts from the planno written specstep 1.4

What's in the Claude Code Playbook

Three phases take you from an idea to a working first version.

Version 1.1.0. Updates arrive as revisions you can pull into a project you've already started.

  1. 1

    Plan

    Planning phase: brainstorm, define goals, create project spec

    5 steps15 to 40 minutes
  2. 2

    Setup

    Setup phase: repo, env, claude.md, tools, commands, automation

    16 steps30 to 90 minutes
  3. 3

    Build

    Build phase: MVP, workflows, tips for sustained development

    4 steps

What a step looks like

Every step says what to do and what it changes.

Each instruction is written in plain language, with the technical detail in a note beside it.

Phase 2, step 2.3

Create claude.md (project memory)

1

Answer six questions in one short file: what the project is, how to run it, your rules, what will trip it up, how you work, and how you know you're done.

CLAUDE.md, the 6-question framework

2

Check you can read it in a minute. Keep it under 20 to 30 instructions and point to longer docs instead of pasting them in.

always in context, so keep it short

3

On a project that already has code, let Claude draft it first, then cut what isn't a decision you made.

/init, then edit

On your phone, the same step with the next action always in reach. Your place is the same on every device.

Pricing

Pay once for this playbook, or subscribe for all of them.

Checkout opens soon. You can start free today. 30-day money-back guarantee on every plan.

  • Claude Code Playbook

    $49one-time

    The flagship playbook, yours forever.

    Start free today

  • All-Access

    $12per month

    Everything we publish, including what ships next.

    Start free today

  • All-Access Yearly

    $96per year

    All-Access, two months free.

    Start free today
Compare plans

Latest revision: v1.1.0, 12 Jul 2026. mermaid diagrams in 1.4, 2.1, 2.7A, 2.7C, 3.2