The book is structured so you can navigate directly to what matters for your context. Six reader profiles — select yours below and we'll tell you exactly where to begin and why.
You've heard about Claude, maybe tried it once or twice. You want to understand what it actually is and how to use it effectively — not just stumble through sessions hoping for good results.
The three foundation chapters are non-negotiable. They build the mental model that every other chapter assumes. Skipping them is the single most common mistake new users make.
Claude is already part of your workflow. But your sessions feel inconsistent — sometimes brilliant, sometimes frustrating. You sense there's more to unlock but you're not sure where the ceiling is.
The prompting chapter is where most daily users have their breakthrough. Then go directly to your professional context — the playbook chapters (13–17) are written for specific roles and assume you already know how to use the interface.
You write code. You want the real technical depth — Claude Code, the API, agentic workflows, multi-agent architectures. You don't need Chapter 2's explanation of the interface.
Chapter 19 on Claude Code is the most technically dense chapter in the book. It treats you as a peer — full installation, real command patterns, safety practices, the mental model shift required to work with an autonomous engineering agent.
You need Claude to hold itself to a higher standard of calibration, source awareness, and epistemic honesty. You're doing real knowledge work — literature reviews, synthesis, analysis — and you need to know exactly where Claude falls short.
Chapter 16 is written specifically for researchers and academics. It doesn't pretend the limitations don't exist — it maps them precisely so you can work around them.
You're responsible for how your team or organization uses AI. You need the strategic framing — what Claude can do at scale, how to deploy it responsibly, how to build workflows that compound over time.
Chapter 15 is written for your context specifically. It skips the tutorial content and goes directly to organizational deployment, team workflows, productivity measurement, and the realistic picture of what you can and can't automate.
You know what Claude is. You don't need the conceptual chapters. You want working prompt templates you can copy, paste, adapt, and use today. Appendix A is where you belong.
Appendix A contains 60+ templates organized by use case — writing, research, coding, analysis, marketing, academic, executive, and more. Every template was developed on real work and tested in live sessions.
What this capability is, how it actually works, and what the research says about it. Not hype — honest assessment.
Specific, actionable methods with the reasoning behind each one. Not "try prompting better" — the actual techniques.
Real prompts and real outputs, not reconstructed from memory. Tested in live sessions against current Claude behavior.
Copy-paste templates at the end of every chapter. Finish reading — apply it in your next session the same day.