create-prism-app

create-prism-app

Scaffold a production-grade, opinionated full-stack starter in seconds — one CLI, a growing collection of curated stacks.

Every starter ships with sensible defaults, auth flows, typed config, tests, and agent-ready docs — wired together so you can install and start building instead of bikeshedding setup.

npm create prism-app@latest

Stacks

Backends share the same security model — RS256 JWT access + refresh rotation (reuse-detected), HMAC-signed requests, RBAC, optional Redis, and Socket.io.

Quick start

Interactive (pick a stack, name, package manager):

npm  create prism-app@latest
pnpm create prism-app@latest
yarn create prism-app
bun  create prism-app

Or with npx:

npx create-prism-app@latest

Non-interactive (CI / scripted):

npm create prism-app@latest -- \
  --name my-app --template nestjs --pm pnpm --git --install

Options

Requires Node.js >= 20.

How it works

Templates live in templates/ and are fetched on demand with giget from github:danh121097/boilerplate-kit/templates/<name>#master — so you always get the current starter without installing every stack. After fetching, the CLI rewrites package.json, optionally runs git init + dependency install, and prints next steps.

Privacy

Zero telemetry. The CLI does not collect, transmit, or store any usage data.

Contributing a stack

The collection is designed to grow. A new stack is just a folder under templates/<name>/ plus three small CLI touch-points:

1. Add the starter to templates/<name>/ (must include package.json + README.md).
2. Register the key in src/types.ts (TEMPLATES) and label it in src/wizard/prompt-template.ts.
3. Update the registry test in src/__tests__/template-registry.test.ts.

See an existing backend (templates/fastify) or frontend (templates/reactjs) for the conventions, then open a PR.

Development

pnpm install
pnpm build
node dist/cli.mjs --version
pnpm test

Link the binary to run it from anywhere:

npm link                       # registers `create-prism-app` on your PATH
create-prism-app --version
npm unlink -g create-prism-app # undo

When linked, the CLI auto-detects the sibling templates/ directory (via realpath on dist/cli.mjs) and copies locally — no GitHub round-trip. Force a specific templates root with BOILERPLATE_KIT_LOCAL=/abs/path (or =1 for $cwd/templates). Local copies mirror what git would ship (tracked plus untracked-but-not-ignored files), minus node_modules, build output, lockfiles, .env, and keys. When git can't list the template (no checkout, or not under <repo>/templates/), a plain copy runs instead and also drops generated auto-import typings.

License

MIT © danh121097