Claude Docs Consultant
Fetch official Claude Code documentation on-demand from code.claude.com. Uses progressive disclosure: resolve the topic to a filename, then fetch only that doc. Never fetch documentation speculatively.
URL Pattern
All docs follow this pattern — substitute the filename:
https://code.claude.com/docs/en/{filename}.md
Quick Routing (Common Topics)
For these high-frequency topics, fetch directly without consulting the full index:
| Topic |
Filename(s) to fetch |
| Hooks (creating, events, lifecycle) |
hooks-guide.md (guide + examples), hooks.md (API reference + all events) |
| Skills (creating, SKILL.md format, triggers) |
skills.md |
| Subagents (types, config, delegation) |
sub-agents.md |
| Agent Teams (multi-agent, teammates, cowork) |
agent-teams.md |
| Plugins (creating, marketplace, installing) |
plugins.md (creating), discover-plugins.md (marketplace + installing) |
| MCP Servers (setup, config, scopes) |
mcp.md |
| Settings (settings.json, config scopes) |
settings.md |
| Permissions (rules, modes, auto mode) |
permissions.md (rules + syntax), permission-modes.md (plan/auto/dontAsk modes) |
| Memory (CLAUDE.md, auto memory, rules) |
memory.md |
| GitHub Actions (CI/CD, @claude PR) |
github-actions.md |
Full Routing
For topics not listed above, consult references/docs-index.md for the complete routing table covering all 60+ documentation pages across platforms, deployment, security, configuration, administration, and reference.
Workflow
- Identify topic — determine which Claude Code feature the task involves
- Route to filename — use quick routing above, or consult
references/docs-index.md
- Fetch with WebFetch — use the URL pattern with the resolved filename
Fetch multiple docs in parallel when the task spans multiple topics.
Fallback: Discovery via Docs Map
If routing does not match any known filename, fetch the documentation map to discover available pages:
https://code.claude.com/docs/en/claude_code_docs_map.md
Identify the relevant doc from the map, then fetch it using the URL pattern.
Rules
- Fetch only the docs actually needed for the current task
- Fetch multiple docs in parallel if the task requires 2+ sources
- Always fetch live from code.claude.com — do not use cached or memorized content
- Do not fetch docs "just in case" — fetch when required by the task
Examples
Example 1: Creating a Hook
Task: "Help me create a pre-tool-use hook to log tool calls"
- Route: hook creation ->
hooks-guide.md + hooks.md
- Fetch both in parallel via WebFetch
- Apply: create hook using guide examples and API reference for PreToolUse event
Example 2: Installing a Plugin
Task: "How do I install plugins from a marketplace?"
- Route: plugin installing ->
discover-plugins.md
- Fetch via WebFetch
- Apply: follow marketplace and installation instructions
Example 3: Unknown Feature
Task: "How do I configure Claude Code output styles?"
- Route: not in quick routing table
- Consult
references/docs-index.md -> find output-styles.md under Configuration
- Fetch
output-styles.md via WebFetch
- Apply: configure output styles per documentation
Source: centminmod/my-claude-code-setup — distributed by TomeVault.
1---2name: claude-docs-consultant3description: Consult official Claude Code documentation from code.claude.com using selective fetching. Use when working on hooks, skills, subagents, plugins, agent teams, MCP servers, permissions, settings, CI/CD (GitHub Actions, GitLab), IDE extensions (VS Code, JetBrains), desktop/web app features, scheduling, memory/CLAUDE.md, deployment (Bedrock, Vertex, Foundry), sandboxing, monitoring, or any Claude Code feature requiring official docs. Fetches only the specific docs needed per task. Use when this capability is needed.4---56# Claude Docs Consultant78Fetch official Claude Code documentation on-demand from code.claude.com. Uses progressive disclosure: resolve the topic to a filename, then fetch only that doc. Never fetch documentation speculatively.910## URL Pattern1112All docs follow this pattern — substitute the filename:1314```15https://code.claude.com/docs/en/{filename}.md16```1718## Quick Routing (Common Topics)1920For these high-frequency topics, fetch directly without consulting the full index:2122| Topic | Filename(s) to fetch |23| --- | --- |24| Hooks (creating, events, lifecycle) | `hooks-guide.md` (guide + examples), `hooks.md` (API reference + all events) |25| Skills (creating, SKILL.md format, triggers) | `skills.md` |26| Subagents (types, config, delegation) | `sub-agents.md` |27| Agent Teams (multi-agent, teammates, cowork) | `agent-teams.md` |28| Plugins (creating, marketplace, installing) | `plugins.md` (creating), `discover-plugins.md` (marketplace + installing) |29| MCP Servers (setup, config, scopes) | `mcp.md` |30| Settings (settings.json, config scopes) | `settings.md` |31| Permissions (rules, modes, auto mode) | `permissions.md` (rules + syntax), `permission-modes.md` (plan/auto/dontAsk modes) |32| Memory (CLAUDE.md, auto memory, rules) | `memory.md` |33| GitHub Actions (CI/CD, @claude PR) | `github-actions.md` |3435## Full Routing3637For topics not listed above, consult `references/docs-index.md` for the complete routing table covering all 60+ documentation pages across platforms, deployment, security, configuration, administration, and reference.3839## Workflow40411. **Identify topic** — determine which Claude Code feature the task involves422. **Route to filename** — use quick routing above, or consult `references/docs-index.md`433. **Fetch with WebFetch** — use the URL pattern with the resolved filename4445Fetch multiple docs in parallel when the task spans multiple topics.4647## Fallback: Discovery via Docs Map4849If routing does not match any known filename, fetch the documentation map to discover available pages:5051```52https://code.claude.com/docs/en/claude_code_docs_map.md53```5455Identify the relevant doc from the map, then fetch it using the URL pattern.5657## Rules5859- Fetch only the docs actually needed for the current task60- Fetch multiple docs in parallel if the task requires 2+ sources61- Always fetch live from code.claude.com — do not use cached or memorized content62- Do not fetch docs "just in case" — fetch when required by the task6364## Examples6566### Example 1: Creating a Hook6768**Task:** "Help me create a pre-tool-use hook to log tool calls"69701. Route: hook creation -> `hooks-guide.md` + `hooks.md`712. Fetch both in parallel via WebFetch723. Apply: create hook using guide examples and API reference for PreToolUse event7374### Example 2: Installing a Plugin7576**Task:** "How do I install plugins from a marketplace?"77781. Route: plugin installing -> `discover-plugins.md`792. Fetch via WebFetch803. Apply: follow marketplace and installation instructions8182### Example 3: Unknown Feature8384**Task:** "How do I configure Claude Code output styles?"85861. Route: not in quick routing table872. Consult `references/docs-index.md` -> find `output-styles.md` under Configuration883. Fetch `output-styles.md` via WebFetch894. Apply: configure output styles per documentation9091---92> Source: [centminmod/my-claude-code-setup](https://github.com/centminmod/my-claude-code-setup) — distributed by [TomeVault](https://tomevault.io).93<!-- tomevault:4.0:skill_md:2026-06-27 -->
tomevault-io