source-driven-development

Implements framework code verified against official documentation with cited sources.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated code often relies on stale training data, producing deprecated APIs, outdated patterns, and subtle bugs that only surface after hours of debugging. This Skill grounds every framework-specific implementation decision in current official documentation so the code you receive is verifiable and version-correct. ## Core Features & Use Cases - Stack Detection: Reads dependency files like package.json, requirements.txt, or go.mod to identify exact framework versions before writing any code. - Documentation-First Implementation: Fetches the specific official docs page for each feature, follows documented API signatures, and avoids deprecated patterns. - Source Citation: Annotates code comments and explanations with full URLs, deep links, and quoted passages so every decision is auditable. - Use Case: You ask for a React 19 form with submission state. Instead of a manual useState/isPending pattern from memory, the Skill fetches react.dev, implements useActionState per the current docs, and cites the exact reference page. ## Quick Start Ask the assistant to implement a framework-specific feature using source-driven development so every pattern is verified against the official documentation for your detected versions.

Frequently Asked Questions about source-driven-development

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

FAQPage Schema
How do I make AI-generated code follow current framework documentation?

Use source-driven development: detect exact versions from dependency files like package.json, fetch the relevant official docs page for each feature, implement the documented patterns, and cite full source URLs in code comments.

How to avoid deprecated APIs in AI-generated code?

Verify each pattern against the official documentation and migration guides for your detected version before implementing. If the docs deprecate a pattern, use the recommended replacement and flag anything that cannot be verified.

What sources are authoritative for framework code decisions?

Official documentation ranks first, followed by official blogs and changelogs, then web standards references like MDN, then compatibility data like caniuse.com. Stack Overflow answers, blog tutorials, and training data are never treated as primary sources.

Does source-driven development work with any programming language?

Yes, it detects stacks from package.json, composer.json, requirements.txt, pyproject.toml, go.mod, Cargo.toml, and Gemfile. It applies to any framework or library where official documentation exists for the detected version.

When should I not use documentation verification for code?

Skip it when correctness does not depend on a specific version, such as renaming variables, fixing typos, or pure logic like loops and data structures. It also does not apply when the user explicitly prioritizes speed over verification.

What happens when official docs conflict with existing project code?

The conflict is surfaced explicitly with both options presented: adopt the modern documented pattern or match the existing codebase for consistency. The user chooses rather than the decision being made silently.