What I built. projectblueprint.io — a live digital-product business: static landing page, Stripe Payment Link checkout, and a serverless download endpoint that re-verifies every purchase against Stripe (retrieve the Checkout Session with line_items expanded, require payment_status === “paid”, price allow-list) before streaming the file. Also a GitHub repo with the free sample. Everything from domain DNS to the live checkout happened in one working day. How Claude Code was used. Two layers: Content agents. Eight Claude Code sessions ran in parallel, each writing one “blueprint” (a complete build spec for a product) against a shared written format contract. The contract — required sections, quality bar phrased as defects (“‘Add auth’ is a defect; name the library, version, route group”), word band — is what kept eight independent sessions coherent. Zero format drift across eight writers. Build agent. One session (this one’s sibling) did the site, Stripe wiring, DNS, deploy — and proved delivery with a real live purchase before calling it done. What I learned: Verification gates beat trust. Every milestone ends with exact commands + expected output. Example, runnable right now against the live site: $ curl -s " https://projectblueprint.io/api/download?session_id=forged " | jq .code # expect: “unknown_session” An agent can argue with your judgment; it can’t argue with an expected-output diff. The what-NOT-to-build list matters more than the feature list. Agents gold-plate. Prohibitions (“No accounts. No A/B framework.”) stopped it cold. A false success I caught: a dashboard flow looked completed (the page even contained the success word) while the API said nothing had happened. Rule since then: UI text proves nothing; verify state through the API you’d bet money on. Literally, in this case. Format contracts scale agents better than prompts. The eight writers got ~200 words of task prompt each; the 700-word shared contract did the real steering. The full sample blueprint (complete, free, no signup) is at https://projectblueprint.io/validation-machine if you want to see the gate format in the wild. Happy to go deep on any of it. submitted by /u/operastudio
Originally posted by u/operastudio on r/ClaudeCode