ARCHE
FamiliesLive demoDocsExamplesBlogGitHub ↗
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

Scaffold lifecycle

How arche create copies, transforms, cleans up, and writes agent context—maintainer view.

1 min read

This page describes what happens inside apps/cli/src/lib/scaffold.ts when you run arche create. Generated users rarely need it; contributors and advanced automators do.

Pipeline

Loading diagram…

Key stages

StageWhat changes
CopyPolyglot or family stub from apps/cli/src/templates/
TransformsRust, Solana, Convex, ORM/database rewrites
CleanupCapability helpers strip live-demo paths and patch leaked wiring when flags omit --live-demo
Live demoOptional overlay from apps/cli/src/templates/addons/live-demo/ when --live-demo is set
Agent contextAGENTS.md, .docs/, .plans/, symlinks
Portfoliopackage.json#portfolio, optional SHOWCASE.mdx

Dogfood vs generated

This repo's apps/web marketing site and /live preview are not copied into the default fullstack template. Use --live-demo to ship Relay Run, chat, lattice, and guest auth in a generated project.

Flags that affect output

  • --no-showcase — skip demo surfaces and SHOWCASE.mdx
  • --live-demo — opt-in Relay Run / chat / lattice capability (separate from --showcase)
  • --no-worker — drop worker workspace and queue admin routes
  • --no-ci / --no-docker — skip those generators
  • --dry-run — plan only

Maintainer commands

Develop the CLI from this repo:

terminal
bun run dev:cli -- --help
bun test apps/cli
bun run template:sync:check
bun run repo:doctor:strict

template:sync:check enforces a minimal fullstack template and a self-contained live-demo addon. See This source repository and repo docs/cli-development.md.

On this page

  • Pipeline
  • Key stages
  • Flags that affect output
  • Maintainer commands