Look up how Claude Code itself works — hooks, skills, subagents, MCP, plugins, settings — from the official docs, so answers come from the current spec instead of memory.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Answer questions about Claude Code from the official documentation, fetched at the moment you need it. Do not answer from memory: this product ships changes weekly, and a confidently wrong answer about a hook event or a manifest field costs more than a fetch.
Fetch the page that covers the question with WebFetch. Start from the overview only if
you need to find your way around; otherwise go straight to the relevant page.
| Topic | URL |
|---|---|
| Overview / index | https://code.claude.com/docs/en/overview |
| Skills | https://code.claude.com/docs/en/skills |
| Hooks — guide | https://code.claude.com/docs/en/hooks-guide |
| Hooks — full reference | https://code.claude.com/docs/en/hooks |
| Subagents | https://code.claude.com/docs/en/sub-agents |
| MCP | https://code.claude.com/docs/en/mcp |
| Plugins — guide | https://code.claude.com/docs/en/plugins |
| Plugins — reference | https://code.claude.com/docs/en/plugins-reference |
| Plugin marketplaces | https://code.claude.com/docs/en/plugin-marketplaces |
| Slash commands | https://code.claude.com/docs/en/slash-commands |
| Settings | https://code.claude.com/docs/en/settings |
| CLI reference | https://code.claude.com/docs/en/cli-reference |
If a URL 404s, the docs have been reorganised — fetch the overview and follow its navigation rather than guessing a new path.
Verify against the live CLI where you can. For anything about plugins, hooks or settings, the installed binary is a second source of truth and it cannot be out of date:
claude plugin validate <path> # what the schema actually accepts, warnings included
claude plugin --help # current subcommands
claude --help # flags
When the docs and the CLI disagree, trust the CLI and say so in your answer.
WebFetch needs network access. With none, say that you are answering from memory and
that the spec should be re-checked — do not present a remembered field list as current.
If you want a local copy for offline work, scripts/scrape_claude_code_docs.py in this
repo mirrors the docs into docs/claude-code/ for personal use. That mirror is
deliberately not committed or shipped: it is Anthropic's content, and a stale local copy
is exactly how wrong answers get confident.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Branch and commit conventions that keep an agent's work reviewable — one branch per task, main stays clean, nothing force-pushed.
The English summary is being prepared. Showing the original description.
Design better agents, skills and hooks for Claude Code, checking the current spec instead of guessing at fields.
The English summary is being prepared. Showing the original description.
Run a feature end to end — scout the code, plan it, build it, and keep a session file so a closed terminal doesn't lose the thread.
The English summary is being prepared. Showing the original description.
Close out a session — summarise what changed, capture what was learned, and prepare the commit.
The English summary is being prepared. Showing the original description.
Hand over a spec and walk away — plans, builds, tests and audits on its own, stopping only at a real blocker.
The English summary is being prepared. Showing the original description.
Run the project's own tests, linter, type checker and build, and report what actually failed.
The English summary is being prepared. Showing the original description.