source-driven-development

Name: source-driven-development
Availability: InStock
Author: huangzida

Resolve framework patterns from official documentation with cited sources.

2|1|Updated Mar 26, 2026

Search Tags:#documentation #frameworks #verification #citation #source-driven #trustworthy-code

Ready to run

npx skills add https://github.com/huangzida/skills --skill source-driven-development-huangzida

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: source-driven-development
Source: https://github.com/huangzida/skills/tree/main/source-driven-development
Command: npx skills add https://github.com/huangzida/skills --skill source-driven-development-huangzida

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Grounds every implementation decision in official documentation to ensure accuracy and trust, preventing outdated patterns from creeping into code.

Core Features & Use Cases

Documentation-backed decision making: All patterns are verified against official docs with citations.
Framework-agnostic correctness: Applicable across any framework or library where correctness matters.
Auditable code paths: Enables traceability from code decisions to primary references.

Quick Start

Start by identifying the exact versions and official docs for the target stack, then implement only patterns shown in the official docs and attach full citations to every decision.

Frequently Asked Questions about source-driven-development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I verify framework patterns against official documentation?▼

To verify framework patterns against official documentation, fetch current docs, extract the documented patterns, implement accordingly, and surface citations with full URLs for every decision.

What is source-driven development for framework-specific code?▼

Source-driven development resolves every framework-specific pattern strictly from official documentation rather than memory, providing sources for every decision to ensure accuracy and trust.

Can I use documentation-backed implementation for any framework or library?▼

Yes, documentation-backed implementation is framework-agnostic and applicable across any framework or library where correctness matters, including boilerplate, starter code, and critical features.

How do I implement boilerplate code with official documentation citations?▼

To implement boilerplate code with citations, identify the exact versions and official docs for your target stack, implement only patterns shown in the official docs, and attach full citations to every decision.

Why does outdated code creep into framework implementations?▼

Outdated code creeps into framework implementations when decisions rely on memory instead of current official documentation, making source-driven verification necessary to prevent deprecated patterns.

What's the best way to ensure trustworthy code across different frameworks?▼

The best way to ensure trustworthy code across frameworks is to ground every implementation decision in official documentation with citations, enabling auditable code paths traceable to primary references.