source-driven-development

Implements framework code verified against official documentation with cited sources.

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/raishoemi/traffic-sim-v2 --skill source-driven-development-raishoemi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: source-driven-development
Source: https://github.com/raishoemi/traffic-sim-v2/tree/main/.github/skills/source-driven-development
Command: npx skills add https://github.com/raishoemi/traffic-sim-v2 --skill source-driven-development-raishoemi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Training data goes stale and APIs get deprecated, so code written from memory often uses 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, or go.mod to identify exact framework versions before writing any code. - Documentation Fetching: Retrieves the specific official docs page for the feature being implemented, following a strict source hierarchy that excludes Stack Overflow and blog posts. - Source Citation: Annotates code comments and explanations with full URLs and quoted passages so every decision can be verified. - Use Case: You are building a form in a React 19 project. The Skill detects React 19.1.0 from package.json, fetches the useActionState reference from react.dev, implements the documented pattern, and cites the exact source instead of using a deprecated useState-based approach. ## Quick Start Implement the login form for my React project using source-driven development and cite the official documentation for every pattern you use.

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 React code that follows current official documentation?

Detect the exact React version from package.json, fetch the relevant page on react.dev for the feature you need, and implement the documented pattern. Cite the full URL in code comments so every decision is verifiable.

How to avoid using deprecated APIs when coding with AI assistants?

Verify each framework-specific pattern against the official documentation for your detected version before implementing. Check migration guides and changelogs for deprecation notices, and never rely solely on training data which may contain outdated patterns.

What sources are authoritative for framework documentation?

Official documentation sites like react.dev or docs.djangoproject.com rank first, followed by official blogs and changelogs, then web standards references like MDN. Stack Overflow answers, tutorials, and AI-generated summaries are not authoritative primary sources.

When should I not verify code against documentation?

Skip verification for version-independent work like renaming variables, fixing typos, moving files, or pure logic such as loops and data structures. Verification matters only when correctness depends on a specific framework version.

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. You choose the approach rather than having one silently picked for you.