cnippet-stack

Install full integrations — auth, database, payments, email, storage — into your existing Next.js app in minutes.

npx cnippet-stack init better-auth

Unlike boilerplates you fork or greenfield generators, cnippet-stack injects working integrations into the project you already have. It detects your setup (App Router, src/ dir, package manager, ORM, path aliases), asks only the questions it can't answer itself, and writes production-quality code with safe merge strategies — never blindly overwriting your files.

How it works

1. Detects your project: Next.js version, router, TypeScript, package manager, Prisma, aliases — all read statically, nothing executed.
2. Asks a few questions (e.g. which OAuth providers) — everything detectable is never prompted.
3. Plans the install and shows you a full diff preview before touching anything.
4. Applies files with per-file strategies: create (fails if the file exists), append (idempotent, markered blocks — e.g. Prisma schema models), and AST-based injection (e.g. wrapping a provider in your layout.tsx).
5. Finishes the plumbing: appends env placeholders (auto-generating secrets), installs dependencies with your package manager, runs post-install commands, and lists the manual steps no CLI can do for you (like OAuth console setup).

Backups of every modified file are kept in .cnippet/backup/<timestamp>/.

Commands

| Command | Description | |---|---| | npx cnippet-stack init <recipe> | Install a recipe into the current project | | npx cnippet-stack list | List available recipes | | npx cnippet-stack login | Log in (required for pro recipes) | | npx cnippet-stack logout | Log out and revoke this device's token | | npx cnippet-stack whoami | Show the logged-in user |

Useful flags for init

| Flag | Effect | |---|---| | --dry-run | Show the full install plan without writing anything | | --yes | Skip prompts and confirmation, use recipe defaults | | --overwrite | Allow overwriting files that already exist | | --cwd <path> | Install into a different directory | | --json | Machine-readable output (for scripts and AI agents), answers via --answers '<json>' |

Recipes

Recipes are versioned, Zod-validated manifests rendered server-side by the registry — browse them at stack.cnippet.dev/recipes. Free recipes need no account; pro recipes require cnippet-stack login and a license.

Current lineup includes better-auth (email/password + OAuth, Prisma models, middleware, starter UI), prisma, biome, and more shipping continuously — no CLI update needed when recipes are added or improved.

Requirements

• Node.js 18+
• A Next.js project using the App Router

Telemetry

The CLI sends anonymous install events (recipe name, version, success, duration). Opt out with CNIPPET_TELEMETRY=0.

Ecosystem

• stack.cnippet.dev — recipe browser, dashboard, licensing
• next.cnippet.dev — in-depth written integration guides
• ui.cnippet.dev — component library

License

MIT — see LICENSE. Recipe templates are rendered by the registry service and are subject to their own tiers/terms.