deep-docslisted

Perform authoritative, version-aware documentation research for software, frameworks, SDKs, libraries, APIs, CLIs, databases, developer tools, and platforms used in the current task or project. Detect the exact product and installed version from project files or safe local commands, then search official versioned documentation, release notes, API specifications, official source repositories, local CLI manuals, and explicitly configured read-only documentation sources. Use when implementation correctness depends on precise behavior, version compatibility, availability, deprecation, configuration, migration, or documented constraints. Prefer primary sources and return source-linked evidence. Defer Apple development documentation to apple-docs. Do not use for general web research, product recommendations, build-versus-buy decisions, debugging without a documentation question, or broad architecture decisions.
martonpaulo/skills · ★ 1 · AI & Automation · score 71

Install: claude install-skill martonpaulo/skills

# Deep Docs Answer precise non-Apple software documentation questions with explicit product and version context. Use `apple-docs` for Apple development; do not duplicate Apple providers here. Use `context7` when an indexed snippet of a library's current API is enough. This skill owns conclusions that must be traced to an official versioned source, and is the escalation when a library is not indexed or when compatibility, availability, deprecation, or migration has to be proven. ## Workflow 1. Run `detect_project_context()` before external lookup in an existing project. Resolve declared, locked, locally detected, and unresolved versions separately. 2. Define the exact behavior, configuration, migration, compatibility, availability, or deprecation question. Use the requested version when explicit; otherwise prefer a trustworthy lock or installed version. 3. Select the smallest applicable configured provider. Read [provider-contract.md](references/provider-contract.md) for the five implemented provider types. 4. Use sources in this order: official versioned documentation; official specifications or API schemas; official release and migration notes; official repository documentation; local installed CLI documentation; accepted standards or language proposals; official vendor forums; community sources. 5. Search narrowly, fetch only the relevant document or sections, and preserve the source URL or local CLI identifier. Do not infer versions, URLs, availability, deprecation, or