source-driven-development

Implements framework code verified against official documentation with cited sources.

1|Updated May 29, 2026
One-click install
npx skills add https://github.com/memasanz/agent-harness --skill source-driven-development-memasanz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: source-driven-development
Source: https://github.com/memasanz/agent-harness/tree/main/.github/skills/source-driven-development
Command: npx skills add https://github.com/memasanz/agent-harness --skill source-driven-development-memasanz

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 grounds every framework-specific decision in official documentation so the code you receive is verifiable and current. ## 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-First Implementation: Fetches the specific official docs page for the feature being built, follows documented API signatures, and avoids deprecated patterns. - Source Citation: Adds full-URL citations in code comments and conversation, quotes relevant passages for non-obvious decisions, 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 react.dev docs for useActionState, implements the modern pattern instead of manual useState loading flags, and cites the source so you can verify it. ## 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 best practices?

Use source-driven development: detect exact versions from dependency files like package.json, fetch the relevant official documentation page, and implement only the patterns shown there. Every framework-specific decision gets a full-URL citation you can verify.

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 docs conflict with existing project code, surface the conflict and let the user choose.

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, blog posts, and AI-generated summaries are never cited 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, covering JavaScript, PHP, Python, Go, Rust, and Ruby ecosystems. The same fetch-implement-cite process applies to each.

When should I not verify code against documentation?

Skip verification when correctness does not depend on a specific version, such as renaming variables, fixing typos, or moving files. Pure logic like loops and data structures that works identically across versions also does not require doc fetching.

What happens if documentation cannot be found for a pattern?

The pattern is explicitly flagged as unverified with a warning that it is based on training data and may be outdated. Honest flagging is preferred over presenting unverified code with false confidence.