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 overview

How to run the Arche scaffold CLI today, and how it relates to the published package.

1 min read

The CLI lives in apps/cli, publishes as @arche/create, and exposes binaries arche and create-arche. Publication is guarded—use the development command until release gates clear.

Run today (source checkout)

terminal
bun run dev:cli -- <project-name> [flags]

Common non-interactive example:

terminal
bun run dev:cli -- my-app --yes --preset=typescript-fullstack --dir=../projects
RouteCommand
Published (after release)npx arche create my-app
Published (alternate)bunx arche create my-app
Developmentbun run dev:cli -- my-app

What the CLI does

Loading diagram…
  1. Copies and transforms template material for the chosen preset
  2. Applies package manager catalogs (Bun / pnpm / experimental npm)
  3. Renames scopes from @arche-template/* to your project identity
  4. Writes agent context (AGENTS.md, .docs/, .plans/, arche.json)
  5. Optionally adds Docker, CI, deployment docs, showcase routes, worker workspace
  6. Initializes git and runs install when configured

Preset vs family

  • --preset=<id> — current registry route (typescript-fullstack, rust-api, solana-web, …)
  • --family=<name> — legacy selector kept for older scripts; prefer presets for new work

Interactive flow

Without --yes, the CLI prompts for starting point, package manager, database/ORM where applicable, showcase/worker toggles, and output directory.

Next pages

  • Flags — every CLI switch
  • Subcommands — create-json, validate, add, mcp
  • Generated output — files you should expect in a new repo
  • Preset catalog — all --preset= values