source-driven-development

Verifies framework code patterns against official documentation and cites sources.

1|Updated Mar 2, 2025
One-click install
npx skills add https://github.com/marjorg/setup --skill source-driven-development-marjorg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: source-driven-development
Source: https://github.com/marjorg/setup/tree/main/home/.agents/skills/source-driven-development
Command: npx skills add https://github.com/marjorg/setup --skill source-driven-development-marjorg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Training data goes stale, APIs get deprecated, and best practices evolve, so framework code written from memory often contains outdated or incorrect 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, Cargo.toml, or Gemfile to identify exact framework and library versions before writing any code. - Documentation-Grounded Implementation: Fetches the specific official documentation page for the feature being implemented, follows documented API signatures, avoids deprecated patterns, and surfaces conflicts between docs and existing code. - Source Citation: Adds full-URL citations in code comments and conversation for every framework-specific decision, and explicitly flags anything that could not be verified. - Use Case: You are building a form in a React 19 project. Instead of a stale useState-based submission handler, the Skill detects React 19.1.0 from package.json, fetches the official useActionState reference, implements the documented pattern, and cites react.dev so you can verify the approach. ## Quick Start Ask the assistant to implement a framework-specific feature using source-driven development so every pattern is verified against the official docs and cited.

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 sure AI-generated code uses current framework best practices?

Use source-driven development: detect exact versions from dependency files like package.json, fetch the official documentation page for the feature, implement the documented pattern, and cite the source URL. This prevents stale training-data patterns from entering your codebase.

How to verify a React or Django pattern against official documentation?

Fetch the specific documentation page for the feature, such as react.dev/reference/react/useActionState or docs.djangoproject.com/en/6.0/topics/auth/, rather than the homepage. Extract API signatures, deprecation warnings, and migration notes, then match your code to them.

What sources are authoritative for framework code decisions?

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, blog tutorials, and AI-generated summaries are never cited as primary sources.

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 stay consistent with the existing codebase. The user chooses; the Skill never silently picks one approach.

When should I not use documentation verification for coding tasks?

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