Blueprints
Pre-composed starter projects that generate complete, functional applications with opinionated architecture and application code.
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 org-dashboard --linter biome --git --pm bunnpx create-faster my-project --blueprint org-dashboard --linter biome --git --pm npmpnpm dlx create-faster my-project --blueprint org-dashboard --linter biome --git --pm pnpmIn 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
| Blueprint | Description |
|---|---|
| Org Dashboard | Dashboard with auth, RBAC, admin panel, and example CRUD |
| Showcase | SEO/GEO-optimized SaaS landing page with blog and programmatic pages |
Web3
| Blueprint | Description |
|---|---|
| dApp (Privy) | Web3 dApp with Privy wallet auth, wagmi, and user management |
| dApp (RainbowKit) | Web3 dApp with RainbowKit wallet connection, SIWE auth, and wagmi |
AWS
| Blueprint | Description |
|---|---|
| Lambda (SST) | AWS Lambda monorepo with API Gateway, SQS worker, and EventBridge cron |
| Lambda (Terraform) | AWS Lambda monorepo with API Gateway, SQS worker, and EventBridge cron |
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:
- A preset composition — stacks, libraries, and project addons
- Application code — pages, layouts, components, and routes
- Extra dependencies — packages specific to the blueprint (e.g.,
posthog-jsfor analytics) - 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.
Modules
Modules are opt-in libraries that add functionality to an app — UI components, authentication, APIs, data fetching, and more. Each module is scoped to its supported stacks.
Agent Context
Every generated project ships with AGENTS.md and CLAUDE.md so AI coding agents understand the stack, conventions, and wiring out of the box.

