context7-usage

name	context7-usage
description	Context7 MCP documentation retrieval patterns for up-to-date library and API references.
version	1.0.0

Provide consistent usage patterns for Context7 MCP so prompts can retrieve current documentation and avoid stale API assumptions. Resolve library identifiers before documentation retrieval Fetch focused documentation for specific topics and versions Always resolve library id first, then fetch docs with a focused topic. Resolve library id for the target package, then fetch docs for routing/hooks/config relevant to the task. When behavior differs by version, request docs for the exact version or clearly specify baseline assumptions. Use a versioned library id when available and compare migration notes before updating prompts.

<decision_tree name="context7_usage"> Do you need current library/framework API behavior? Use Context7 resolve and fetch flow before making claims Use local codebase evidence first </decision_tree>

<related_agents> Use for local codebase context before external doc lookup Use for synthesis when multiple doc sources conflict </related_agents>

<related_skills> Use with external verification workflows Use with project-local evidence gathering </related_skills>

Keep guidance evidence-based and version-aware Prefer project conventions over generic defaults

<best_practices> Apply this skill only when domain fit is clear </best_practices>

<error_escalation> Minor inconsistencyDocument and continue Ambiguous guidanceClarify assumptions Conflicting constraintsEscalate with options Unsafe or misleading retrieval guidanceBlock and escalate to maintainers with corrective steps </error_escalation>

Prefer official or primary documentation sources State uncertainty when docs are unavailable or ambiguous Relying on stale memory of API signatures without retrieval