shadcn/ui
- Adds shadcn-compatible files and a starter button component.
- Depends on Tailwind CSS, which is fixed on in the MVP.
- Developers can extend the component set after downloading the project.
Documentation
Practical notes for the website builder, generated project output, supported stack options, and the published CLI package that reuses the same shared generator core.
Open Builder01
BaseForge is a TypeScript-first developer project generator. The MVP is website-first: users choose options, preview generated output, and download a zip.
The generated project is intended to be unzipped and edited locally. The shared generator core is also used by the published `@baseforge/create` CLI package.
02
unzip my-app.zip
cd my-app
npm install
npm run dev
npm run typecheck
npm run buildThe generated project supports pnpm guidance when pnpm is selected in the builder.
pnpm install
pnpm dev03
04
These are the exact MVP option groups exposed by `@baseforge/schema`. Unsupported frameworks, languages, routers, databases, ORMs, auth providers, and package managers are not documented as available.
| Category | Supported options | Notes |
|---|---|---|
| Framework |
| MVP-supported. |
| Language |
| MVP-supported. |
| Router |
| MVP-supported. |
| Project structure |
| MVP-supported. |
| Styling |
| MVP-supported. |
| UI |
| MVP-supported. |
| Database |
| MVP-supported. |
| ORM |
| MVP-supported. |
| Auth |
| Credentials scaffold only. |
| Docker |
| Local PostgreSQL only. |
| Package manager |
| MVP-supported. |
05
The generated project keeps `app/`, `components/`, and `lib/` at the project root. Generated projects do not use a `src/` directory.
app/
layout.tsx
page.tsx
globals.css
components/
lib/
package.json
tsconfig.json
next.config.ts
postcss.config.mjs
.env.example
.gitignore
README.md06
npm run db:generate
npm run db:push
npm run db:studiodocker compose up -d
docker compose down07
`.env.example` is only an example. Replace placeholder secrets and keep production values out of source control.
08
Common scripts are generated for every project. Prisma scripts are added only when Prisma is selected.
09
After download, unzip locally, install dependencies, copy `.env.example` to `.env.local` when selected features need env vars, configure values, and run checks before deployment.
cp .env.example .env.local
npm install
npm run dev
npm run typecheck
npm run buildThe exact env setup depends on the selected optional features.
10
11
12
CLI generation is available through the published `@baseforge/create` package and uses the same shared generator core as the website.
npx @baseforge/create@latest13