source-driven-development

Implements framework code verified against official documentation with cited sources.

Updated Jul 19, 2026
One-click install
npx skills add https://github.com/DagimAlemayehuu/AgenticEngineering --skill source-driven-development-dagimalemayehuu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: source-driven-development
Source: https://github.com/DagimAlemayehuu/AgenticEngineering/tree/main/agentic-engineering/core/dependencies/research/source-driven-development
Command: npx skills add https://github.com/DagimAlemayehuu/AgenticEngineering --skill source-driven-development-dagimalemayehuu

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 implementation 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, following a strict source hierarchy (official docs, official blogs, MDN, caniuse) and rejecting Stack Overflow or blog posts as authorities. - Source Citations: Annotates code comments and explanations with full URLs, deep-link anchors, and quoted passages so every decision can be verified. - Conflict Surfacing: When documentation contradicts existing project code, it presents both options instead of silently choosing one. - Use Case: You ask for a React 19 form handler. The Skill reads package.json, fetches react.dev/reference/react/useActionState, implements the modern Actions pattern instead of manual useState loading flags, and cites the exact doc section. ## Quick Start Use source-driven development to implement a form submission handler for this project, verifying the pattern against the official docs for my detected framework version and citing your sources.

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 APIs?▼

Verify the framework version from the dependency file, then fetch the official documentation page for the specific feature before implementing. Cite the doc URL in code comments so every pattern can be checked against the authoritative source.

How to detect a project's framework versions before writing code?▼

Read the project's dependency manifest: package.json for Node/React/Vue, composer.json for PHP, requirements.txt or pyproject.toml for Python, go.mod for Go, Cargo.toml for Rust, and Gemfile for Ruby. If versions are missing or ambiguous, ask the user rather than guessing.

What sources are authoritative for framework documentation?▼

Official documentation sites rank first, followed by official blogs and changelogs, then web standards references like MDN and compatibility data like caniuse. Stack Overflow answers, tutorials, and AI training data are never acceptable as primary citations.

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 discrepancy is never resolved silently.

When should I skip documentation verification?▼

Skip it for version-independent work like renaming variables, fixing typos, moving files, or pure logic such as loops and data structures that behave identically across versions. It also does not apply when the user explicitly prioritizes speed over verification.