source-driven-development

Verify framework-specific code against official version-specific documentation.

Updated Jun 1, 2026
One-click install
npx skills add https://github.com/j-cogburn/d3 --skill source-driven-development-j-cogburn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: source-driven-development
Source: https://github.com/j-cogburn/d3/tree/main/tests/project-t01/.d3/skills/source-driven-development
Command: npx skills add https://github.com/j-cogburn/d3 --skill source-driven-development-j-cogburn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing framework-specific code from memory often leads to outdated, deprecated, or incorrect patterns that waste hours of debugging and rework. This Skill eliminates that risk by requiring every implementation decision to be backed by official, version-specific documentation, so you get code you can trust.

Core Features & Use Cases

  • Automatic Stack Detection: Reads dependency files like package.json or go.mod to identify exact framework and library versions, ensuring you fetch the correct documentation for your project.
  • Mandatory Documentation Verification: Fetches only official, authoritative sources (official docs, changelogs, web standards) for every framework pattern, never relying on stale training data or unvetted tutorials.
  • Conflict Surfacing: When documented best practices clash with existing codebase patterns, it explicitly presents the options to you instead of making silent, potentially breaking changes.
  • Use Case: When building a React 19 form, this Skill ensures you use the current useActionState hook instead of deprecated useState patterns, with full source citations you can verify.

Quick Start

Use the source-driven-development skill to implement a new data fetching feature for your Vue 3.4 project, citing official Vue documentation for all composition API pattern choices.

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?

You verify framework code by requiring official documentation verification for every implementation decision, fetching authoritative sources like changelogs and web standards to enforce version-specific pattern adherence and ensure code correctness.

What is the best way to prevent deprecated framework patterns in my codebase?

The best way to prevent deprecated framework patterns is to enforce mandatory source citation for all framework-specific code, reading dependency files to detect exact library versions and explicitly surfacing conflicts between documented best practices and existing code.

How do I ensure version compliance when implementing new framework features?

You ensure version compliance by automatically detecting exact framework and library versions from dependency files, then fetching only official, authoritative sources to enforce version-specific pattern adherence during feature implementation and boilerplate generation.

How does source citation work for code review and legacy code improvement?

Source citation for code review and legacy code improvement works by requiring official documentation verification for every framework pattern, explicitly flagging unverified patterns and presenting options when documented best practices clash with existing codebase patterns.

Can I use automatic stack detection to fetch correct documentation for my project?

Yes, you can use automatic stack detection by reading dependency files like package.json or go.mod to identify exact framework and library versions, ensuring you fetch the correct, version-specific documentation for your project.

Why does conflict surfacing matter when updating framework-specific code?

Conflict surfacing matters because it explicitly presents options when documented best practices clash with existing codebase patterns, preventing silent, potentially breaking changes and ensuring long-term maintainability during feature implementation and legacy code improvement.