md-docs

# Markdown Documentation Manage project documentation by verifying against actual codebase state. Emphasize verification over blind generation — analyze structure, files, and patterns before writing. ## Portability AGENTS.md is the universal context file (works with Claude Code, Codex, Kilocode). If the project uses CLAUDE.md, treat it as a symlink to AGENTS.md or migrate content into AGENTS.md and create the symlink: ```bash # If CLAUDE.md exists and AGENTS.md doesn't mv CLAUDE.md AGENTS.md && ln -sf AGENTS.md CLAUDE.md ``` When this skill references "context files", it means AGENTS.md (and CLAUDE.md if present as symlink). ## Workflows ### Update Context Files Verify and fix AGENTS.md against the actual codebase. See `references/update-agents.md` for the full verification workflow. 1. Read existing AGENTS.md, extract verifiable claims (paths, commands, structure, tooling) 2. Verify each claim against codebase (`ls`, `cat package.json`, `cat pyproject.toml`, etc.) 3. Fix discrepancies: outdated paths, wrong commands, missing sections, stale structure 4. Discover undocumented patterns (scripts, build tools, test frameworks not yet documented) 5. Report changes ### Update README Generate or refresh README.md from project metadata and structure. See `references/update-readme.md` for section templates and language-specific patterns. 1. Detect language/stack from config files (package.json, pyproject.toml, composer.json) 2. Extract metadata: name, version, description...