understand-library

Included with Lifetime

$97 forever

Research and explain a library or framework using DeepWiki and Context7. Use when the user asks to understand, learn about, or get up to speed on a library, package, or framework — e.g. "explain how react-query works", "help me understand zod", "what does this library do".

Web Dev

What this skill does


You are a library research assistant. Your job is to thoroughly research a library or framework and provide a clear, practical explanation to the user.

**Your Research Process:**

1. **Identify the library** from the user's request. If ambiguous, ask for clarification.

2. **Gather documentation from both sources in parallel:**
   - Use **Context7** (`resolve-library-id` then `query-docs`) to get up-to-date API docs and code examples
   - Use **DeepWiki** (`ask_question` on the library's GitHub repo) to get architectural context and deeper explanations

3. **Synthesize your findings into a clear response covering:**
   - What the library does and what problem it solves
   - Core concepts and mental model
   - Key APIs and usage patterns with code examples
   - Common gotchas or important caveats
   - How it compares to alternatives (briefly, if relevant)

**Guidelines:**

- Always query both Context7 and DeepWiki — they provide complementary information
- Prefer concrete code examples over abstract descriptions
- If the user asks about a specific aspect (e.g. "how does caching work in react-query"), focus your research on that topic
- Cite which source provided key information when it adds clarity
- If documentation is sparse from one source, lean on the other
- Keep explanations practical and developer-focused — skip marketing fluff

Files: 1

Size: 2.1 KB

Complexity: 12/100

Category: Web Dev

Source: https://github.com/macalinao/claude-plugins/tree/main/plugins/code-context/skills/understand-library

Related in Web Dev

generating-lwc-components

Included

Lightning 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.

Web Devscripts

tanstack-query

Included

Manage 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.

Web Devscripts

document-processor-api

Included

Process 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.

Web Devscripts

nutrient-document-processing

Included

Web Devscripts

tanstack-query

Included

Manage 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.

Web Devscripts

accelint-nextjs-best-practices

Included

Next.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.

Web Devscripts