Create FasterCreate Faster

Interactive CLI

Step-by-step guide to the interactive workflow

The interactive CLI provides a guided experience for creating projects. Run the command without any flags to start:

# Using your favorite package manager
bun create faster
npm create faster
pnpm create faster

Workflow Overview

The CLI walks through configuration in a logical sequence, starting with naming decisions, then application setup, followed by infrastructure choices, and finally installation preferences.

Step-by-Step Process

Project Name

First, you'll name your project:

◇  Name of your project?
│  my-saas

The CLI validates that no file or directory with this name exists in the current directory. For single-app projects, this name becomes the application directory. For multi-app projects, it becomes the monorepo root.

Blueprint or Custom

If blueprints are available, the CLI asks how you want to start:

◇  How do you want to start?
│  ● Use a blueprint (pre-composed starter project)
│  ○ Custom (choose everything yourself)

Blueprint: Skips app configuration, database, and ORM — the blueprint defines all of those. Some blueprints also predefine deployment (e.g., Lambda blueprints). You proceed to deployment (if not predefined), linter, tooling, git, and package manager selection.

Custom: Continues with the full configuration flow below.

See Blueprints for available starter projects.

Application Count

Next, specify how many applications to create:

◇  How many apps do you want to create?
│  Eg: a backend + a frontend = enter 2
│  Only a Next.js app = enter 1
│  Turborepo will be used if more than one
│  3

Single app (1): Generates a standard framework project structure.

Multiple apps (2+): Automatically configures Turborepo with apps in apps/ directory and shared packages in packages/.

App Configuration

For each application, you'll configure its name, stack, and modules.

App Name

For single-app projects, the app name matches the project name automatically. For multi-app projects, you'll name each application:

◇  Name of the app #1?
│  web

◇  Name of the app #2?
│  mobile

◇  Name of the app #3?
│  api

Stack Selection

Choose the framework for each app. Stacks are organized by type:

◇  Select the stack for web
│
├ Web / Mobile App
│  ● Next.js (React framework with SSR)
│  ○ TanStack Start (Full-stack React framework)
│  ○ Expo (React Native framework)
│
└ Server / API
   ○ Hono (Fast web framework)
   ○ Node.js (Plain TypeScript server)

The stack determines the base template and available modules.

Module Selection

After selecting a stack, choose optional modules to include. Available modules depend on the selected framework and are grouped by category:

◇  Do you want to add any Next.js modules to web?
│
│  UI
│  ◻ shadcn/ui
│  ◻ Next Themes
│
│  Content
│  ◻ MDX
│  ◻ PWA
│
│  Auth
│  ◻ Better Auth
│
│  API
│  ◻ tRPC
│
│  Data Fetching
│  ◻ TanStack Query
│  ◻ TanStack Devtools
│
│  Forms
│  ◻ React Hook Form
│  ◻ TanStack Form

Use arrow keys to navigate and space to toggle selections.

Database Selection

Choose a database provider or skip:

◇  Include a database?
│  ● PostgreSQL
│  ○ MySQL
│  ○ SQLite
│  ○ None

Selecting a database enables ORM selection in the next step. Database configuration is shared across all applications in a monorepo via the packages/db package.

ORM Selection

If you selected a database, choose an ORM:

◇  Configure an ORM?
│  ● Drizzle
│  ○ Prisma
│  ○ None

The ORM package includes:

  • Type-safe database client
  • Schema definitions
  • Authentication integration (if auth module selected)
  • Database connection configuration

Deployment Platform

Choose an optional deployment platform:

◇  Deployment platform?
│  ● SST
│  ○ Terraform (AWS)
│  ○ None

SST: Generates sst.config.ts with stack-aware resource mapping. See SST.

Terraform (AWS): Generates a complete infra/ directory with AWS provider, S3 backend, and per-environment configs. See Terraform (AWS).

Linter Selection

Choose a linter/formatter:

◇  Code quality tools?
│  ● Biome
│  ○ Oxlint + Oxfmt
│  ○ ESLint + Prettier
│  ○ ESLint
│  ○ Prettier
│  ○ None

See Biome, Oxlint + Oxfmt and ESLint for details.

Git Initialization

Choose whether to initialize a Git repository:

◇  Initialize Git?
│  Yes / No (default: Yes)

If enabled, the CLI runs git init after file generation and before the dependency install, so the prepare script of Husky finds the repository and activates the git hooks. This is required if you plan to use Husky for git hooks. With --no-install, the hooks activate on your first install.

Tooling

Select additional development tools:

◇  Add any extras?
│  ◻ Husky

Husky: Configures pre-commit hooks with lint-staged (requires Git and a linter). See Husky.

Dependency Installation

Finally, choose whether to install dependencies immediately and which package manager to use:

◇  Install dependencies now?
│  ● Install with bun
│  ○ Install with pnpm
│  ○ Install with npm
│  ○ Skip installation

If you select a package manager, the CLI runs the installation process:

◆  Installing dependencies with bun...
│
◇  Dependencies installed successfully!

If you skip, you can manually run the installation later:

cd my-saas
bun install

Validation Rules

The CLI enforces compatibility requirements during configuration:

ORM requires Database: You cannot select an ORM without first selecting a database provider.

Husky requires Git: The Husky extra is only available if Git initialization is enabled.

Unique app names: In multi-app projects, each application must have a unique name.

If you make incompatible selections, the CLI displays an error message explaining the requirement.

After Generation

Once file generation completes, the CLI runs post-generation tasks if configured:

◆  Initializing git repository...
│
◇  Git repository initialized successfully!

Then displays a comprehensive summary with an auto-generated command to recreate the project:

◇  📂 Summary ────────────────────────────────────╮
│                                                 │
│  🏠 Structure:                                  │
│                                                 │
│  📦 my-app/                                     │
│  ├─ 🚀 apps/                                    │
│  │  ├─ web/ (Next.js +4 libraries)              │
│  │  ├─ mobile/ (Expo +1 library)                │
│  │  ├─ api/ (Hono +1 library)                   │
│  ├─ 📦 packages/                                │
│  │  └─ db/ (Drizzle + PostgreSQL)               │
│  └─ ⚙️  Turborepo, Git, Biome                   │
│                                                 │
│  💡 Next steps:                                 │
│                                                 │
│  cd my-app                                      │
│                                                 │
│  # Development:                                 │
│  bun run dev        # Start development server  │
│                                                 │
│  # Production:                                  │
│  bun run build  # Build for production          │
│  bun run start  # Start the app                 │
│                                                 │
│  # Git:                                         │
│  git add .                                      │
│  git commit -m "chore: initial commit"          │
│  git branch -M main                             │
│  git remote add origin <your-repo-url>          │
│  git push -u origin main                        │
│                                                 │
├─────────────────────────────────────────────────╯
│
└  🚀 Project created successfully at /home/bob/my-app!
🔥 You can recreate this project with the following command:

bunx create-faster my-app \
  --app web:nextjs:shadcn,next-themes,mdx,pwa \
  --app mobile:expo:nativewind \
  --app api:hono:aws-lambda \
  --database postgres \
  --orm drizzle \
  --git \
  --pm bun \
  --linter biome

The auto-generated command allows you to share your exact configuration with team members or reproduce the project setup for testing.

On this page