Throughliner is a structured method for driving Claude through a real build. Most people find it while trying to make an app or some software with AI, and hitting the walls that come with it. It's the throughline from vibe coding to something you can actually ship.
AI tools promise anyone can build software now. Then you try, and you discover nobody told you what to do when…
Some of these the tooling already helps with, and where it does, that's said above rather than claimed as Throughliner's. Two of them are skills no tool settles. What the method adds is the rest.
Throughliner is a Claude Code plugin built around one thing: the reasoning travels with the work. Every piece of work carries why it's wanted — written as prose, in your words, approved by you — so a session starting fresh tomorrow builds what you meant instead of inferring it from the code. That thread of why is the throughline, and it's what the method is named for.
Around that it puts a structured way of working: the build breaks into small, explicit steps, and each one is planned, built and recorded before the next begins.
It handles the project management so you can focus on the decisions that are actually yours: what should this do, what should it look like, what matters and what doesn't. It's project-agnostic — the method drives any serious build, not only software — but if you're making an app, this is the structure that gets you there.
Short, problem-first reads on the ideas that make Throughliner click. Each one is the whole thing, right here — the cards below link to complete articles on this site.
Months of writing rules for an AI, getting worse results the harder I tried — until the conventions of legislative drafting turned out to be the answer. Ships with a free prompt.
A month later you can't remember why you built it that way — the throughline carries the reason alongside the work, so it's never lost.
You've got the slash commands but not the rhythm — how /plan, /next and /done fit into one repeatable loop, and how to break it.
You have an idea mid-build and don't want to lose it — the path every idea follows, from capture to done.
Most of your work gets sorted for you — but knowing the three flavours tells you when to ask for an audit, the one you'll reach for yourself.
Everyone is racing to solve memory. An agent that remembers everything and still decides on its own isn't fixed — it's broken in a way that's harder to catch.
Two ways forward, and neither is the "right" one — pick what fits where you are.
Ask questions, see how other non-coders are building, and hear about new features as they land. The reading lives here on the site; the Discord is the people.
Join the DiscordStuck now and want a person on it? We work on your actual project together and get you a clear next step you can run immediately.
See coachingDeciding whether to put a team through this, or wanting to show it to whoever would? There's a page written for that reader.
Coaching for teams