source-driven-development

Verify framework implementation decisions against official documentation with cited sources.

1|Updated Jan 28, 2025

Search Tags:#documentation #framework #code #best-practices #verify #citation #dependency-detection

Ready to run

npx skills add https://github.com/josuenavarroaguado/josuenavarroaguado.github.io --skill source-driven-development-josuenavarroaguado

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: source-driven-development
Source: https://github.com/josuenavarroaguado/josuenavarroaguado.github.io/tree/main/.github/skills/source-driven-development
Command: npx skills add https://github.com/josuenavarroaguado/josuenavarroaguado.github.io --skill source-driven-development-josuenavarroaguado

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures framework-specific implementation decisions are backed by authoritative official documentation so code does not rely on stale training data, deprecated APIs, or memory-based patterns that introduce bugs and long-term maintenance costs.

Core Features & Use Cases

Version-aware detection: identify exact framework and library versions from dependency files and prompt for clarification when versions are missing or ambiguous.
Document-backed implementation: fetch the specific official documentation pages for the feature being implemented, extract API signatures and patterns, and produce code that matches the documented usage.
Conflict surfacing and citation: highlight discrepancies between existing project code and current documentation, present options to the user, and include full URLs and quoted passages for every non-obvious decision.
Use Case: migrating a React app to a new major version and updating form handling to the documented modern pattern while citing migration guides and API references.

Quick Start

Use the source-driven-development skill to implement a React form handler, detect versions from package.json, and include full official documentation links for each decision.

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?▼

To verify framework code against official documentation, you detect exact dependency versions from project files, fetch relevant official documentation pages, surface conflicts with existing code, and include full source URLs and quoted passages for each pattern.

What is source-driven development for framework migrations?▼

Source-driven development for framework migrations ensures implementation decisions are backed by authoritative official documentation, preventing reliance on stale training data, deprecated APIs, or memory-based patterns that introduce bugs and long-term maintenance costs.

How do I implement routing and state management using documented framework patterns?▼

To implement routing and state management using documented patterns, fetch specific official documentation pages for the feature, extract API signatures and patterns, and produce code that matches the documented usage for your exact dependency versions.

Does this approach work with both frontend and backend frameworks?▼

Yes, this approach works with frontend and backend frameworks when implementing routing, forms, data fetching, state management, authentication, migrations, or creating starter patterns by verifying against authoritative official documentation.

What's the best way to update deprecated API patterns in a React migration?▼

The best way to update deprecated API patterns in a React migration is to detect versions from package files, fetch migration guides and API references, highlight discrepancies between existing code and current documentation, and present options with full URLs and quoted passages.

Why does my framework implementation conflict with current documentation?▼

Your framework implementation conflicts with current documentation when code relies on stale training data or deprecated APIs. Conflict surfacing detects exact dependency versions, fetches relevant documentation, highlights discrepancies, and includes full source URLs and quoted passages for each decision.