By name: research-verify-before-claim description: Use when you must verify facts about libraries, tools, commands, or APIs before recommending an approach.
Goal
Avoid confident nonsense. Verify with primary sources and/or local evidence.
Workflow
- Identify what must be true for the recommendation to work.
- Verify versions and capabilities:
- Read official docs/release notes
- Check local tool output (e.g., --version, help)
- Prefer minimal working examples:
- A tiny snippet or command that proves feasibility
- State uncertainty explicitly when verification is not possible.
- Provide fallbacks:
- Alternative libraries
- Feature flags
- Safer defaults
Output format
- Claims verified (bullets)
- Evidence (docs/commands)
- Recommendation
- Fallback options