next-forge

Guides setup, customization, and deployment of the next-forge Turborepo Next.js SaaS template.

Updated Sep 17, 2026
One-click install
npx skills add https://github.com/ridhijain709/AIPORSCHE --skill next-forge-ridhijain709
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: next-forge
Source: https://github.com/ridhijain709/AIPORSCHE/tree/main/.agents/skills/next-forge/upstream
Command: npx skills add https://github.com/ridhijain709/AIPORSCHE --skill next-forge-ridhijain709

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Building a SaaS application from scratch requires wiring together authentication, payments, database, email, CMS, analytics, and security before writing any product code. This Skill provides expert guidance on the next-forge Turborepo template so you can initialize, configure, customize, and deploy a production-grade Next.js monorepo without reverse-engineering its structure. ## Core Features & Use Cases - Project Initialization & Setup: Walks through npx next-forge@latest init, environment variable configuration, database migrations with Prisma and Neon PostgreSQL, and Stripe CLI webhook testing. - Architecture Guidance: Explains the monorepo layout with seven apps (app, web, api, email, docs, storybook, studio) and over twenty shared @repo/* packages covering auth, payments, CMS, analytics, observability, and more. - Provider Swapping & Deployment: Documents how to replace default integrations (Clerk, Stripe, BaseHub, Resend) with alternatives like Supabase, Paddle, or Lemon Squeezy, and how to deploy apps to Vercel with correct environment variables. - Use Case: You want to launch a SaaS product quickly. Use this Skill to scaffold the monorepo, connect a Neon database, configure Clerk authentication and Stripe billing, then deploy the app, web, and api projects to Vercel. ## Quick Start Ask the assistant to initialize a new next-forge project and explain which environment variables are required to run it locally.

Frequently Asked Questions about next-forge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a new project with next-forge?

Run npx next-forge@latest init and the CLI prompts for a project name and package manager (bun, npm, yarn, or pnpm). After installation, set DATABASE_URL in packages/database/.env, run bun run migrate, then start development with bun run dev.

How do I run database migrations in a next-forge monorepo?

Run bun run migrate after editing packages/database/prisma/schema.prisma. This executes Prisma format, generate, and db push in sequence against the PostgreSQL database defined by DATABASE_URL.

Can I swap Clerk for another authentication provider in next-forge?

Yes, next-forge is modular. Replace the packages/auth directory with Supabase Auth, Auth.js, or Better Auth, then update the AuthProvider in the design system and the webhook handlers in the api app.

Does next-forge work if optional environment variables are missing?

Yes, all integrations besides the database are optional. Clients use optional chaining such as stripe?.prices.list(), so missing keys silently disable the corresponding feature instead of causing errors.

How do I deploy a next-forge monorepo to Vercel?

Create three separate Vercel projects with root directories apps/app, apps/web, and apps/api. Add environment variables per project or use Vercel Team Environment Variables, and update the NEXT_PUBLIC inter-app URLs to production domains.

How do I add shadcn/ui components to the next-forge design system?

Run npx shadcn@latest add [component] -c packages/design-system to add new components. Use bun run bump-ui to update existing shadcn/ui components across the design system package.