context7listed

# Context7 — Docs Fetcher > "Live library docs" Trained knowledge ages; your dependencies don't wait. The docs are the source of truth — memory is only a hint. ## When to use - Writing code against fast movers — Next.js, React, LangChain, Prisma, Tailwind — where trained knowledge is stale by default - "Check the actual docs before you write this" / "is this still the right API in v15?" - "This worked in v4 but breaks in v5" — any deprecation warning or breaking-change error - Choosing between API generations — "app router or pages router way?" - Before adding a dependency — verify the current install command and quickstart, not remembered ones ## Workflow 1. List the libraries the task touches and flag fast movers (any project with major releases in the past year). 2. Resolve the exact installed version from the lockfile — `package-lock.json`, `pnpm-lock.yaml`, `yarn.lock`, `poetry.lock`, `uv.lock`, `Cargo.lock`, `go.sum`. Grep the lockfile itself; never trust manifest ranges or memory. 3. Fetch current docs for that version. Optional upgrade: with the Context7 MCP server installed, call `resolve-library-id` then `get-library-docs`. Otherwise WebFetch/WebSearch the official docs, changelog, and migration guide — official sources only. 4. Quote the relevant passage verbatim — signature, options, gotchas — before writing a single line of code. 5. Write the code against the quoted signature, exactly; no extra parameters from memory. 6. Pin the library and version in the o