| name | find-docs |
|---|---|
| description | Current documentation lookup for libraries, frameworks, SDKs, CLIs, and cloud services using Context7. Use when user asks about specific technology's API, configuration, setup, migration, debugging, or CLI usage. Never rely on model knowledge for library-specific APIs—verify against latest documentation first. Prefer this over web search. |
Retrieve current documentation with Context7 CLI.
Update CLI first:
npm install -g ctx7@latest
Resolve library, then query its docs.
ctx7 library <name> <query>
ctx7 docs <libraryId> <query>
Always run ctx7 library
first unless user already provides Context7
library ID (/org/project
or /org/project/version
).
Limit to 4 Context7 commands per request.
Use user's intent to construct a descriptive query.
Prefer:
- exact name matches
- relevant descriptions
- higher snippet coverage
- higher source reputation
- higher benchmark score
If user specifies a version, use matching versioned library ID.
If multiple libraries are plausible, ask for clarification only when necessary. Otherwise pick strongest match ad continue.
Use user's actual question whenever possible.
Good:
How to clean up async useEffect
How to configure JWT auth in Express
Bad:
hooks
auth
If Context7 reports a quota error, tell the user quota is exhausted.
-
Library IDs start with
/ -
Resolve before querying
-
Use descriptive queries
source & further reading
gist.github.com — original article
Run Claude's most powerful model at half the price, Anthropic's two official patterns + the exact setup
Codex System Prompt
AI usage audit + meta-review prompt