understanding-code-context

To find authoritative versioned documentation for external libraries, resolve the library ID and retrieve official docs using Context7. This Skill applies multiple search variations like exact package or org/repo names before falling back to web search for unindexed libraries.

Analyzing dependencies and learning API patterns during onboarding is best done by retrieving version-specific official documentation. This approach ensures you review accurate configuration options and best practices instead of guessing library intent from source code.

Resolving a Context7 library ID when documentation lookups fail requires trying multiple search variations including exact package, framework plus concept, org/repo, and base name. If the library is not indexed, implement a fallback strategy to web search.

Context7 does not support retrieving official docs for every framework or library. It requires the library to be indexed within its system, necessitating a web search fallback strategy for unindexed packages and connection checks for troubleshooting.

Using Context7 for configuration review instead of standard web search removes uncertainty by guiding you to authoritative, version-specific documentation. This ensures you apply correct API patterns and recommended setup options for your specific library version.

Limitations of relying on Context7 for versioned library documentation include connectivity requirements and the dependency on library indexing. If a library is not indexed, the system must fall back to web search, which may not provide version-specific accuracy.