Documentation Index
Fetch the complete documentation index at: https://docs.cubby.pro/llms.txt
Use this file to discover all available pages before exploring further.
cubby init
Scaffold a new Cubby app with Next.js and Prisma preconfigured for the platform (SQLite by default; Neon Postgres on Builder/Pro).Usage
Arguments
| Argument | Description | Default |
|---|---|---|
name | App name or . for current directory | my-cubby-app |
Examples
What Gets Created
The scaffold includes a complete Next.js 16 + Prisma setup (SQLite by default):App Name Rules
App names must be DNS-safe:- 3-30 characters
- Lowercase letters, numbers, and hyphens only
- Must start and end with a letter or number
My Appbecomesmy-appapp_namebecomesapp-name
After Initialization
npm run dev needs no Docker and no local database —
Cubby runs prisma db push for you on deploy. Hot reload works immediately.
If you chose the Neon Postgres template, use cubby dev instead — it runs a local
Postgres container and requires Docker (see cubby dev).
The CUBBY.md File
Every scaffolded app includes aCUBBY.md file that provides context for AI coding assistants. It documents:
- Platform constraints
- API route patterns
- Database access patterns
- Authentication (handled by Cubby SSO)
- What NOT to do
Customizing the Schema
Editprisma/schema.prisma to define your data models:
data/ dir must exist first, or prisma db push fails with
P1003 Database does not exist:
prisma db push for you — so for frontend work you can just run
npm run dev. On the Neon template, cubby dev (Docker) handles schema sync automatically.
Next Steps
Aftercubby init:
- Install dependencies:
npm install - Start development:
npm run dev(SQLite/no-DB; no Docker) orcubby dev(Neon; Docker) - Edit your schema:
prisma/schema.prisma - Build your app: Add pages in
app/ - Deploy:
cubby deploy
Related Commands
cubby dev- Start local developmentcubby deploy- Deploy to productioncubby check- Validate project