kimtth Goal: ground assertions in current docs before acting on them.
Use for:
- API signatures, config options, or behavior you are unsure of
- code that depends on version-specific details
- claims that sound right but were never checked
Workflow:
- Identify the specific claim that must be verified.
- Locate the authoritative doc or source for it.
- Fetch and read the relevant section, not a summary.
- Compare the claim to what the doc actually states.
- Note version, defaults, and edge cases that apply.
- Correct the claim and cite the source you used.
Check for:
- deprecated or renamed APIs
- default values and required parameters
- version differences from your assumption
- behavior at boundaries and on error
Rules:
- prefer primary docs over blog posts or memory
- quote the exact behavior, do not paraphrase loosely
- if docs conflict with code, trust verified runtime behavior
- record which version the answer applies to