Template recipes
Copy proven Nextron stack selections for common application foundations.
Stack recipes
A template is a set of choices.
Nextron composes the base app with provider-aware modules. Use these recipes when the generator asks what your project needs.
$ npx @edwinfom/nextron@latest create my-appMinimal app
The cleanest Nextron base for a product that does not need infrastructure yet.
Good forMarketing sites, prototypes, and custom architectures
- Database
- None
- Authentication
- None
- Additional modules
- None
- Next.js App Router
- Strict TypeScript
- Tailwind CSS
- Typed environment shell
SaaS foundation
A complete account, data, dashboard, payment, and background-job foundation.
Good forB2B products and team workspaces
- Database
- Drizzle + PostgreSQL + Neon
- Authentication
- Better Auth
- Additional modules
- tRPC, Dashboard, Stripe, Inngest
- Protected dashboard
- Typed procedures
- Stripe webhook
- Inngest function registry
AI product
A streaming AI surface with auth, persistence-ready boundaries, and typed APIs.
Good forCopilots, assistants, and knowledge tools
- Database
- Drizzle + PostgreSQL + Neon
- Authentication
- Clerk
- Additional modules
- AI, tRPC, Dashboard
- Streaming chat route
- Provider client
- Chat components
- Protected product shell
Merchant of Record
A compact paid-product base using Polar for checkout, tax handling, and customer access.
Good forMicro-SaaS, digital goods, and paid tools
- Database
- Prisma + PostgreSQL + Supabase
- Authentication
- NextAuth
- Additional modules
- Polar, Dashboard, Inngest
- Checkout route
- Customer portal
- Signed webhook
- Protected settings
Typed backend
A focused server foundation with typed procedures and retryable background work.
Good forProduct APIs, service layers, and automation
- Database
- Drizzle + PostgreSQL + local
- Authentication
- None
- Additional modules
- tRPC, Inngest
- Typed API router
- Database schema
- Function registry
- Validated server secrets
How the recipe becomes your code
The generator resolves compatibility before it writes files, then records every choice for later additions.
- SelectAnswer the interactive stack prompts.
- ComposeCompatible templates and dependencies are merged.
- ValidateEnvironment variables and file mappings are checked.
- OwnInspect, change, and deploy normal source code.
Recipes are guidance for the interactive generator. There is no template flag or remote template registry, so the pages never hide important provider decisions.
Follow the generator walkthroughWhat every recipe includes
Every generated project starts from the same readable Next.js base:
my-app/
├── src/
│ ├── app/
│ ├── shared/
│ └── env.ts
├── AGENTS.md
├── CLAUDE.md
├── nextron.config.ts
├── .env.example
└── package.jsonSelected modules extend this base under src/modules and add only the routes, packages, and
environment variables they declare. The generator validates required templates before writing the
application.
Adjust a recipe safely
You can change any provider choice while answering the prompts, but keep these compatibility rules in mind:
- Better Auth and NextAuth require a database module.
- Clerk can be used without a database.
- Dashboard requires authentication.
- PostgreSQL with Neon uses the Neon serverless driver.
- Other PostgreSQL providers use the standard
postgresdriver in Drizzle projects.
After generation, review Project structure and configure the module-specific environment variables.