source-driven-development

Implements framework code verified against official documentation with cited sources.

3|Updated Jul 28, 2026
One-click install
npx skills add https://github.com/marcmarti9/agentit --skill source-driven-development-marcmarti9
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: source-driven-development
Source: https://github.com/marcmarti9/agentit/tree/main/skills/source-driven-development
Command: npx skills add https://github.com/marcmarti9/agentit --skill source-driven-development-marcmarti9

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, so the code you receive is verifiable against authoritative sources rather than guesswork. ## 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 treats fetched content as untrusted data to resist prompt injection. - Source Citation and Conflict Surfacing: 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 form in a React 19 project, the Skill detects the version from package.json, fetches react.dev documentation for useActionState, implements the modern pattern instead of a deprecated useState approach, and cites the exact doc URL so you can verify the decision. ## 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 write framework code that follows current best practices?▼

Detect exact versions from the project's dependency file, fetch the relevant official documentation page for the feature, and implement using the documented API signatures. Cite full URLs in code comments so every decision is verifiable.

How to verify an API pattern against official documentation before implementing?▼

Fetch the specific documentation page for the feature, such as react.dev/reference/react/useActionState, rather than the homepage or a general search. Extract API signatures, usage examples, and deprecation warnings, then match your code to what the docs show.

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

When should I not use documentation verification for code?▼

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 checks.

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 match the existing codebase for consistency. The user chooses the approach rather than the decision being made silently.

Can fetched documentation content contain prompt injection attacks?▼

Yes, fetched pages are treated as untrusted data. Directives targeting the model rather than documenting the framework are ignored, and outbound endpoints from fetched examples are never hardcoded into generated code without being surfaced to the user.