source-driven-development

Implements framework code grounded in fetched official documentation with cited sources.

Updated Jul 22, 2026
One-click install
npx skills add https://github.com/Chau165/local_skill --skill source-driven-development-chau165
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: source-driven-development
Source: https://github.com/Chau165/local_skill/tree/main/codex/skills/source-driven-development
Command: npx skills add https://github.com/Chau165/local_skill --skill source-driven-development-chau165

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Training data goes stale, APIs get deprecated, and best practices evolve, so framework code written from memory often contains outdated or incorrect patterns. This Skill grounds every framework-specific implementation decision in official documentation, so the code you receive is verifiable against authoritative sources. ## Core Features & Use Cases - Stack Detection: Reads dependency files like package.json, composer.json, requirements.txt, go.mod, Cargo.toml, or Gemfile to identify exact framework versions before writing any code. - Documentation-Grounded Implementation: Fetches the specific official documentation page for the feature being implemented, follows documented API signatures, avoids deprecated patterns, and treats fetched content as untrusted data rather than instructions. - Source Citation and Conflict Surfacing: Adds full-URL citations in code comments and conversation, quotes relevant passages for non-obvious decisions, and explicitly flags anything that could not be verified. - 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 relying on a possibly outdated useState approach. ## Quick Start Implement this feature using source-driven development so every framework pattern is verified against the official docs and cited.

Frequently Asked Questions about source-driven-development

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

FAQPage Schema
How do I write framework code that follows current official documentation?

Detect exact versions from the project's dependency file, fetch the specific official documentation page for the feature, implement using the documented API signatures, and cite full source URLs in code comments. Flag anything the docs do not cover as unverified.

What sources are authoritative for verifying framework patterns?

Official documentation is the primary source, followed by official blogs and changelogs, then web standards references like MDN, and compatibility data like caniuse.com. Stack Overflow answers, blog posts, tutorials, and training data are never cited as primary sources.

Does this approach work with any framework or language?

Yes, it supports any stack with a dependency file, including Node, PHP, Python, Go, Rust, and Ruby projects. The version detected from files like package.json or go.mod determines which documentation patterns are correct.

What happens when official docs conflict with existing project code?

The conflict is surfaced to the user with both options explained, such as using the modern documented pattern versus matching the existing codebase. The Skill never silently picks one approach over the other.

When should I not use documentation-driven development?

Skip it when correctness does not depend on a specific version, such as renaming variables or fixing typos, for pure logic that works identically across versions, or when the user explicitly prioritizes speed over verification.