What problem does it solve? When writing code against libraries like React, Next.js, Prisma, or FastAPI, guessing API patterns from memory leads to errors, while pasting full documentation pages wastes enormous amounts of context tokens. This Skill fetches only the relevant slices of official documentation so coding decisions are grounded in current, correct references. ## Core Features & Use Cases - Token-Efficient Fetching: Retrieves docs through the Context7 MCP server and filters output by content type (examples, api-ref, setup, concepts, migration, troubleshooting, patterns), achieving 60-90% token savings via shell-based extraction that costs zero LLM tokens. - Auto-Detection Workflow: Maps task context (implementing, debugging, installing, integrating, upgrading) to the right content type, with library resolution from names, error messages, or direct Context7 IDs. - Robust Error Handling: Structured error codes for library-not-found, mismatches, empty results, and rate limits, plus exponential-backoff retries for infrastructure failures and multi-source API key configuration. - Use Case: While debugging a PrismaClientKnownRequestError, fetch troubleshooting and example content for unique constraint errors from the official Prisma docs instead of guessing at the fix. ## Quick Start Ask the assistant to fetch the official React documentation examples for useState before writing a new hook-based component.
