claude-code-docs
Claude Code Docs
Local search over the official Claude Code documentation. All ~74 English doc pages from code.claude.com/docs are stored as individual markdown files with descriptive filenames.
How to search
The docs live in a local directory. Find it by checking common locations:
# Check if there's a known docs path
ls ~/github/*/claude-docs/claude-code/docs/*.md 2>/dev/null || ls ~/.claude/claude-code-docs/docs/*.md 2>/dev/null
Search strategy
- Start with Grep using 2-3 keywords from the user's question across all
*.mdfiles in the docs directory. This quickly identifies which docs are relevant. - Read the most relevant doc in full using Read. The real answer lives in the full document — grep snippets alone are not enough context.
- Check related docs when the question spans multiple features. Many Claude Code features have both a CLI flag and an in-session command (e.g.,
--add-dirand/add-dir,--worktreeand/branch). If your answer involves a Desktop feature, also check if there's a CLI equivalent, and vice versa. A second grep with different keywords often surfaces the complementary doc. - Stop searching once you have the answer. Two or three doc reads should be enough for most questions. Don't keep searching for confirmation — synthesize what you found and respond.
More from s0up4200/skills
mobile-adapt
Use when a user wants a site, app, screen, flow, dashboard, or full project adapted for phones or mobile web, or mentions responsive/mobile-first/iPhone/iOS Safari/touch/safe-area/landscape/keyboard issues. Also use for mobile audits, mobile regressions, small-screen layout fixes, bottom navigation redesigns, form/table/chart adaptation, or iPhone-specific usability work.
12release-tag
Create and push a signed git release tag. Use this skill when the user says "tag a release", "new release", "cut a release", "bump version", "release tag", "tag version", "push a tag", or any variation of wanting to create a new version tag. Also use when the user types "/release-tag" or "/release".
6retro
>-
3platform-docs
Search and reference official Anthropic platform documentation locally. Use whenever the user asks about the Claude API, Anthropic SDKs (Python, TypeScript), REST API endpoints, models, pricing, tool use, computer use, MCP server protocol, prompt engineering, extended thinking, prompt caching, vision, batch processing, Agent SDK, embeddings, streaming, structured outputs, citations, context windows, token counting, files API, PDF support, multilingual support, model deprecations, rate limits, error codes, or any other Anthropic platform capability. Also use when you need to look up API details yourself mid-task — checking request/response schemas, SDK method signatures, authentication, or endpoint parameters. Prefer this over web fetching for Anthropic API and platform docs. NOT for Claude Code (the CLI tool) — use claude-code-docs for that.
2libtorrent
Answer questions about the libtorrent C++ BitTorrent library using a local scraped mirror of libtorrent.org docs and blog posts. Use this skill whenever the user asks about libtorrent settings, APIs, performance tuning, building libtorrent, the piece picker, DHT, BitTorrent v2, alerts, torrent_handle, session configuration, or any other libtorrent-specific topic. Also trigger when the user mentions libtorrent by name, references libtorrent classes like session, torrent_handle, settings_pack, or asks about BitTorrent implementation details that libtorrent covers. Invoke via /libtorrent or automatically when the context matches.
1emotional-awareness
>-
1