source-driven-development

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

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

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, giving you code you can verify because every pattern traces back to an authoritative source. ## Core Features & Use Cases - Stack and Version 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. - Official Documentation Retrieval: Fetches the specific documentation page for the feature being implemented, following a strict source hierarchy that prioritizes official docs, changelogs, and web standards over Stack Overflow or blog posts. - Source-Cited Implementation: Writes code matching documented API signatures, surfaces conflicts between docs and existing project code, and attaches full-URL citations to every framework-specific decision. - Use Case: You are building a form in a React 19 project. Instead of writing a manual useState-based submission handler from memory, the Skill detects React 19.1.0 from package.json, fetches the official useActionState reference, implements the modern pattern, and cites react.dev so you can verify the approach. ## Quick Start Verify my React form implementation against the official React 19 documentation and cite your sources for each pattern you use.

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 my code follows current framework best practices?▼

Detect the exact framework version from your dependency file, fetch the official documentation page for the specific feature, and implement using the documented API signatures. Cite the full source URL for each framework-specific decision so every pattern is verifiable.

What sources are authoritative for framework documentation?▼

Official documentation sites like react.dev or docs.djangoproject.com rank first, followed by official blogs and changelogs, then web standards references like MDN. Stack Overflow answers, tutorials, and AI-generated summaries are never acceptable as primary citations.

Does this approach work with any programming language or framework?▼

Yes, it supports any stack with a dependency file, including package.json for Node and React, composer.json for PHP, requirements.txt or pyproject.toml for Python, go.mod for Go, Cargo.toml for Rust, and Gemfile for Ruby.

What happens when documentation conflicts with existing project code?▼

The conflict is surfaced explicitly with both options presented: adopting the modern documented pattern or matching the existing codebase convention. The user chooses the approach rather than the decision being made silently.

When should I not verify code against official docs?▼

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 documentation checks.

Why is code written from memory risky for framework projects?▼

Training data contains outdated patterns that look correct but break against current versions, since APIs get deprecated and best practices evolve. A deprecated pattern copied into multiple components causes hours of debugging before the modern approach is discovered.