claude-docs-consultant
Claude Docs Consultant retrieves official Claude Code documentation on-demand from code.claude.com, resolving topics to specific filenames before fetching. Use this skill when implementing hooks, skills, subagents, plugins, agent teams, MCP servers, permissions, settings, CI/CD pipelines, IDE extensions, deployment options, sandboxing, monitoring, memory configuration, or other Claude Code features that require authoritative reference documentation. The skill fetches only the specific docs needed per task and never retrieves documentation speculatively.
git clone --depth 1 https://github.com/centminmod/my-claude-code-setup /tmp/claude-docs-consultant && cp -r /tmp/claude-docs-consultant/.claude/skills/claude-docs-consultant ~/.claude/skills/claude-docs-consultantSKILL.md
# 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
1. **Identify topic** — determine which Claude Code feature the task involves
2. **Route to filename** — use quick routing above, or consult `references/docs-index.md`
3. **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"
1. Route: hook creation -> `hooks-guide.md` + `hooks.md`
2. Fetch both in parallel via WebFetch
3. 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?"
1. Route: plugin installing -> `discover-plugins.md`
2. Fetch via WebFetch
3. Apply: follow marketplace and installation instructions
### Example 3: Unknown Feature
**Task:** "How do I configure Claude Code output styles?"
1. Route: not in quick routing table
2. Consult `references/docs-index.md` -> find `output-styles.md` under Configuration
3. Fetch `output-styles.md` via WebFetch
4. Apply: configure output styles per documentationUse this agent for comprehensive codebase analysis, forensic examination, and detailed code mapping with optional Chain of Draft (CoD) methodology. Excels at locating specific functions, classes, and logic, security vulnerability analysis, pattern detection, architectural consistency verification, and creating navigable code reference documentation with exact line numbers. Examples: <example>Context: User needs to find authentication-related code in the project. user: "Where is the user authentication logic implemented?" assistant: "I'll use the code-searcher agent to locate authentication-related code in the codebase" <commentary>Since the user is asking about locating specific code, use the code-searcher agent to efficiently find and summarize authentication logic.</commentary></example> <example>Context: User wants to understand how a specific feature is implemented. user: "How does the license validation work in this system?" assistant: "Let me use the code-searcher agent to find and analyze the license validation implementation" <commentary>The user is asking about understanding specific functionality, so use the code-searcher agent to locate and summarize the relevant code.</commentary></example> <example>Context: User needs to find where a bug might be occurring. user: "I'm getting an error with the payment processing, can you help me find where that code is?" assistant: "I'll use the code-searcher agent to locate the payment processing code and identify potential issues" <commentary>Since the user needs to locate specific code related to an error, use the code-searcher agent to find and analyze the relevant files.</commentary></example> <example>Context: User requests comprehensive security analysis using Chain of Draft methodology. user: "Analyze the entire authentication system using CoD methodology for comprehensive security mapping" assistant: "I'll use the code-searcher agent with Chain of Draft mode for ultra-concise security analysis" <commentary>The user explicitly requests CoD methodology for comprehensive analysis, so use the code-searcher agent's Chain of Draft mode for efficient token usage.</commentary></example> <example>Context: User wants rapid codebase pattern analysis. user: "Use CoD to examine error handling patterns across the codebase" assistant: "I'll use the code-searcher agent in Chain of Draft mode to rapidly analyze error handling patterns" <commentary>Chain of Draft mode is ideal for rapid pattern analysis across large codebases with minimal token usage.</commentary></example>
Execute OpenAI Codex CLI (GPT-5.2) for code analysis. Use when you need Codex's GPT-5.2 perspective on code.
Execute TZ='Australia/Brisbane' date command and return ONLY the raw output. No formatting, headers, explanations, or parallel agents.
Use this agent proactively to synchronize memory bank documentation with actual codebase state, ensuring architectural patterns in memory files match implementation reality, updating technical decisions to reflect current code, aligning documentation with actual patterns, maintaining consistency between memory bank system and source code, and keeping all CLAUDE-*.md files accurately reflecting the current system state. Examples: <example>Context: Code has evolved beyond documentation. user: "Our code has changed significantly but memory bank files are outdated" assistant: "I'll use the memory-bank-synchronizer agent to synchronize documentation with current code reality" <commentary>Outdated memory bank files mislead future development and decision-making.</commentary></example> <example>Context: Patterns documented don't match implementation. user: "The patterns in CLAUDE-patterns.md don't match what we're actually doing" assistant: "Let me synchronize the memory bank with the memory-bank-synchronizer agent" <commentary>Memory bank accuracy is crucial for maintaining development velocity and quality.</commentary></example>
Use this agent when you need comprehensive UX/UI design guidance, including user experience optimization, premium interface design, scalable design systems, data visualization with Highcharts, or Tailwind CSS implementation. Examples: <example>Context: User is building a dashboard with complex data visualizations and wants to improve the user experience. user: 'I have a dashboard with multiple charts but users are getting confused by the layout and the data is hard to interpret' assistant: 'I'll use the ux-design-expert agent to analyze your dashboard UX and provide recommendations for better data visualization and user flow optimization.'</example> <example>Context: User wants to create a premium-looking component library for their product. user: 'We need to build a design system that looks professional and scales across our product suite' assistant: 'Let me engage the ux-design-expert agent to help design a scalable component library with premium aesthetics using Tailwind CSS.'</example> <example>Context: User is struggling with a complex multi-step user flow. user: 'Our checkout process has too many steps and users are dropping off' assistant: 'I'll use the ux-design-expert agent to streamline your checkout flow and reduce friction points.'</example>
Execute z.ai GLM 4.7 model via Claude Code CLI. Use when you need z.ai's GLM 4.7 perspective on code analysis.
Generate PNG images using AI (multiple models via OpenRouter including Gemini, FLUX.2, Riverflow, SeedDream, GPT-5 Image, GPT-5.4 Image 2, proxied through Cloudflare AI Gateway BYOK). Also analyze/describe existing images using multimodal AI vision. Use when user asks to "generate an image", "create a PNG", "make an icon", "make it transparent", "describe this image", "analyze this image", "what's in this image", "explain this image", or needs AI-generated visual assets for the project. Supports model selection via keywords (gemini, riverflow, flux2, seedream, gpt5, gpt5.4), configurable aspect ratios/resolutions, transparent backgrounds (-t), reference image editing (-r), image analysis (--analyze), and per-project cost tracking (--costs).
>