bosskuai-documentation-lookuplisted

# Documentation Lookup ## When to use - Code depends on specific framework or library behavior and you need to verify it - User asks "how do I configure X in [library]?" or "what's the API for Y?" - Working with a library version that may differ from training data knowledge - Answering questions about obscure or recently changed API signatures - Any time version-specific behavior matters (breaking changes, new features, deprecated methods) - Avoiding hallucinated API signatures by grounding answers in live docs ## How this differs from nearby skills - **vs search-first:** search-first checks the existing codebase for prior solutions and patterns already in use. documentation-lookup fetches external, authoritative library documentation via Context7. - **vs polyglot-engineering:** polyglot-engineering handles cross-language translation and idiomatic patterns. documentation-lookup is specifically for fetching accurate, current external API docs. - **vs coding-best-practices:** coding-best-practices applies general principles. documentation-lookup answers factual questions about specific APIs. - **Training data vs Context7:** Always prefer Context7 for version-specific behavior, configuration options, and exact API signatures. Use training data only as fallback when Context7 is unavailable. ## MCP requirements - **Context7 (required).** This skill cannot function without it. - Graceful degradation: if Context7 is unavailable, answer from training data and explicitly state: "Th