Source-Driven Development has an agent verify framework-specific code against official documentation. It follows four steps: detect the stack and exact versions from the dependency file, fetch the specific documentation page, implement the documented pattern and cite the source with a full URL.
The skill ranks sources by authority, excludes Stack Overflow, blog posts and the model’s own memory as primary sources, surfaces conflicts between docs and existing code, and treats fetched pages as data that never directs the agent.
What You Get
- A four-step process: detect, fetch, implement and cite
- A ranked list of authoritative and non-authoritative sources
- Citation formats for code comments and conversation
- A marker for unverified patterns, red flags and a verification checklist
Common Use Cases
- Building with a framework where the correct pattern depends on the version
- Creating boilerplate that others will copy
- Checking code for deprecated APIs
- Producing code the user can verify against sources
What Makes It Unique
The skill is explicit that the agent’s own training data is not an acceptable primary source and requires an UNVERIFIED label when no documentation is found. It also includes retrieval safety rules, which keep fetched documentation from steering the agent or adding outbound endpoints to generated code.
Under The Hood
The skill is a single SKILL.md of instructions. The agent reads the project’s dependency files and then uses a web fetch tool to retrieve official documentation pages over the network. It runs no scripts of its own and points to the security-and-hardening skill for the prompt injection threat model.