source-driven-development

Verifies framework code patterns against official documentation and cites sources.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/yourlabpt/yourlabpt_website --skill source-driven-development-yourlabpt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: source-driven-development
Source: https://github.com/yourlabpt/yourlabpt_website/tree/main/projects/skills/source-driven-development
Command: npx skills add https://github.com/yourlabpt/yourlabpt_website --skill source-driven-development-yourlabpt

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 implementation decision in official documentation, ensuring the code you receive is verifiable against authoritative sources. ## Core Features & Use Cases - Stack Detection: Reads dependency files like package.json, composer.json, or go.mod to identify exact framework versions before writing any code. - Documentation-Grounded Implementation: Fetches the specific official docs page for each feature, follows documented patterns, and avoids deprecated APIs. - Source Citation: Annotates framework-specific decisions with full URLs and quoted passages so you can verify every choice. - 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 modern pattern, and cites the source instead of relying on outdated useState-based patterns. ## Quick Start Verify my framework code against the official documentation for the versions in my package.json and cite your sources for each pattern.

Frequently Asked Questions about source-driven-development

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

FAQPage Schema
How do I verify framework code against official documentation?▼

Detect the exact framework versions from dependency files like package.json or composer.json, then fetch the specific official docs page for each feature you implement. Follow the documented API signatures and cite full URLs for every framework-specific decision.

What sources are authoritative for framework best practices?▼

Official documentation sites like react.dev or docs.djangoproject.com are the primary authority, followed by official blogs and changelogs, then web standards references like MDN. Stack Overflow answers, blog posts, and training data should never be 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 detection step reads package.json, composer.json, requirements.txt, go.mod, Cargo.toml, or Gemfile to determine which documentation applies.

When should I not verify code against documentation?▼

Skip verification when correctness does not depend on a specific version, such as renaming variables, fixing typos, or moving files. Pure logic like loops and data structures that works identically across versions also does not require doc fetching.

What happens when documentation conflicts with existing code?▼

The conflict is surfaced to you with both options explained, such as using the modern documented pattern versus matching the existing codebase style. You choose the approach rather than having one silently picked for you.