The verdict says build.
So here's the repo.
Validation tells you an idea is worth building. The next gap is the weeks of scaffolding between a yes and a running app. We close it: a validated idea becomes a runnable Next.js 15 repo, today, from the CLI or the public API.
What lands on disk
A spec, then a repo.
Not a chat window that dribbles out snippets. A written brief, then a runnable Next.js app on your disk, the way you would do it yourself if you had the week back. Add your GitHub token and it pushes the repo for you too.
A technical spec, not a vibe
The validated idea becomes a written build brief: data model, routes, auth model, the third-party services it needs. The same document an engineer would write before opening an editor.
A scaffolded Next.js repo
The spec compiles into a real Next.js 15 app. App Router, server components, a typed Drizzle data layer, CRUD routes per model, Stripe when the idea is paid. Folders where you would put folders.
Pushed to your GitHub
Run scaffold with --push and your own GitHub token, and it creates the repo and pushes the scaffold for you. No token? It commits locally with a README, .env.example, and CI wired up, then tells you to set one.
A real run. Generated with skeptra scaffold or POST /api/v1/scaffold/nextjs, which returns a zip.
The boring parts, already correct.
Most generated code wins the demo and loses the second week. We scaffold the things that are tedious to get right and miserable to retrofit.
Wins the demo. Loses week two.
Correct from line one.
const data: any = await fetch()any-typed, errors surface at runtime
Strict TypeScript from the Drizzle schema to the component props. No week-one hunt through "any" errors.
schema → queries → propsschema.ts ↛ query.tsschema and queries drift apart
A typed Drizzle schema, FK-ordered, with typed queries scaffolded alongside it, so the database and the app never drift apart.
pgTable(...) ⟶ typed query// TODO: wire Stripe laterpayments bolted on after the fact
When the idea is paid, Stripe is set up against the pricing the validator already worked out, ready for its first real charge.
stripe(price) ✓ validatedSame three layers, two outcomes. The line between a demo and a real app is whether they were built right the first time.
Validate it. Then build it.
The generator is the next link in the chain, not a different product. The idea you score today carries the spec the generator builds from. Score it, clear the read, and walk away with a runnable repo.
Score an idea firstAutomatic push to a fresh GitHub repo (with your own GitHub token set, otherwise it commits locally and tells you to set one), multi-tenant row-level security, and white-label themes all ship today. We say the day each one ships, and never before. No fake repos, no fake traction, and we never push on our own credentials.