

Built a Next.js boilerplate that saves Claude ~20k tokens per session by removing every choice it has to make
I have been building side projects with Claude Code for the last year and the same thing kept happening on every new repo.
Claude reads the codebase. Claude asks where my auth helpers live. Claude picks a state management approach that is different from the one I used last week. By the time it writes any actual code I have burned a few thousand tokens just teaching it the project again.
The thing that broke me was realizing I had explained my Stripe webhook pattern to Claude probably forty times across different repos. Same explanation, same code, different session.
So I tested a hypothesis. Most stacks give the AI too many choices, and every choice costs tokens to deliberate. I built the same feature twice. Once on a default Next.js setup. Once on a stack where I had picked one way to do everything and documented it.
The opinionated version finished in roughly 60% fewer back and forths. Not because the AI got smarter. Because there was nothing to decide.
That stack is what I packaged into LaunchPaid. The site is launchpaid.app.
What is in it:
Next.js, TypeScript, Prisma, Supabase, Tailwind, shadcn. One auth pattern. One way to fetch data. One Stripe setup. Plus 15 skills in the .claude/ folder for the recurring stuff (Prisma migrations, Stripe webhooks, adding a new dashboard page, the auth flow). Copy-paste templates for new routes, server actions, forms. A memory layer that holds stable project context so Claude does not have to rediscover it every session. And on top of that a persistent memory so each session understand your project as much as possible.
Average session on a new feature is running around 20k tokens for me now. Before this it was on average 70k tokens.