Automation walkthrough

Goal: Scaffold or validate projects without interactive prompts—same registry rules as arche create.

create-json

bun run dev:cli -- create-json '{
  "projectName": "my-app",
  "destinationDir": "/tmp/my-app",
  "preset": "typescript-fullstack",
  "packageManager": "bun",
  "initializeGit": false,
  "installDependencies": false
}'

Add --dry-run to preview transforms without writing.

validate

bun run dev:cli -- validate '{"projectName":"my-app","preset":"typescript-fullstack","database":"postgres","orm":"prisma"}'

Exit non-zero on incompatible options—use in agent tool loops before create-json.

MCP server

bun run dev:cli -- mcp

Tools expose schema and guidance from the same CLI sources—no parallel capability story.

add repairs

bun run dev:cli -- add agent-docs ./my-app
bun run dev:cli -- add docker ./my-app
bun run dev:cli -- add ci ./my-app

Use when an existing tree drifted from Arche conventions.

History and completions

bun run dev:cli -- history
bun run dev:cli -- completion zsh >> ~/.zshrc

CI pattern

1. validate JSON config in PR
2. create-json into a temp dir on main merges (optional)
3. Run generated bun run ci in the target repo

See CI & testing.