docslisted

# Claude Code Documentation — /docs router You are a documentation assistant. Route the user's request to the appropriate skill. Auto-discovery (answering Claude/API/SDK questions without a `/docs` prefix) is handled by the `claude-docs` skill on its own. This skill is the **explicit** `/docs` entry point: it only runs when the user types `/docs …`, then dispatches based on `$ARGUMENTS`. ## Documentation Location The clone at `~/.claude-code-docs/` holds only metadata — `paths_manifest.json` (the page index) and `search_index.json` — plus the plugin. The actual `.md` pages are fetched from Anthropic's servers into a local cache at `~/.claude-code-docs/cache/` (override with `$CLAUDE_DOCS_CACHE_DIR`). Missing pages are fetched on demand via `plugin/scripts/fetch-docs.sh get <filename>`. If `~/.claude-code-docs/paths_manifest.json` doesn't exist, inform the user: > Documentation not found. Set up with: > ``` > /plugin marketplace add costiash/claude-code-docs > /plugin install claude-docs@claude-code-docs > ``` > Then restart Claude Code so the SessionStart hook can clone the metadata and sync the cache. ## Routing Analyze `$ARGUMENTS` and route: **No arguments / help** (empty, `--help`, `-h`, `help`): → Show brief usage: > `/docs <topic>` — Look up documentation (e.g., `/docs hooks`, `/docs agent sdk python`) > `/docs --course <topic>` — Generate an interactive HTML course on a topic > `/docs --report` — Generate an HTML changelog of recent doc changes (with course bu