LabscoMCP early access ↗
REPO PACKAGEOFFICIAL

vercel next-forge

vercel · publisher7,120 GitHub starsMIT · Listed as freegithub.com/vercel/next-forge

LABSCO SUMMARY

Summary

next-forge is a Next.js SaaS starter template, and the single skill in this package is a generalist guide to it rather than one skill per integration.

What's here is one skill, "next-forge" itself, describing a Turborepo monorepo template that scaffolds a marketing site, a main app, an API, a docs site, an email app, and Storybook, all wired to vendor services out of the box — Clerk for auth, Stripe for payments, Resend for email, Sentry and BetterStack for observability, Arcjet for security, and PostHog or Google Analytics for tracking, plus SEO, feature-flag, cron, and internationalization packages. The skill's job is to answer questions about that template's installation, architecture, packages, customization, and deployment once you've run npx next-forge@latest init.

It's for someone starting a new Next.js SaaS product who wants those vendor choices already decided and wired together, and is willing to accept next-forge's opinions about which service does auth or billing rather than picking their own. It is not aimed at adding one feature to an existing app — the repository's structure only makes sense as the skeleton a project is scaffolded from.

READ MORE

Why there is only one skill for so much surface area.

The README lists roughly twenty integrated packages, but a single skill covers all of them at once, not one skill per package. That means it can explain how the pieces fit together in general terms; it won't have the package-by-package depth a set of per-integration skills would give you.

What it costs to use.

Getting real value from it assumes you already have, or are willing to create, accounts with the services next-forge is built around — Clerk, Stripe, Resend, and the rest — since next-forge's own setup is largely configuring those, not just running the CLI.