next-forge

Scaffold and maintain multi-package Turborepo monorepo SaaS starters.

246|42|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/vercel/vercel-plugin --skill next-forge-vercel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: next-forge
Source: https://github.com/vercel/vercel-plugin/tree/main/skills/next-forge
Command: npx skills add https://github.com/vercel/vercel-plugin --skill next-forge-vercel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines building and maintaining a multi-package Turborepo SaaS starter by providing a battle-tested boilerplate and cohesive tooling for Next-forge projects.

Core Features & Use Cases

  • Monorepo boilerplate: integrated apps and packages scaffolded with Turborepo best practices.
  • Workspace orchestration: consistent cross-app imports, env validation, and shared tooling.
  • Use Case: quickly bootstrap a SaaS starter with Clerk, Prisma/Neon, Stripe, and more.

Quick Start

Run npx next-forge init to scaffold your project.

Frequently Asked Questions about next-forge

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

FAQPage Schema
How do I scaffold a Turborepo monorepo SaaS starter?

Scaffold a Turborepo monorepo SaaS starter by running `npx next-forge init`, which generates a production-grade multi-package project with integrated apps, shared tooling, and workspace orchestration.

What is included in a Turborepo SaaS boilerplate?

A Turborepo SaaS boilerplate includes multi-package workspace orchestration with integrated apps, consistent cross-app imports, environment variable validation, and shared tooling for rapid project bootstrapping.

Can I use Clerk, Prisma, and Neon in a Turborepo workspace setup?

Yes, you can integrate Clerk, Prisma, and Neon in a Turborepo workspace setup. The boilerplate provides cohesive tooling to quickly bootstrap a SaaS starter integrating these specific services.

How do I manage cross-app imports and environment variables in a Turborepo?

Manage cross-app imports and environment variables in a Turborepo by utilizing workspace orchestration patterns that enforce consistent shared tooling and environment validation across all workspace packages.

What's the best way to maintain shared tooling across multi-package Next.js apps?

The best way to maintain shared tooling across multi-package Next.js apps is using a Turborepo monorepo boilerplate that enforces consistent workspace orchestration, cross-app imports, and environment validation.