Guides
Practical guides for shipping with a coding agent.
Short, practical notes on the parts of an AI SaaS launch that decide whether it works: agent readiness, pre-launch verification, and choosing between Claude and Codex.
How to make a SaaS boilerplate coding-agent ready
Repo memory, safe edit zones, setup checks, and a verification contract that lets Claude or Codex customise a repo without breaking billing or email.
Read guideWhat to verify before launching a Next.js SaaS starter
The core launch path checked end to end: checkout, signed webhooks, email delivery, Postgres records, discovery files, and a clean production build.
Read guideClaude vs Codex for customising a SaaS boilerplate
How Claude and Codex differ when customising a SaaS repo, where each is stronger, and why the same repo memory lets you use both.
Read guideStripe webhook and Resend fulfilment checklist for Next.js SaaS
Verify the signature, process the event once, persist the purchase, then send Resend delivery email with a recovery path.
Read guideHow to write reusable agent prompts for SaaS work
A practical structure for reusable SaaS prompts that keep Claude, Codex, Cursor, or Windsurf focused on safe, verifiable repo changes.
Read guide