addy-source-driven-development

Implements framework code verified against official documentation with cited sources.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Training data goes stale, APIs get deprecated, and best practices evolve, so code written from memory often contains outdated or incorrect framework 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, or Cargo.toml to identify exact framework versions before writing any code. - Documentation-Grounded Implementation: Fetches the specific official docs page for the feature being implemented, follows documented API signatures, and avoids deprecated patterns. - Source Citation: 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: You are building a form in a React 19 project. The Skill detects React 19.1.0 from package.json, fetches the useActionState reference from react.dev, implements the documented pattern, and cites the source so you can verify every decision. ## Quick Start Implement the form submission logic for my project using source-driven development, checking my package.json and citing official documentation for every framework pattern you use.

Frequently Asked Questions about addy-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 best practices?▼

Detect exact versions from the project's dependency file, fetch the relevant official documentation page, and implement using the documented API signatures. Cite full URLs for each framework-specific decision so every pattern is verifiable.

What sources are authoritative for verifying code 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, 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 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 for consistency. The user chooses the approach rather than the decision being made silently.

When should I not verify code against documentation?▼

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