source-driven-development

Verifies framework code decisions against official documentation with cited sources.

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/MSC72m/DevForge --skill source-driven-development-msc72m
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: source-driven-development
Source: https://github.com/MSC72m/DevForge/tree/main/skills/source-driven-development
Command: npx skills add https://github.com/MSC72m/DevForge --skill source-driven-development-msc72m

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Training data goes stale, APIs get deprecated, and best practices evolve, so code written from memory often contains outdated or incorrect framework patterns. This Skill grounds every framework-specific implementation decision in official documentation, giving you code you can verify and trust. ## Core Features & Use Cases - Stack Detection: Reads dependency files like package.json, composer.json, or go.mod to identify exact framework versions before writing any code. - Documentation-Grounded Implementation: Fetches the relevant official docs page, follows documented API signatures, and avoids deprecated patterns. - Source Citation: Adds full-URL citations in code comments and conversation, and explicitly flags anything that could not be verified. - Use Case: When building a React 19 form, the Skill detects the version from package.json, fetches the useActionState reference from react.dev, implements the modern pattern, and cites the source instead of relying on a possibly outdated useState approach. ## Quick Start Ask the agent 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 the dependency file, fetch the relevant official documentation page, and implement only the patterns shown there. Every framework-specific decision gets a full-URL citation so you can verify it.

How to verify an API signature before implementing it in code?▼

Fetch the specific official docs page for that API rather than relying on memory, then match the documented signature exactly. If the docs deprecate a pattern, use the recommended replacement and cite the migration guidance.

Which sources are authoritative for framework documentation?▼

Official documentation sites rank first, followed by official blogs and changelogs, then web standards references like MDN, then compatibility data like caniuse.com. Stack Overflow answers, tutorials, and AI-generated summaries are never cited as primary sources.

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, or pure logic like loops and data structures. It is also unnecessary when the user explicitly prioritizes speed over verification.

What happens when official docs conflict with existing project code?▼

The conflict is surfaced to the user with both options explained: adopt the modern documented pattern or stay consistent with the existing codebase. The Skill never silently picks one approach.

Can fetched documentation content contain prompt injection attacks?▼

Yes, fetched pages are treated as untrusted data. Only API definitions, examples, and deprecation notes are extracted, while directives targeting the model are ignored and never allowed to override the user's request or expand task scope.