What problem does it solve?
Prevents unreliable or second-hand answers by forcing technical responses to be grounded in primary sources like official documentation, blog posts, source code, and changelogs.
Core Features & Use Cases
- Primary-source-first answering: Resolves answers by searching for official documentation first, then official blog/changelog posts, then GitHub source/README/releases, and only then uses web search to locate a primary URL to fetch and read.
- Tool-driven verification: Uses context7 for library/framework documentation lookups, defuddle for extracting clean content from official blog pages, and GitHub access (GitHub MCP or gh CLI) for source-based evidence.
- Evidence-forward output: Produces responses that include a sourced section with a URL/identifier, a retrieved timestamp (or context7 docs note), and a key excerpt quoted before analysis.
Quick Start
Run /source-first when you need an authoritative answer and tell it what technology and exact question to verify using official sources.