ARCHE
FamiliesDocsExamplesBlogGitHub ↗
Documentation

Start

  • Getting started
  • Philosophy

Guides

  • First hour
  • Agent context
  • Verification
  • Package managers
  • Scaffold lifecycle
  • Showcase & portfolio

Walkthroughs

  • TypeScript fullstack
  • Convex product
  • Rust API & fullstack
  • Solana family
  • Customize & experiments
  • Automation (JSON/MCP)

CLI

  • Overview
  • Flags
  • Subcommands
  • Generated output

Presets

  • Preset catalog

Stack

  • TypeScript architecture
  • Convex
  • Rust
  • Solana
  • Authentication
  • Prisma store
  • tRPC

Operations

  • Deployment
  • Environment variables
  • Workers & queues
  • CI & testing
  • Scaling
  • Security
  • Troubleshooting

Reference

  • Stack links
  • Capabilities
  • This source repo
  • Code examples
← Documentation

CLI flags

Non-interactive and power-user flags for arche create.

1 min read

Flags apply to the main scaffold command (bun run dev:cli -- … from source).

FlagPurpose
--yesNon-interactive defaults (CI, agents, repeatability).
--dir=<path>Parent directory or exact project path for output.
--preset=<id>Starting point from the registry (see Presets).
--family=<name>Legacy family selection when migrating old scripts.
--pm=bun|pnpm|npmPackage manager. Bun default; pnpm first-class; npm experimental.
--backend=<name>Backend override on fullstack-capable routes.
--database=postgres|sqlite|mongodb|noneDatabase selection for supported routes.
--orm=prisma|drizzle|noneORM selection for supported routes.
--showcase / --no-showcaseKeep or strip demo/showcase routes and content.
--worker / --no-workerInclude or omit the BullMQ worker workspace.
--docker / --no-dockerGenerate or skip Dockerfiles and compose stubs.
--ci / --no-ciGenerate or skip GitHub Actions CI workflows.
--deployment=<mode>Deployment documentation mode baked into generated docs.
--dry-runPrint planned writes without touching disk.

By concern

GroupFlags
Output--dir, --output, --dry-run, --yes
Stack--preset, --family, --bundle, --backend, --database, --orm
Package manager--pm, --package-manager
Infra--worker, --docker, --ci, --deployment, --tests
Product--showcase, --install, --git
Agent / UX--help, --version

Walkthroughs: TypeScript · Automation

Examples

terminal
# TypeScript fullstack with pnpm catalogs
bun run dev:cli -- my-app --yes --preset=typescript-fullstack --pm=pnpm --dir=../projects

# Rust API only
bun run dev:cli -- my-api --yes --preset=rust-api --dir=../projects

# Preview without writing files
bun run dev:cli -- my-app --yes --dry-run

# API-only shape without worker
bun run dev:cli -- my-app --yes --preset=typescript-fullstack --no-worker

npm

--pm=npm exists for compatibility experiments. Bun is the default; pnpm is first-class on routes where the verification matrix records pnpm support. Prefer those unless you are explicitly testing npm output.