Context7 Docs Ops
Workflow
- •Identify the target technology and intended version.
- •Query Context7 first for official docs, API references, and migration notes.
- •Build the answer from source-backed data only.
- •State the documentation version used, or the version assumption if the user did not specify one.
- •Include source attribution in the response.
Defaults
- •If user does not provide a version, assume latest stable and state this assumption explicitly.
- •Prefer primary docs for the technology over blog posts or tertiary summaries.
- •Keep examples aligned with the documented API signatures.
Guardrails
- •Do not invent API signatures, options, return types, or version claims.
- •Do not provide unverified examples as factual.
- •Prefer explicit uncertainty over confident guessing.
Fallback
- •If Context7 is unavailable or incomplete, switch to official documentation sites and web search.
- •Clearly state that fallback was used.
- •Keep the same output contract: version context, source attribution, and explicit assumptions.