Find the primary source
Every family below links the official documentation site. Blogs and answers age; the vendor's docs, changelog and repository are maintained alongside the release. When two sites disagree, the primary source wins.
Developer Docs
Official Library Docs: a Navigator Across 42 Families.
Every family below answers four questions: what the official docs cover, which tasks they fit, which they do not, and the version caveat to carry into any AI-assisted answer. Scan the group, open the chunk, follow the primary source — then hand your assistant the exact version and the exact excerpt, not a guess.
42 families · 7 groups · an official link in every chunkThe primary source beats the retelling — every chunk links the official docs
The method: from primary source to checkable answer
Pin the version you actually run
Read your lockfile, not your memory. Most documentation sites carry a version switcher — set it to your installed major before reading, because the default view usually documents the latest release, not yours.
Check deprecations before you build
Search the docs for the API you are about to use plus the words deprecated and removed, and skim the migration guide for your major. Ten minutes here is cheaper than discovering the removal in a failing build.
Know which document you are reading
Tutorials teach the happy path, reference pages define the contract, changelogs tell you what moved between versions. A tutorial answer to a reference question is how subtle bugs get shipped — match the document type to the question.
Hand the context to your AI assistant
State the library and exact version, then paste the relevant doc excerpt with your question. An assistant reasoning over the current reference beats one recalling a training snapshot — and its answer becomes checkable against the excerpt you gave it.
Frameworks & rendering09
Next.jsRouting (App and Pages Router), rendering modes, data fetching, caching, middleware and deployment.
Fits: Choosing a rendering strategy, App Router migrations, caching and revalidation questions.
Not for: Your application's business logic, or hosting questions specific to a non-Vercel platform.
Version caveat: The App/Pages Router split means answers differ by both major version and router — state which one you run.
Context7 id /vercel/next.js · official documentation
ReactComponents, hooks, effects, Server Components, and the current-generation API reference.
Fits: Hook semantics, effect lifecycle questions, Server vs Client Component boundaries.
Not for: Framework-level routing or data fetching — that lives in Next.js, React Router or TanStack docs.
Version caveat: React 18→19 changed defaults and deprecations; hooks-era answers do not transfer to class-era code.
Context7 id /reactjs/react.dev · official documentation
React RouterClient and framework-mode routing, loaders and actions, and the merged Remix feature set.
Fits: Route configuration, loader/action data flow, migration from Remix or older router majors.
Not for: Server rendering strategy outside the router's framework mode.
Version caveat: Major versions changed the API surface repeatedly, and v7 absorbed Remix — version-pin every answer.
Context7 id /remix-run/react-router · official documentation
TanStack RouterType-safe routing, search-param APIs, loaders and file-based route generation.
Fits: Fully typed route trees, search-param state, framework-agnostic SPA routing.
Not for: Server-first rendering frameworks — its center of gravity is the typed client router.
Version caveat: Moves quickly and leans on codegen; match the docs to your exact minor version.
Context7 id /tanstack/router · official documentation
AstroIslands architecture, content collections, integrations and static/SSR output modes.
Fits: Content-heavy sites, mixing UI frameworks per-island, content collection schemas.
Not for: Highly interactive app shells where a single-framework SPA/SSR stack fits better.
Version caveat: Integration APIs and content collections shifted across majors — check which major the answer assumes.
Context7 id /withastro/docs · official documentation
ViteDev server, build pipeline, plugin API and environment/library modes.
Fits: Build configuration, plugin authoring, migrating bundlers, dev-server behavior.
Not for: Framework-specific conventions layered on top by Next.js, Astro or SvelteKit.
Version caveat: Plugin hooks and defaults move between majors; pin the major before trusting a config snippet.
Context7 id /vitejs/vite · official documentation
ExpoReact Native app workflow: SDK modules, EAS build/submit/update, routing and native config plugins.
Fits: Mobile builds without native toolchain ownership, OTA updates, store submission flow.
Not for: Deep custom native modules beyond what config plugins and prebuild cover.
Version caveat: SDK versions ship on a fast cadence and pin React Native versions — answers are SDK-version-specific.
Context7 id /expo/expo · official documentation
TauriDesktop and mobile shells for web frontends with a Rust core: windows, IPC, permissions, bundling.
Fits: Small-footprint desktop apps from an existing web UI, native capability via commands.
Not for: Teams unwilling to touch the Rust side once IPC or plugins get non-trivial.
Version caveat: v1 and v2 differ substantially (mobile targets, permission model) — the docs id here is the v2 site.
Context7 id /websites/v2_tauri_app · official documentation
SwiftUIApple's declarative UI framework across iOS, iPadOS, macOS, watchOS and visionOS.
Fits: View composition, state propagation, platform-adaptive layouts in the Apple ecosystem.
Not for: Cross-platform delivery — this is the native Apple stack by definition.
Version caveat: APIs are gated by OS version, not library version — state your deployment target in every question.
Context7 id /websites/developer_apple_swiftui · official documentation
Paste the code and the doc excerpt into the AI Coding Assistant
UI, state & validation04
shadcn/uiCopy-in component recipes over Radix primitives and Tailwind, plus the CLI and registry format.
Fits: Owning component code instead of a dependency, theming via CSS variables, registry-driven setups.
Not for: A classic versioned component library — you vendor the code and maintain it after copying.
Version caveat: Recipes track Tailwind and Radix versions; a component copied last year drifts from today's registry.
Context7 id /shadcn-ui/ui · official documentation
Tailwind CSSUtility classes, theme tokens, responsive/variant syntax and build integration.
Fits: Utility lookups, theme customization, migrating config between majors.
Not for: Component semantics or accessibility patterns — utilities style, they do not structure.
Version caveat: v4 moved configuration into CSS and changed defaults — v3 answers often do not apply.
Context7 id /tailwindlabs/tailwindcss.com · official documentation
TanStack QueryServer-state caching: queries, mutations, invalidation, prefetching and hydration.
Fits: Cache lifetimes, invalidation strategy, optimistic updates, SSR hydration questions.
Not for: Client-only UI state — that belongs to component state or a state library.
Version caveat: Key APIs were renamed across majors (v4→v5 especially); match the docs major to your lockfile.
Context7 id /tanstack/query · official documentation
ZodSchema declaration, parsing and inference for TypeScript-first runtime validation.
Fits: Validating external input at boundaries, deriving static types from one schema source.
Not for: Heavy data transformation pipelines — it validates and coerces, it is not an ETL tool.
Version caveat: Error-shape and API details changed between majors; check which major your codebase pins.
Context7 id /colinhacks/zod · official documentation
Paste the code and the doc excerpt into the AI Coding Assistant
Backend, data & runtimes09
SupabasePostgres hosting with auth, row-level security, storage, realtime and edge functions.
Fits: RLS policy design, auth flows, client/server key boundaries, Postgres-first backends.
Not for: Non-Postgres data models, or fully custom auth stacks living outside its primitives.
Version caveat: Client libraries and key formats have shifted generations — verify which API-key era an answer assumes.
Context7 id /supabase/supabase · official documentation
FastAPIPython APIs from type hints: routing, dependency injection, validation and OpenAPI generation.
Fits: Typed request/response modeling, auto-documented APIs, async Python services.
Not for: Long-running background processing — pair it with a worker/queue system instead.
Version caveat: Its validation layer follows Pydantic's major versions — the Pydantic v1/v2 split is the usual trap.
Context7 id /fastapi/fastapi · official documentation
NestJSOpinionated Node server architecture: modules, providers, guards, pipes and microservice transports.
Fits: Large TypeScript backends wanting DI and structure, gRPC/queue transports, testing seams.
Not for: Small single-file services where the framework's ceremony outweighs its structure.
Version caveat: Decorator and DI semantics track TypeScript compiler settings; align docs, major and tsconfig.
Context7 id /nestjs/docs.nestjs.com · official documentation
Spring BootJVM service framework: auto-configuration, starters, actuator, security and data access.
Fits: Enterprise Java/Kotlin services, configuration-property questions, actuator observability.
Not for: Lightweight functions or scripts — the platform assumes a long-lived service.
Version caveat: Boot 2→3 moved to Jakarta namespaces and newer JVM baselines — answers split hard on that boundary.
Context7 id /spring-projects/spring-boot · official documentation
MongoDBDocument data modeling, query and aggregation language, indexes, drivers and Atlas operations.
Fits: Aggregation pipeline construction, index strategy, driver API questions.
Not for: Relational modeling with heavy cross-entity joins and constraints — that is a relational database's job.
Version caveat: Server, driver and Atlas each version separately — name all three when asking anything precise.
Context7 id /mongodb/docs · official documentation
PrismaSchema-first ORM: migrations, typed client queries, relation modeling and connection handling.
Fits: Schema evolution with migrations, typed query construction, relation loading strategy.
Not for: Hand-tuned SQL-first codebases — raw escape hatches exist but are not the center.
Version caveat: Generator and client internals have shifted across majors; regenerate and re-check after upgrades.
Context7 id /prisma/docs · official documentation
Drizzle ORMSQL-flavored TypeScript ORM: schema in code, type-safe query builder and migration kit.
Fits: Teams wanting SQL semantics with static types, edge-runtime-friendly database access.
Not for: Deep ORM abstractions (identity maps, lazy graphs) — it deliberately stays close to SQL.
Version caveat: Young and fast-moving: dialect features and the migration kit change between minors, not just majors.
Context7 id /drizzle-team/drizzle-orm-docs · official documentation
Payload CMSCode-first headless CMS: collections, access control, hooks, and admin UI over your database.
Fits: Config-as-code content models, embedding a CMS inside a Next.js codebase.
Not for: Editor-first SaaS CMS expectations — the source of truth is your repository config.
Version caveat: The v3 era fuses with Next.js; v2-era answers about standalone servers no longer map.
Context7 id /payloadcms/payload · official documentation
BunJavaScript runtime, package manager, bundler and test runner in one binary.
Fits: Fast installs and scripts, built-in test/bundle workflows, Node-compat checks.
Not for: Codebases pinned to Node-specific native modules or runtime internals it does not replicate.
Version caveat: Node compatibility is broad but not total and improves release by release — verify per API, per version.
Context7 id /oven-sh/bun · official documentation
Paste the code and the doc excerpt into the AI Coding Assistant
AI SDKs & protocols09
Vercel AI SDKProvider-agnostic TypeScript AI toolkit: text/object generation, streaming, tool calls and UI hooks.
Fits: Streaming chat UIs, structured output, swapping model providers behind one interface.
Not for: Provider-exclusive features that have not landed in the abstraction yet.
Version caveat: Major versions reshaped core APIs and package names — lockfile major first, docs second.
Context7 id /vercel/ai · official documentation
OpenAI APIOpenAI's HTTP platform: model endpoints, tool use, structured output, files and batching.
Fits: Endpoint selection, request/parameter shapes, migration between API generations.
Not for: ChatGPT the consumer product — plans and app behavior are a different surface.
Version caveat: Endpoint generations coexist and deprecate on their own schedule; date any answer you rely on.
Context7 id /websites/developers_openai_api · official documentation
OpenAI Python SDKThe official Python client: typed requests, streaming, retries and async usage.
Fits: Client configuration, streaming iteration patterns, error and retry handling in Python.
Not for: REST-level questions better answered by the platform docs themselves.
Version caveat: The v0→v1 client rewrite changed everything; snippets are useless without the SDK version.
Context7 id /openai/openai-python · official documentation
Google Gen AI Python SDKThe unified google-genai Python client for Gemini across API-key and Vertex entry points.
Fits: Client setup for either entry point, streaming and multimodal request shapes in Python.
Not for: Legacy google-generativeai code — that is the predecessor SDK with a different surface.
Version caveat: It replaced an older SDK of similar name; confirm which package an answer imports before copying.
Context7 id /googleapis/python-genai · official documentation
Gemini APIGoogle's model API: generation, multimodal input, function calling, caching and model catalog.
Fits: Capability and parameter questions, model selection within the Gemini family.
Not for: Vertex-specific enterprise plumbing — overlapping but separately documented.
Version caveat: Model names and capability tiers rotate quickly; re-check the catalog date before hardcoding one.
Context7 id /websites/ai_google_dev_gemini-api · official documentation
LangGraphGraph-structured agent orchestration: nodes, edges, state, persistence and human-in-the-loop.
Fits: Long-running agent state machines, checkpointing, controlled multi-step flows.
Not for: One-shot prompt calls — a plain SDK call is simpler than a graph.
Version caveat: Python and JS variants track different release lines; state language and version together.
Context7 id /langchain-ai/langgraph · official documentation
Pydantic AITyped Python agent framework built on Pydantic validation: agents, tools, structured results.
Fits: Schema-validated model output, dependency-injected tools, type-checked agent code.
Not for: Teams outside the Pydantic/typing ecosystem — the value is the type system.
Version caveat: Young framework iterating fast; minor releases move APIs, so pin and read the changelog.
Context7 id /pydantic/pydantic-ai · official documentation
MastraTypeScript agent framework: workflows, agents, tools, memory and evals.
Fits: Structured TS agent apps with workflow steps and built-in eval harnesses.
Not for: Python-first stacks or teams wanting a thin SDK rather than a framework.
Version caveat: Early and fast-moving — expect surface changes between minors and verify against your installed version.
Context7 id /mastra-ai/mastra · official documentation
Model Context Protocol SDKThe MCP spec and official SDKs: servers, clients, tools, resources and transports.
Fits: Building or consuming MCP servers, transport and capability negotiation questions.
Not for: Product-specific MCP integrations — those live in each vendor's own docs.
Version caveat: The protocol revision matters as much as the SDK version; both sides must speak the same revision.
Context7 id /modelcontextprotocol/typescript-sdk · official documentation
AI agents & automation04
Claude CodeAnthropic's coding agent: CLI and IDE usage, hooks, MCP configuration, skills and permissions.
Fits: Configuring agent permissions and hooks, MCP server wiring, workflow automation questions.
Not for: General Claude API usage — the platform API is documented separately.
Version caveat: The agent surface evolves quickly across releases; check the docs against your installed version.
Context7 id /anthropics/claude-code · official documentation
OpenClawAn open-source personal AI assistant/agent project; its docs cover setup, channels and skills.
Fits: Self-hosted assistant experiments where you own the runtime and its integrations.
Not for: Turn-key managed products — this is a run-it-yourself open-source stack.
Version caveat: Community-driven and renamed during its life; verify current names and setup against the repository.
Context7 id /openclaw/openclaw · official documentation
OpenCodeAn open-source terminal coding agent; docs cover installation, providers and session workflow.
Fits: Terminal-first agent coding with your own model keys and provider choice.
Not for: IDE-embedded experiences — its home is the terminal.
Version caveat: Rapid release cadence typical of young agent tools; pin the version an answer was written for.
Context7 id /anomalyco/opencode · official documentation
n8nWorkflow automation: nodes, triggers, credentials, self-hosting and AI agent nodes.
Fits: Connecting services without custom glue code, self-hosted automation, AI steps in flows.
Not for: Latency-critical or heavy-compute paths — orchestration is the product, not raw throughput.
Version caveat: Node parameters shift between releases; match the docs to your instance version, cloud or self-hosted.
Context7 id /n8n-io/n8n-docs · official documentation
Platforms, payments & auth04
VercelDeployment platform: builds, serverless/edge functions, domains, caching and observability.
Fits: Build and routing configuration, function limits, domain and cache behavior.
Not for: Framework APIs themselves — Next.js has its own family above.
Version caveat: Platform limits and defaults change without a version number you control — date-check anything numeric.
Context7 id /websites/vercel · official documentation
StripePayments platform: payment intents, subscriptions, webhooks, Connect and the API reference.
Fits: Integration flow design, webhook handling, subscription lifecycle questions.
Not for: Regional payment availability questions — those are account- and country-specific.
Version caveat: The API is date-versioned per account; an answer is only correct relative to your pinned API date.
Context7 id /websites/stripe · official documentation
ClerkManaged auth and user management: prebuilt components, sessions, organizations and middleware.
Fits: Dropping in auth UI, session handling in Next.js middleware, org/role modeling.
Not for: Fully self-hosted identity requirements — it is a managed service by design.
Version caveat: SDK middleware patterns changed across majors; confirm the docs match your installed SDK line.
Context7 id /clerk/clerk-docs · official documentation
Better AuthSelf-hosted TypeScript auth framework: sessions, providers, plugins and database adapters.
Fits: Owning the auth stack in your own database with typed server/client APIs.
Not for: Teams wanting a managed identity provider with SLAs — this runs inside your app.
Version caveat: Young project with a fast plugin surface; re-verify adapter and plugin APIs on upgrade.
Context7 id /better-auth/better-auth · official documentation
Paste the code and the doc excerpt into the AI Coding Assistant
Testing & language tooling03
PlaywrightBrowser automation and e2e testing: locators, fixtures, tracing, parallelism and browser installs.
Fits: Stable end-to-end suites, locator strategy, CI browser setup and trace debugging.
Not for: Unit testing — pair it with a unit runner like Vitest rather than stretching e2e everywhere.
Version caveat: Browser binaries pin to the package version — mismatched installs are the classic CI failure.
Context7 id /microsoft/playwright · official documentation
VitestVite-native unit testing: config, mocking, snapshots, coverage and workspace mode.
Fits: Fast unit/component tests in Vite-ecosystem projects, Jest-migration questions.
Not for: Cross-browser end-to-end flows — that is Playwright's territory.
Version caveat: Tracks Vite majors closely; upgrade both together or expect resolver surprises.
Context7 id /vitest-dev/vitest · official documentation
TypeScriptThe language and compiler: type system features, tsconfig options and release notes.
Fits: Type-system questions, compiler-option effects, understanding errors by version.
Not for: Runtime behavior — types erase; runtime questions belong to your runtime's docs.
Version caveat: Minor releases add real type-system features; an answer may be valid only above a specific version.
Context7 id /microsoft/typescript · official documentation
Paste the failing test and the error into the AI Coding Assistant
FAQ
Frequently asked questions
What is this page?
A navigator over official library documentation: 42 families on one page, and for each — what the official docs cover, which tasks they fit, which they do not, and the version caveat you must carry into any AI-assisted answer. Every chunk links the primary source, so the page is a starting point, never a substitute for the vendor's docs.
How do I find the primary source for a library?
Start from the official documentation link in the library's chunk below. Failing that, the package registry entry (npm, PyPI) names the homepage and repository, and the repository's README links the docs site. Treat search results, blog posts and Q&A threads as secondary: useful for orientation, decisive for nothing.
Why do the version caveats matter so much?
Because an AI assistant may rely on training knowledge unless current documentation is provided, and a version mismatch — the assistant describing a different release than the one you run — is a common cause of wrong answers about these libraries. Naming the version you run and reading the family's caveat here first reduces that risk. For how version-pinned retrieval addresses this at the tool level, see our Context7 guide.
Tutorial, reference or changelog — which should I read?
Match the document to the question. Learning a workflow for the first time: the tutorial. Checking exact parameters, types, defaults and edge behavior: the reference. Upgrading, or debugging something that used to work: the changelog and the migration guide. Most documentation frustration comes from asking a reference question of a tutorial page.
How do I check whether an API is deprecated?
Search the official docs for the symbol plus 'deprecated', check the reference page for a deprecation notice, and read the changelog entries between your version and the current one. Deprecations are announced in one major and removed in a later one — the changelog tells you which side of that window your version sits on.
What is the right way to give documentation to an AI assistant?
Three parts: the library name with the exact version from your lockfile, the smallest doc excerpt that bears on your question, and the question itself with your failing code if there is any. The version stops the assistant from answering about a different release; the excerpt gives it current facts to reason over; the pairing makes the answer verifiable against the source you provided.
Where next
Related Tools
Context7 guideVersion-pinned library docs for AI coding — MCP, API, SDK.GigaChat APIOAuth, TLS, structured output, files and streaming — a safe first integration.Yandex AI StudioChat, embeddings, Wordstat, Search, OCR, Translate and SpeechKit — choose by job.AI Coding AssistantThe coding hub — review, debug, explain, test in chat.Vibe coding in TelegramDescribe what you want and get working code back in chat.All modelsSee every model @vustbot runs and how the free tier works.All tools