source-driven-development

Implements framework code grounded in fetched official documentation with cited sources.

Updated Sep 5, 2026
One-click install
npx skills add https://github.com/pohlai88/afenda-xforge-v5 --skill source-driven-development-pohlai88
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: source-driven-development
Source: https://github.com/pohlai88/afenda-xforge-v5/tree/main/.agents/skills/source-driven-development
Command: npx skills add https://github.com/pohlai88/afenda-xforge-v5 --skill source-driven-development-pohlai88

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated framework code often relies on 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 with full URLs. ## Core Features & Use Cases - Stack Detection: Reads dependency files like package.json, composer.json, or go.mod to identify exact framework versions before writing code. - Documentation-Grounded Implementation: Fetches the specific official docs page for each feature, follows documented API signatures, and avoids deprecated patterns. - Source Citation & Conflict Surfacing: Annotates code with full-URL citations, quotes relevant passages, 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 on useActionState, implements the documented pattern, and cites the source instead of using an outdated useState-based approach. ## Quick Start Ask the assistant to implement a framework feature using source-driven development so every pattern is verified against 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 official documentation?

Detect exact versions from the project's dependency file, fetch the specific official docs page for the feature, implement the documented API signatures, and cite full URLs in code comments. Never rely on memory for framework-specific patterns.

What sources are authoritative for verifying API usage?

Official documentation is the primary source, followed by official blogs and changelogs, then web standards references like MDN, then compatibility data like caniuse.com. Stack Overflow, blog posts, and AI-generated summaries are never acceptable as primary citations.

Does this approach work with any programming language or framework?

Yes, it supports any stack with a dependency manifest: package.json for Node, composer.json for PHP, requirements.txt or pyproject.toml for Python, go.mod for Go, Cargo.toml for Rust, and Gemfile for Ruby.

What happens when documentation conflicts with existing project code?

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

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. It is also skippable when the user explicitly prioritizes speed over verification.