Read The Damn Docs
Do not guess where authoritative docs can answer the question. Web-search for
the current official docs, open the relevant pages, and read them before
coding. See the description above for the trigger conditions and the
Anthropic/Claude API carve-out.
What Counts As Docs
Use the most authoritative source available:
- Official product docs, API references, migration guides, changelogs, and
SDK source/types for third-party behavior. Find these with web search when
you do not already have the exact URL.
- Package registry metadata for versions.
- Local repo docs, ADRs, and schemas when the question is about
project-specific behavior rather than a third-party contract.
Avoid Stack Overflow, old blog posts, and memory as the primary source when
official docs exist.
Required Workflow
- Identify the exact surface: package name, installed version, target
version, provider endpoint, or config file.
- Search the web for the current official docs unless they're already local
or the user supplied a URL.
- Open and read the docs closest to that surface.
- Extract the facts needed: option names, imports, breaking changes, limits,
permissions, examples for the current major version.
- Implement or answer using those facts. If the docs conflict with existing
code, inspect the local code path and call out the discrepancy.
- Verify with the smallest useful check: typecheck, tests, build, or a local
reproduction.
- Name the docs consulted when that evidence affects the recommendation.
If Docs Are Unavailable
If network access, auth, or missing local files prevents reading the docs,
say that plainly before relying on memory.
1---2name: read-the-damn-docs3description: Use when installing or upgrading a version-sensitive package, SDK, or framework; working with auth, billing, migrations, or another security-sensitive flow; or diagnosing an error that suggests API drift (deprecation, missing exports, changed defaults, version mismatch). Web-searches for current official docs and reads them before assuming from memory. For Anthropic/Claude API questions, defer to the claude-api skill instead.4---56# Read The Damn Docs78Do not guess where authoritative docs can answer the question. Web-search for9the current official docs, open the relevant pages, and read them before10coding. See the description above for the trigger conditions and the11Anthropic/Claude API carve-out.1213## What Counts As Docs1415Use the most authoritative source available:1617- Official product docs, API references, migration guides, changelogs, and18 SDK source/types for third-party behavior. Find these with web search when19 you do not already have the exact URL.20- Package registry metadata for versions.21- Local repo docs, ADRs, and schemas when the question is about22 project-specific behavior rather than a third-party contract.2324Avoid Stack Overflow, old blog posts, and memory as the primary source when25official docs exist.2627## Required Workflow28291. Identify the exact surface: package name, installed version, target30 version, provider endpoint, or config file.312. Search the web for the current official docs unless they're already local32 or the user supplied a URL.333. Open and read the docs closest to that surface.344. Extract the facts needed: option names, imports, breaking changes, limits,35 permissions, examples for the current major version.365. Implement or answer using those facts. If the docs conflict with existing37 code, inspect the local code path and call out the discrepancy.386. Verify with the smallest useful check: typecheck, tests, build, or a local39 reproduction.407. Name the docs consulted when that evidence affects the recommendation.4142## If Docs Are Unavailable4344If network access, auth, or missing local files prevents reading the docs,45say that plainly before relying on memory.
caneff