askit-build-agents-mdlisted

# askit-build-agents-md ## Purpose Author and keep current a plugin's `AGENTS.md`: the project-level agent instructions and navigation entrypoint, the first thing an agent reads (Standard sec 3.10). It is the single most portable cross-tool surface (Claude, Codex, Gemini, Copilot, and Cursor all read `AGENTS.md`). Two modes: `create` authors a tight AGENTS.md; `improve` syncs it to the component index and trims it. Authoring depth is in [references/authoring-agents-md.md](references/authoring-agents-md.md). Follows the shared builder contract ([../../docs/reference/builder-pattern.md](../../docs/reference/builder-pattern.md)). ## When to use When the user asks to author, write, sync, or trim `AGENTS.md` (or `CLAUDE.md`), or when components were added or removed and the navigation is stale. ## create mode 1. Brief interview: what the project is, the conventions (runtime, build/test/lint), and the boundaries. Skip if in context. 2. Author a TIGHT AGENTS.md: what-this-is, current-state (read before assuming capabilities), conventions, build/test/lint, where-to-look. Keep it minimal and essential-only, and prefer positive instructions over long "do not" lists. Verbose, generated-looking context files measurably reduce agent task success and raise cost, so brevity is a feature, not a shortcut. 3. Keep the component list aligned with `library.json` and the index. `node scripts/generators/sync-agents-md.mjs` renders the component section from the manifest so it does not drift. 4.