Blueprints

Blueprints are complete starter projects — not just library presets. Each blueprint generates a functional application with pages, layouts, components, and routes that you can run immediately after generation.

When you select a blueprint, the CLI pre-fills the stack, libraries, database, ORM, and sometimes deployment from the blueprint's composition. You only choose the linter, tooling, git, and package manager.

Quick Start

bunx create-faster my-project --blueprint dashboard --linter biome --git --pm bun

npx create-faster my-project --blueprint dashboard --linter biome --git --pm npm

pnpm dlx create-faster my-project --blueprint dashboard --linter biome --git --pm pnpm

In interactive mode, the CLI prompts you to choose between a blueprint or a custom project when blueprints are available:

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

Available Blueprints

Business

Web3

AWS

What You Can Customize

Blueprints define the application architecture (stacks, libraries, database, ORM, and optionally deployment). You choose the developer experience:

• --linter — Biome, ESLint + Prettier, ESLint, or Prettier
• --tooling — Husky (git hooks with lint-staged)
• --git — Initialize a git repository
• --pm — Package manager (bun, npm, pnpm)

How Blueprints Work

A blueprint combines:

1. A preset composition — stacks, libraries, and project addons
2. Application code — pages, layouts, components, and routes
3. Extra dependencies — packages specific to the blueprint (e.g., recharts for dashboard charts)
4. Extra environment variables — blueprint-specific configuration

Blueprint application code overrides the default structural templates. For example, a blueprint's page.tsx replaces the stack's default landing page with a functional application page.