context7
Use when looking up library documentation, API references, framework patterns, or code examples for ANY library (React, Next.js, Vue, Django, Laravel, etc.). Fetches current docs via Context7 REST API. Triggers on: how to use library, API docs, framework pattern, import usage, library example.
What this skill does
# Context7 Documentation Lookup Skill Fetch current library documentation, API references, and code examples via the Context7 REST API. ## When to Use Use this skill when the user asks about library APIs, framework patterns, or version-specific behavior. Trigger on: - Library questions: "How do I use [library]?", "[library] API docs", "[library] patterns" - Import statements: `import`, `require`, `from` followed by a library name - Framework-specific topics: hooks, routing, middleware, ORM queries, schema definitions ## When NOT to Use Do NOT use this skill for: - General programming concepts (closures, recursion, design patterns) - Code review or refactoring tasks - Debugging business logic - Writing scripts from scratch without library-specific questions ## Core Workflow 1. **Search** for the library ID: ```bash scripts/context7.sh search "library-name" ``` 2. **Pick the best result**: Choose the ID with the highest score and most relevant description. Prefer official sources (e.g., `/vercel/next.js` over community forks). 3. **Fetch documentation** with a focused topic: ```bash scripts/context7.sh docs "<library-id>" "<topic>" "<mode>" ``` Always extract a specific topic from the user's question. For "How does React Suspense work with server components?", use topic `suspense server components`. ## Parameters | Parameter | Required | Description | |-----------|----------|-------------| | `library-id` | Yes | From search results, format `/vendor/library` | | `topic` | No | Focus area extracted from user query (e.g., `hooks`, `routing`, `validation`) | | `mode` | No | `code` (default) for API references; `info` for conceptual guides | ## Mode Selection Use `code` mode (default) when the user asks for API references, code examples, or implementation patterns. Use `info` mode when the user asks for conceptual explanations, architecture guides, or migration tutorials. ## Examples ```bash # React hooks API scripts/context7.sh search "react" scripts/context7.sh docs "/facebook/react" "hooks" "code" # Next.js App Router conceptual guide scripts/context7.sh search "nextjs" scripts/context7.sh docs "/vercel/next.js" "app router" "info" # Django ORM queries scripts/context7.sh search "django" scripts/context7.sh docs "/django/django" "queryset filter" "code" # Laravel Eloquent relationships scripts/context7.sh search "laravel" scripts/context7.sh docs "/laravel/framework" "eloquent relationships" "code" ``` ## Environment Configuration Set `CONTEXT7_API_KEY` for higher rate limits (optional): ```bash export CONTEXT7_API_KEY="your-api-key" ``` --- > **Contributing:** https://github.com/netresearch/context7-skill --- ## Credits & Attribution This skill is based on the excellent work by **[Netresearch DTT GmbH](https://www.netresearch.de/)**. Original repository: https://github.com/netresearch/context7-skill **Copyright (c) Netresearch DTT GmbH** — Methodology and best practices (MIT / CC-BY-SA-4.0) Special thanks to [Netresearch DTT GmbH](https://www.netresearch.de/) for their generous open-source contributions to the TYPO3 community, which helped shape this skill collection. Adapted by webconsulting.at for this skill collection
Related in Web Dev
generating-lwc-components
IncludedLightning Web Components with PICKLES methodology and 165-point scoring. Use this skill when the user creates or edits LWC components, builds wire service patterns, or writes Jest tests for LWC. TRIGGER when: user creates/edits LWC components, touches lwc/**/*.js, .html, .css, .js-meta.xml files, or asks about wire service, SLDS, or Jest LWC tests. DO NOT TRIGGER when: Apex classes (use generating-apex), Aura components, or Visualforce.
tanstack-query
IncludedManage server state in React with TanStack Query v5. Set up queries with useQuery, mutations with useMutation, configure QueryClient caching strategies, implement optimistic updates, and handle infinite scroll with useInfiniteQuery. Use when: setting up data fetching in React projects, migrating from v4 to v5, or fixing object syntax required errors, query callbacks removed issues, cacheTime renamed to gcTime, isPending vs isLoading confusion, keepPreviousData removed problems.
document-processor-api
IncludedProcess documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.
nutrient-document-processing
IncludedProcess documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.
tanstack-query
IncludedManage server state in React with TanStack Query v5. Covers useMutationState, simplified optimistic updates, throwOnError, network mode (offline/PWA), and infiniteQueryOptions. Use when setting up data fetching, fixing v4→v5 migration errors (object syntax, gcTime, isPending, keepPreviousData), or debugging SSR/hydration issues with streaming server components.
accelint-nextjs-best-practices
IncludedNext.js performance optimization and best practices. Use when writing Next.js code (App Router or Pages Router); implementing Server Components, Server Actions, or API routes; optimizing RSC serialization, data fetching, or server-side rendering; reviewing Next.js code for performance issues; fixing authentication in Server Actions; or implementing Suspense boundaries, parallel data fetching, or request deduplication.