dotagents-standardlisted

# dotagents ## What this is **dotagents** turns a project's agent context from one big file into a **router + a library**. - The **router** is a slim `AGENTS.md` at the repo root. It is *always* read. It describes the agent's identity and, crucially, tells the agent **where to look** for deeper context — but only when a task actually needs it. - The **library** is a hidden `.agents/` directory holding the "heavy" context, split into small, single-purpose files organized by *kind* (behavioral rules vs. static reference vs. durable memory vs. task specs, etc.). The whole point is **progressive disclosure**: load a screenful of routing rules up front, then pull in only the specific files the current task matches. A monolithic `AGENTS.md`/`CLAUDE.md` forces the agent to read a database schema while editing CSS, mixes "never use `any`" (a rule) with "we chose Postgres in 2023" (a memory), and invites a clutter of vendor folders (`.claude/`, `.cursor/`, `.gemini/`) in the root. dotagents fixes all three by *separating by kind* and *loading conditionally*. **The value lives entirely in that discipline.** If you dump everything into `AGENTS.md`, you've gained nothing. If you scatter files but the router never points to them, agents won't find them. Both halves — a *tight router* and *well-factored files* — must hold. ## Two related specs share the "`.agents`" name Be aware there are two overlapping standards; know which one the user means: 1. **dotagents** (github.com