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

Agent context

Canonical AGENTS.md, .docs, .plans, and arche.json in generated projects.

1 min read

Arche generates a small map so coding agents load the right context without stuffing the entire repository into a prompt.

Agent context map
AGENTS.md
Entry map for every agent
CLAUDE.md
Symlink → AGENTS.md
.docs/
Internal architecture topics
.plans/active/
One approved in-flight plan
arche.json
Machine-readable scaffold metadata
Read root → nearest workspace AGENTS.md → one active plan

Canonical files

  • AGENTS.md — entry map; other agent files should point here.
  • CLAUDE.md — symlink to AGENTS.md when the preset enables it.
  • .docs/ — internal topics (architecture, deployment, features).
  • .plans/active/ — one approved in-flight plan at a time.
  • arche.json — machine-readable metadata about the scaffold.

What is not generated

Context budget

Arche does not generate duplicate rule trees or unverified production claims.

  • .cursor/rules/ or .claude/rules/ duplicate trees
  • Stale “production ready” claims without verification evidence

Agent workflow

Loading diagram…
  1. Read root AGENTS.md.
  2. Read the nearest workspace AGENTS.md for the package you touch.
  3. Load one matching .plans/active/ file only for approved work.

When commands or env names change, update the nearest AGENTS.md and the owning .docs/ topic.