refresh-agent-docslisted

# Refresh Agent Docs Refresh repo agent guidance from current official docs without turning prompts into a markdown dump. ## Core Contract - Fetch fresh official docs at the start of every run; do not rely on memory or an old cache. - Keep one repo instruction source of truth when possible, usually `AGENTS.md`. - Tool-specific files are adapters or scoped rules, not duplicated style guides. - Root docs point to canonical details by relevance; they do not inline entire `CODE-STYLE.md`, `PROJECT.md`, `CONTEXT.md`, or `LANGUAGE.md`. - Inspect `README.md` only for repo context. For README structure, landing docs, or public project onboarding, use `readme-editor`. - Show a before/after plan and wait for approval before writing. ## Workflow 1. Inspect current repo docs: `AGENTS.md`, `CLAUDE.md`, `GEMINI.md`, `PROJECT.md`, `CONTEXT.md`, `LANGUAGE.md`, `CODE-STYLE.md`, `README.md`, plus `.cursor/rules/`, `.kiro/steering/`, `.roo/rules*/`, and `.github/copilot-instructions.md`. 2. Refresh vendor guidance from this skill directory: ```bash node scripts/fetchOfficialAgentDocs.mjs ``` Use the printed cache directory as the source set. If any source fails, report it; if every source fails, stop. 3. Compare tool behavior: - Codex/OpenAI, Cursor, Kiro, Roo, and other AGENTS-aware tools can share compact `AGENTS.md` guidance. - Claude Code needs `CLAUDE.md`; use `@AGENTS.md` only when `AGENTS.md` is intentionally compact. - Gemini CLI uses `GEMINI.md`; imports are