Launchpad

A Next.js starter with auth, billing and an AGENTS.md your agent will follow

Sam CarterLaunched 4 weeks agoTemplateWorking · checked 3 hours ago
0:42

About

Most starters are built for humans. Launchpad is built for you and your agent: auth, Stripe billing, emails and an admin panel, plus an AGENTS.md that explains the conventions so Claude Code, Codex or Cursor extend it the right way.

How it was made

Shared by the maker. Numbers are their own estimate.

Build time
Ongoing
AI spend
$90
Prompts
~300
Written by AI
90%

Agents

  • Claude Code

    100% of the work

    Built and maintains it

MCP servers2

  • Supabase

    Database and auth set-up

  • Stripe

    Products and webhooks

Build recipe

The code is on GitHub. If you’d rather build it yourself than fork it, paste this into your own agent.

Written by Claude Code

From the project’s code and history · 359 words

Build a template called Launchpad: a Next.js starter with auth, billing and an AGENTS.md your agent will follow.

What it does

Most starters are built for humans. Launchpad is built for you and your agent: auth, Stripe billing, emails and an admin panel, plus an AGENTS.md that explains the conventions so Claude Code, Codex or Cursor extend it the right way.

Stack

Use Next.js, Supabase, Stripe, Tailwind, shadcn/ui. The original was built with Claude Code in Ongoing, for about $90 in AI usage.

How it fits together

  • A starter with auth, billing, email and an admin view
  • An AGENTS.md that explains the conventions to coding agents
  • Scripts that set up a new project in one command

Build it in this order

  1. Pick the conventions and write them down first
  2. Build auth, billing and email with tests
  3. Add the admin view
  4. Write AGENTS.md and try a feature using only it
  5. Add a setup script and a short README

Tools to connect

  • Supabase MCP: database and auth set-up
  • Stripe MCP: products and webhooks

A prompt that worked: Write an AGENTS.md that works

Read the whole repo. Write an AGENTS.md under 150 lines that tells a coding agent: how to run, test and lint; where each kind of code lives; the five conventions that matter most here (with a file that shows each one); and what never to do. Then try a small task using only AGENTS.md as guidance and tell me what was missing.

Watch out for

  • Every feature you add is something people must delete; keep it lean
  • Agents follow AGENTS.md literally, so keep it short and concrete

Done when

  • A new project is running in under ten minutes
  • An agent can add a feature by following AGENTS.md
  • Tests cover auth and billing

Before writing code, ask me up to five questions about who this engineering template is for and what the first version must do. Then work in small steps: after each one, tell me how to try it and wait for my feedback.

Discussion

3 comments · 1 member tried it

  • Priya RamanTried it3 hours ago

    Clean idea and it actually works. The build log is the most useful part for me, I'd love more detail on how you structured the prompts in week two.

  • Kenji Mori1 day ago

    What did the agent struggle with most? Always curious where people had to step in.

    • Sam CarterMaker2 hours ago

      Thanks! Good question, I'll write it up in the build log this week.