Guides for people who ship.

Most product blogs are announcements wearing the costume of articles. This one is built the other way round. Each guide takes a single question that matters when you are actually trying to ship something — how do I describe what I want, what is safe to let an agent do to my codebase, what breaks after launch and who notices first — and answers it at the length the question deserves.

It is written for two readers who rarely share a bookshelf. The first has an idea and no intention of learning to code: a founder, an operator, a shop owner who needs a booking page that actually saves bookings. The second is a working engineer deciding how much rope to give an AI agent inside a repository that already has users. The guides are labelled by track so you can tell which is which before you commit to a scroll.

The rules we write under are simple. No invented customers, no invented metrics, no benchmarks that cannot be reproduced. Where a capability sits behind a paid plan, the guide says so. Where the product does something narrower than the industry phrase for it, the guide describes what it actually does instead of borrowing the phrase. That is less exciting and considerably more useful.

Nothing here requires an account to read. If you want the shorter, click-by-click version of any of it, the documentation is the companion volume — most guides link across to it at the end, and the section anchors are on the cards further down this page.