Claude Code — The Beginner's Handbook
Most people install Claude Code, type something vague, watch it do something unexpected and quietly close the window. Nothing about that is a failure of skill — nobody explained the loop it works in, that it can be stopped mid-action, or that the most useful thing you can hand it is a way to check its own work. This handbook covers all three, and assumes no coding background and no terminal experience.
What you get
- 39-page PDF, 20 chapters, written to be read in order in one sitting
- The explore–plan–implement–verify loop, the one chapter to read if you only read one
- A route that avoids the terminal entirely, and the terminal route for anyone who wants it
- CLAUDE.md, permissions, context, rewind, skills, subagents and parallel work, each in its own chapter
- Twelve things that go wrong, with what to do about each
- Three complete sessions start to finish, a first-week checklist, a cheat sheet and a glossary
- The same book as Markdown, so you can keep it open beside your work
- Bonus: the
grill-meskill, the questioning routine used to write this handbook, ready to install
Works with
- Claude Code on macOS, Linux and Windows, and the desktop and web versions where available
- Any editor — nothing in the book depends on a particular IDE
- Checked against Anthropic's published documentation in September 2026
One licence, personal and client work, forever. No resale.
This is a handbook for someone who can describe what they want built but has never opened a terminal, and for the developer who has been using Claude Code as a faster autocomplete and suspects there is more to it. Both groups get stuck in the same place: not knowing what the tool is actually doing between the prompt and the result.
So the book is built around that gap. The first five chapters get a working session on screen — setup with no terminal, setup with one, a first session, and what to build first so the first attempt is one that can succeed. Chapter six is the spine: explore, plan, implement, verify, the four-beat loop that separates a session that lands from one that wanders. Every later chapter hangs off it.
The middle of the book is craft. How to phrase a request so the answer is checkable. What belongs in CLAUDE.md and what does not. Version control described as an undo button rather than a subject to study. Permissions, and the honest trade between speed and supervision. Context as a resource that runs out, and what to do when it does. Skills, subagents and plugins, and when each is worth the setup.
Do I need to know how to code?
No. Chapter 2 avoids the terminal entirely, and chapter 9 covers version control without asking anyone to learn Git first.
Is this the same as the Claude Chat handbook?
No — different tool, no overlap. The Chat handbook covers the product most people use in a browser. This one covers the agent that reads and changes files on your machine.
How long does it take to read?
About ninety minutes end to end. Chapters 1 to 6 take under thirty, and that is enough to start.
Reviews
Nothing here yet.
Questions & answers
No questions yet. If something about this product isn't clear, ask — we answer publicly so the next person finds it too.
