Agent context (TypeScript routes with agent support)
terminal
AGENTS.md # Entry map — start here
CLAUDE.md -> AGENTS.md # Symlink when enabled
.docs/ # Internal topics (architecture, deploy, features)
.plans/ # Approved in-flight work (one active plan)
arche.json # Machine-readable scaffold metadataArche does not generate .cursor/rules/ or .claude/rules/ trees. Those duplicate context and drift quickly.
See Agent context for how agents should walk the map.
Workspace metadata
- Root
package.jsonwith workspaces and scripts - Bun
workspaces.catalogor pnpmcatalog:fromtoolings/catalog/workspace-catalog.json - Rendered root
turbo.json(not a static copy)—tasks match included apps - Per-app
package.jsonfiles with scoped names derived from your project name
Optional bundles
| Toggle | Output |
|---|---|
--docker | Dockerfiles / compose stubs for API and related services |
--ci | GitHub Actions workflows aligned with the preset |
--deployment | .docs/ deployment topics pointing at Vercel / Render / Railway patterns |
--showcase | Demo routes + SHOWCASE.mdx for portfolio sync |
--worker | apps/worker BullMQ workspace (requires Redis in env) |
Portfolio / showcase
With --showcase, fullstack presets may include:
SHOWCASE.mdx— frontmatter for kitsunekode.in syncpackage.json#portfolio— tags and featured flags
See docs/portfolio-sync.md in the template repository.
arche.json
Records the exact command and choices used to produce the tree—treat it as reproducibility metadata, not runtime config.