source-driven-development

Implements framework code verified against official documentation with cited sources.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/JacobThree/zero-bloat-mcp-stack --skill source-driven-development-jacobthree
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: source-driven-development
Source: https://github.com/JacobThree/zero-bloat-mcp-stack/tree/main/ai_blueprints/agent-skills/skills/source-driven-development
Command: npx skills add https://github.com/JacobThree/zero-bloat-mcp-stack --skill source-driven-development-jacobthree

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI assistants often write framework code from stale training data, producing deprecated APIs and outdated patterns that break against current library 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 any code. - Documentation-First Implementation: Fetches the specific official docs page for the feature being built, follows documented API signatures, and avoids deprecated patterns flagged in migration guides. - Source Citation: Annotates code comments and conversation output with full URLs, deep links, and quoted passages so every decision can be independently verified. - Use Case: You ask for a form handler in a React 19 project. The Skill detects React 19.1.0 from package.json, fetches the useActionState reference from react.dev, implements the modern pattern, and cites the exact documentation URL instead of emitting a stale useState-based 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 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 your dependency file, fetch the relevant official docs page for each feature, and implement only the patterns shown there. Every framework-specific decision gets a full-URL citation so you can verify it.

How to avoid deprecated APIs when generating code with AI?▼

Check the official documentation and migration guides for your detected version before implementing. If the docs deprecate a pattern, use the replacement; if no documentation exists for a pattern, flag it explicitly as unverified rather than guessing.

Which sources are authoritative for framework code decisions?▼

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, blog tutorials, and AI training data are never treated as primary sources.

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 Skill never silently picks one side when documentation and project code disagree.

When should I not use documentation-verified development?▼

Skip it for version-independent work like renaming variables, fixing typos, moving files, or pure logic such as loops and data structures. It also does not apply when you explicitly prioritize speed over verification.