documentation-lookuplisted

# Documentation Lookup (Context7) When the user asks about libraries, frameworks, or APIs, fetch current documentation via the Context7 MCP (tools `resolve-library-id` and `query-docs`) instead of relying on training data. ## Core Concepts - **Context7**: MCP server that exposes live documentation; use it instead of training data for libraries and APIs. - **resolve-library-id**: Returns Context7-compatible library IDs (e.g. `/vercel/next.js`) from a library name and query. - **query-docs**: Fetches documentation and code snippets for a given library ID and question. Always call resolve-library-id first to get a valid library ID. ## When to use Activate when the user: - Asks setup or configuration questions (e.g. "How do I configure Next.js middleware?") - Requests code that depends on a library ("Write a Prisma query for...") - Needs API or reference information ("What are the Supabase auth methods?") - Mentions specific frameworks or libraries (React, Vue, Svelte, Express, Tailwind, Prisma, Supabase, etc.) Use this skill whenever the request depends on accurate, up-to-date behavior of a library, framework, or API. Applies across harnesses that have the Context7 MCP configured. ## How it works ### Step 1: Resolve the Library ID Call the **resolve-library-id** MCP tool with: - **libraryName**: The library or product name taken from the user's question (e.g. `Next.js`, `Prisma`, `Supabase`). - **query**: The user's full question. This improves relevance ranking of re