scoped-agentslisted

# scoped-agents Create a folder-scoped `AGENTS.md` and register it in the repo-root `AGENTS.md`, following the layering rules below. Use it to add new scoped rules, or to split an overgrown root `AGENTS.md` into per-folder files. ## Load-bearing rules (do not violate) - **`AGENTS.md` is the source of truth** — harness-agnostic, carries the real rules. `CLAUDE.md` is a THIN layer that `@AGENTS.md`-imports and adds only Claude-specific notes. Never invert this. If a repo has a fat `CLAUDE.md` and no `AGENTS.md`, fix that first (move the rules into `AGENTS.md`, reduce `CLAUDE.md` to the import + Claude-only notes). - **Scoped files never duplicate the root or the global rules.** A folder `AGENTS.md` holds only what is specific to that folder. Repo-wide rules stay at the root; cross-repo operator rules stay in the global `~/.config/AGENTS.md`. - **More-specific wins.** Precedence: direct chat > memory > deeper scoped (`a/b/AGENTS.md`) > shallower scoped (`a/AGENTS.md`) > root > global. ## Steps 1. **Confirm the pattern.** Repo root has `AGENTS.md`; if Claude Code is used, `CLAUDE.md` is thin and imports it (`@AGENTS.md`). Establish that before scoping. 2. **Create `<folder>/AGENTS.md`** from the template below — only rules that truly belong to that folder. If those rules currently live in the root, MOVE them (don't leave a duplicate). 3. **Register it** in the root `AGENTS.md` under `## Scoped AGENTS.md` (create the section + table if missing). One