mirror of
https://github.com/affaan-m/everything-claude-code.git
synced 2026-03-31 06:03:29 +08:00
* feat(commands): add /docs; feat(agents): add docs-lookup; feat(mcp-configs): document Context7; docs: add MCP subsection to CONTRIBUTING Made-with: Cursor * fix: address PR review — use Context7 MCP tool names in docs-lookup agent; CONTRIBUTING Agent Fields + MCP wording; mcp-config description; /docs quoted example; treat fetched docs as untrusted Made-with: Cursor * docs-lookup: note that harness may expose Context7 tools under prefixed names Made-with: Cursor * docs-lookup: examples use prefixed tool names (mcp__context7__*) for resolution Made-with: Cursor
1.4 KiB
1.4 KiB
description
| description |
|---|
| Look up current documentation for a library or topic via Context7. |
/docs
Purpose
Look up up-to-date documentation for a library, framework, or API and return a summarized answer with relevant code snippets. Uses the Context7 MCP (resolve-library-id and query-docs) so answers reflect current docs, not training data.
Usage
/docs [library name] [question]
Use quotes for multi-word arguments so they are parsed as a single token. Example: /docs "Next.js" "How do I configure middleware?"
If library or question is omitted, prompt the user for:
- The library or product name (e.g. Next.js, Prisma, Supabase).
- The specific question or task (e.g. "How do I set up middleware?", "Auth methods").
Workflow
- Resolve library ID — Call the Context7 tool
resolve-library-idwith the library name and the user's question to get a Context7-compatible library ID (e.g./vercel/next.js). - Query docs — Call
query-docswith that library ID and the user's question. - Summarize — Return a concise answer and include relevant code examples from the fetched documentation. Mention the library (and version if relevant).
Output
The user receives a short, accurate answer backed by current docs, plus any code snippets that help. If Context7 is not available, say so and answer from training data with a note that docs may be outdated.