source-driven-development

Grounds framework-specific code decisions in fetched official documentation with cited sources.

10|1|Updated Jul 29, 2026
One-click install
npx skills add https://github.com/flowing-abyss/obsidian-local-fonts --skill source-driven-development-flowing-abyss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: source-driven-development
Source: https://github.com/flowing-abyss/obsidian-local-fonts/tree/main/.ai/skills/source-driven-development
Command: npx skills add https://github.com/flowing-abyss/obsidian-local-fonts --skill source-driven-development-flowing-abyss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated code often relies on stale training data, producing deprecated APIs and outdated patterns that break against current framework versions. This Skill forces every framework-specific decision to be verified against official documentation and cited, so the code you receive is traceable to an authoritative source. ## Core Features & Use Cases - Stack Detection: Reads dependency files like package.json, composer.json, requirements.txt, go.mod, Cargo.toml, or Gemfile to identify exact framework versions before writing code. - Documentation Fetching and Citation: Retrieves the specific official docs page for each pattern, implements the documented approach, and cites full URLs with anchors in code comments and conversation. - Conflict Surfacing: When existing project code contradicts current documentation, it presents both options instead of silently choosing one. - Use Case: You ask for a form handler in a React 19 project. The Skill reads package.json, fetches the React docs for useActionState, implements the modern pattern, and cites the source instead of emitting a deprecated useState-based approach from memory. ## Quick Start Ask the assistant to implement a framework-specific feature using source-driven development so every pattern is verified against the official docs 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 best practices?

Require the AI to detect your framework versions from dependency files like package.json, fetch the official documentation for each pattern, and cite sources. This prevents deprecated APIs from stale training data entering your codebase.

How to verify an AI is not using deprecated APIs?

Check that every framework-specific pattern includes a citation to official documentation with a full URL. Deprecated APIs typically appear when code is written from memory rather than verified against the current version's docs and migration guides.

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, blog tutorials, and AI training data are not authoritative primary sources.

When should I skip documentation verification for code?

Skip verification when correctness does not depend on a framework version, such as renaming variables, fixing typos, or pure logic like loops and data structures. Version-independent tasks gain nothing from fetching docs.

What happens when official docs conflict with existing project code?

The conflict is surfaced to you with both options explained: adopt the modern documented pattern or stay consistent with the existing codebase. The decision is never made silently, since either choice has real tradeoffs.