Hype StackHypeStack

Create a Project

The Hype CLI scaffolds a new Hype Stack project with one command.

CLI map

CommandDocsJob
createThis pageScaffold the bare template
composeCompose Your StackInstall packs into a project
templateAdd a TemplateInstall a curated pack bundle
onboardOnboardingFill .env from installed packs
deployDeployShip the web stack, mobile app, and extension
mcpMCP ServerExpose CLI tools to AI agents

You may not need this command

If your next step is compose or template, you can skip create. Run either without a project and it runs the same scaffolding wizard for you first, then installs your packs. Reach for create on its own only when you want the bare template with nothing added yet.

Usage

bash
npx @hype-stack/cli create

The CLI walks you through a few prompts:

  1. Project name and directory - where to scaffold it
  2. AI editors - cursor, t3code, claude, codex, copilot, opencode, windsurf (tick every one your team uses)
  3. Frontend look - a color theme and how round the corners should be
  4. Admin, mobile, and extension look - one question each, "copy the frontend settings?", answered yes by default

create clones the base template, the empty canvas. It does not pick a starter or install feature packs. Add those after with the template and compose commands, then run onboard to fill in your .env (both commands offer it at the end of a run).

Theming every app

The project ships four themable surfaces: the customer-facing frontend, the internal admin dashboard, the Expo mobile app, and the browser extension. Each carries its own theme and corner radius. The frontend section asks for both values. Then admin, mobile, and extension each open with "copy the frontend settings?", which is what most people want, so accepting all three is three keypresses. Say no to any of them and you get that app's own theme and radius pickers. Sections only appear for apps your project has.

Themes are color only and radius is shape only, so switching palette never reshapes your buttons and cards. The same theme catalog drives all four apps; the CLI converts the tokens to the format each app uses (the mobile app's NativeWind stylesheet takes HSL channels, the others take OKLCH).

Every answer has a flag, which is how the preview site's copy-command button reproduces what you saw on screen:

bash
npx @hype-stack/cli create my-app --theme ocean --radius 0.75rem --admin-theme midnight --mode dark
FlagWhat it does
-t, --theme <theme>Frontend color theme.
--admin-theme <theme>Admin color theme. Defaults to --theme.
--mobile-theme <theme>Mobile app color theme. Defaults to --theme.
--extension-theme <theme>Browser extension color theme. Defaults to --theme.
--radius <value>Frontend corner radius as a CSS length: 0rem, 0.375rem, 0.625rem, 0.75rem, 1rem, 1.4rem.
--admin-radius <value>Admin corner radius. Defaults to --radius.
--mobile-radius <value>Mobile app corner radius. Defaults to --radius.
--extension-radius <value>Browser extension corner radius. Defaults to --radius.
--mode <light|dark>Color mode the app boots in.

A flag skips its question. Anything you leave out is still prompted for, so you can pin just the theme and pick the rest interactively. The same flags work on compose and template.

What gets scaffolded

After the CLI finishes, you get:

my-app/
  apps/
    backend/     # Hono API with Prisma, Kysely
    frontend/    # React SPA with TanStack Router, Tailwind
    mobile/      # Expo app with expo-router, NativeWind
    extension/   # Browser extension with Vite, Tailwind
  packages/      # Shared types, utils, configs
  docker-compose.yml
  nx.json
  pnpm-workspace.yaml
  stack.json

The stack.json file tracks the project's apps, paths, and installed packs:

json
{
  "name": "my-app",
  "installedPacks": []
}

After scaffolding

Install dependencies and start the stack:

bash
cd my-app
pnpm dev

If you opted into Docker services and migrations during create, Postgres, Valkey, and RustFS are already running. If not, start them with docker compose up -d from apps/backend.

See Fastest Template for the full first-run walkthrough.

Sponsor open source

Every purchase and sponsorship funds my 8+ years of work on open source given freely to the community. It keeps the lights on, funds new packs, and keeps the ecosystem alive. Even a small tier means a lot. Thank you!

Sponsor on GitHub