What problem does it solve? Framework APIs change across versions, and code written from training data often uses deprecated signatures or outdated patterns. This Skill forces every framework-specific implementation decision to be verified against current official documentation before code is written, with explicit citations and UNVERIFIED flags when verification fails. ## Core Features & Use Cases - DETECT → FETCH → IMPLEMENT → CITE workflow: Reads dependency manifests (package.json, pyproject.toml, go.mod, etc.) to identify exact versions, fetches the specific official doc page, implements documented patterns, and cites full URLs in code comments. - Cache-aware revalidation: Integrates with webfetch-cache hooks so repeated fetches of the same doc page use HTTP 304 revalidation, making verification nearly free within a session. - Source hierarchy and conflict surfacing: Prioritizes official docs, changelogs, and standards references over Stack Overflow, and surfaces conflicts between docs and existing codebase patterns to the user instead of silently choosing. - Use Case: When migrating a React 18 app to React 19, the Skill detects the version from package.json, fetches react.dev reference pages, replaces manual isPending state with useActionState, and cites the exact doc URLs in the code. ## Quick Start Ask the assistant to implement a framework-specific feature using source-driven-development, for example: "Write a Next.js route handler following the current official docs and cite your sources."
