Source Driven
Implement features from official docs for the exact installed dependency versions, not training d…
by helderberto · MIT
The skill
Implement features from official docs for the exact installed dependency versions, not training data. Use when asked to "check the docs", "use official docs", "source-driven", or with unfamiliar APIs/libraries. Don't use for well-known stdlib APIs or project-internal code.
Source-Driven Development
Never rely on training data for API usage. Read the source of truth for the installed version.
- Pin versions — read the project manifest/lockfile for the exact version of each library involved.
- Fetch docs for that version (not "latest") with WebFetch. Extract signatures, required params, return types, breaking changes. Docs missing or ambiguous → the repo README for that tag, then the installed package source (
node_modules/, site-packages, vendor, …) and its type definitions. - Implement only confirmed APIs, matching signatures exactly. Anything you cannot verify gets marked inline:
// UNVERIFIED: could not confirm in docs for v{version}(ordocs for v{closest}, installed v{actual}). - Cite surprising or version-specific usage with a one-line
// Ref: <url>. Don't comment obvious calls.
Use this skill
Connect your agent to the Skill Store MCP server and ask for it by ref: helderberto/source-driven-36753954705.
Details
- Publisher
- helderberto
- Category
- Software Development › Developer docs & tooling
- License
- MIT
- Updated
- 2026-10-16
References
More from helderberto
- A11Y Audit Audit accessibility (WCAG) in frontend code.
- Architecture Audit Surface architectural friction across a codebase and propose deep-module refactors as RFCs.
- Build Implement the next unblocked ticket test-first and commit it, or fan every ticket out to parallel…
- Check Validate code quality — auto-fix formatting/lint, verify types, run tests.