The Claude Method — Principles & Patterns

Claude can produce a chapter, a module, or a section of a report in minutes. That is exactly what makes long projects dangerous.

The first few days of any book, codebase, or research project built with Claude go well. Then, somewhere around the tenth or the fortieth decision, things start to drift: a chapter contradicts one from last week, a naming convention nobody decided to change has changed anyway, a rejected design resurfaces as if it were new. Nothing crashes. There's no error message. The project just slowly stops holding together — and by the time it's obvious, the drift runs through everything already built.

Beyond Chat is not a book about prompts, and it doesn't try to explain how Claude works internally. It's a practical system for the part of the work Claude can't do for you: setting direction before you generate, keeping a project's memory alive across sessions, dividing large work without losing the whole, catching drift before it compounds, knowing when to restart instead of pushing through a session that's stopped serving you, and reviewing output at a scale no one can read twice.

Built around six core principles and worked through in three complete walkthroughs — a technical book, a software project, and a long technical document — this is a method for advanced Claude users whose work doesn't end after one message: writers, developers, researchers, and teams running projects that last weeks, not minutes.

You'll come away with a complete working system, not a list of tips — including four ready-to-use templates (Project Brief, Decision Log, Context File, and a three-phase Review Checklist) you can start using on your very next project.

Human Direction + Claude Execution + Human Judgment. That's the whole book, in one line.

You already know what to do. That's the strange part.

If you've read Beyond Chat, or learned the same lessons the hard way, you know the principles: direction before generation, context as an asset, decisions that survive, dividing without losing the whole. You can recite them. And still, mid-project, you stop — session open, cursor blinking — and think: I know the principles. What do I actually do right now?

That gap is what this book is about.

A principle is a single tool. It tells you what matters, but it has no steps — you can't run it. Real projects don't arrive shaped like single principles; they arrive shaped like walls. The session grows too large to work in. A decision from three weeks ago turns out wrong, and half the project is built on it. Four people each produced a piece, and now the pieces have to become one thing. Each wall requires several principles at once, used in a particular order.

That ordered combination is a pattern: a reusable workflow that composes two or more principles to resolve a recurring situation. This book is ten of them — each a numbered procedure you run when you hit its wall, each combining principles you already have into something none of them could do alone, and each ending with its most distinctive section: how to know the workflow is starting to fail, before the project collapses.

The ten span the life of a project: defining one you don't yet understand, producing work too big for one pass, navigating a project bigger than your context window, propagating a change after you've built on the old version, merging separate pieces into one whole, sweeping a drifted body back to one standard, reviewing an output too large to read twice, onboarding a new person into shared work, recovering a project whose reasoning was never recorded, and crossing the session boundary intact. Each ends with a one-page reference card.

This is the second book in a series. Beyond Chat gave the principles — the components. Claude Patterns gives the assemblies. It assumes you did the first book and doesn't repeat it: every chapter is a workflow, and every workflow passes three tests — it's drawable as steps, it combines two or more principles, and it could not simply be a chapter in Beyond Chat.

Principles tell you where you're trying to go. Patterns get you through the walls between here and there.