source-driven-development

Verifies framework code against official documentation and cites sources for every implementation decision.

Updated Sep 15, 2026
One-click install
npx skills add https://github.com/Qiuyi-Hong/addyosmani-skills --skill source-driven-development-qiuyi-hong
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: source-driven-development
Source: https://github.com/Qiuyi-Hong/addyosmani-skills/tree/main/skills/source-driven-development
Command: npx skills add https://github.com/Qiuyi-Hong/addyosmani-skills --skill source-driven-development-qiuyi-hong

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated framework code often relies on stale training data, producing deprecated APIs and outdated patterns that break against current library versions. This Skill grounds every framework-specific implementation decision in fetched official documentation, with citations the user can verify. ## Core Features & Use Cases - Stack Detection: Reads dependency files (package.json, composer.json, requirements.txt, go.mod, Cargo.toml, Gemfile) to identify exact framework versions before writing code. - Documentation Fetching and Citation: Retrieves the specific official docs page for each feature, implements the documented pattern, and cites full URLs with anchors in code comments and conversation. - Conflict Surfacing and Injection Defense: Flags discrepancies between docs and existing code for user decision, and treats fetched documentation as untrusted data to resist prompt injection. - Use Case: When building a React 19 form, the Skill detects the version from package.json, fetches the useActionState reference from react.dev, implements the documented pattern, and cites the source instead of emitting a deprecated useState-based approach. ## Quick Start Ask the agent to implement a framework-specific feature using source-driven development so every pattern is verified against the official docs for your detected versions.

Frequently Asked Questions about source-driven-development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make AI-generated code match current framework documentation?

Use source-driven development: detect exact versions from dependency files like package.json, fetch the relevant official docs page for each feature, and implement only documented patterns. Every non-trivial decision gets a full-URL citation so you can verify it.

How to avoid deprecated APIs in AI-generated React or Django code?

Check the official documentation and migration guides for your detected version before implementing. If the docs deprecate a pattern, use the replacement; if no documentation exists for a pattern, flag it as unverified rather than relying on training data.

Which sources are authoritative for verifying framework code?

Official documentation ranks first, followed by official blogs and changelogs, then web standards references like MDN, then compatibility data like caniuse.com. Stack Overflow answers, blog tutorials, and AI-generated summaries are never acceptable as primary citations.

Can fetched documentation pages contain prompt injection attacks?

Yes, fetched pages are treated as untrusted data. The Skill extracts only API signatures, examples, and deprecation notes while ignoring directives aimed at the model, and never hardcodes outbound endpoints from fetched examples without surfacing them to the user.

When should I not verify code against official documentation?

Skip verification when correctness does not depend on a framework version, such as renaming variables, fixing typos, moving files, or writing pure logic like loops and data structures that behaves identically across versions.