agent-guidance-factorylisted

# Agent Guidance Factory Create source-controlled instructions that coding agents actually load and can follow. These files guide behavior; they do not replace linters, hooks, tests, permissions, or other enforcement. Read `references/agent-guidance-files.md` before creating, migrating, or materially changing `AGENTS.md`, `CLAUDE.md`, `.claude/rules/`, or `.cursor/rules/`. ## Route 1. Identify the target agents and existing surfaces. Prefer portable `AGENTS.md` for shared repository guidance. Use `CLAUDE.md` only for Claude Code-specific behavior, and Cursor rules when structured metadata, glob attachment, or Team/User/Project rule behavior is required. 2. Choose scope deliberately: root for every task in the repo, nested files for subtrees with different commands or constraints, and override files only when the target agent documents that override behavior. 3. Inspect the repo before writing: root layout, build/test/lint scripts, CI, docs, config, existing guidance files, PR templates, and recent commit messages. Verify commands from source files rather than inventing them. 4. Write concise, directive Markdown. Include only durable facts and workflows that matter in most relevant sessions: layout, exact commands, coding conventions, test expectations, security/configuration boundaries, review expectations, and completion proof. 5. Keep hot guidance small. Include repo evidence only when it changes an agent action, boundary, command, style