Flags

All available flags for the ds-start init command.

Init Flags

All flags are optional. When no module flags are provided, the interactive wizard guides you through three build paths: recommended production starter, app with auth, or base app.

FlagDescription
--baseScaffold the foundation only, no modules. Cannot be combined with module flags
--prismaAdd Prisma 6 ORM with PostgreSQL and typed JSONB. Mutually exclusive with --drizzle
--drizzleAdd Drizzle ORM with PostgreSQL. Mutually exclusive with --prisma
--authAdd Better Auth with email/password, Google OAuth, and route protection. Requires --prisma or --drizzle
--clerkAdd Clerk managed authentication with pre-built components and route protection. No database required
--stripeAdd Stripe billing with subscription management, customer portal, and webhooks. Requires --auth or --clerk
--emailAdd transactional email with Resend and React Email templates
--file-uploadsAdd S3-compatible file uploads with presigned URLs. Works with AWS S3, Cloudflare R2, MinIO, Backblaze B2
--zustandAdd Zustand client state management with typed stores and devtools middleware
--formsAdd JSON-driven form renderer with classic, conversational, and multistep view modes
--github-workflowsAdd GitHub Actions CI pipeline with lint, typecheck, build, and secret scanning
--vercel-deployAdd Vercel CD pipeline with preview and production deploys. Implies --github-workflows
-y, --yesSkip the wizard and apply the recommended production preset (Prisma, Better Auth, email, GitHub Actions CI)

--base vs -y

These two flags represent opposite ends of the spectrum:

  • --base — Foundation only, zero modules. The minimal starting point.
  • -y — The recommended production preset with Prisma, Better Auth, email, and GitHub Actions CI. No prompts.

Without either flag, the interactive wizard lets you choose your path.

Module Dependencies

Some modules have prerequisites:

  • --prisma and --drizzle are mutually exclusive (one ORM per project)
  • --auth requires --prisma or --drizzle (Better Auth stores sessions in the database)
  • --stripe requires --auth or --clerk (billing needs user identity)
  • --vercel-deploy implies --github-workflows (CD builds on CI)

On this page