Source Driven Development

This tackles the problem of writing framework code from stale training data by forcing every implementation decision to trace back to official documentation. It detects your stack versions from dependency files, fetches the specific docs pages for what you're building, then implements using current patterns with inline citations. The workflow is detect, fetch, implement, cite. Use it when framework correctness matters: forms, auth, routing, anything that'll become a template others copy. It won't let you ship a deprecated React pattern just because it feels familiar, and it surfaces version conflicts between docs and existing code instead of silently picking one. The citation overhead pays off when you avoid debugging phantom APIs that changed two versions ago.

skills.sh installs: 67.4K
GitHub stars: 114.6K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add addyosmani/agent-skills --skill source-driven-development --agent claude-code

Installs into .claude/skills of the current project.

Files

Source-Driven Development

Overview

Every framework-specific code decision must be backed by official documentation. Don't implement from memory — verify, cite, and let the user see your sources. Training data goes stale, APIs get deprecated, best practices evolve. This skill ensures the user gets code they can trust because every pattern traces back to an authoritative source they can check.

When to Use

The user wants code that follows current best practices for a given framework
Building boilerplate, starter code, or patterns that will be copied across a project
The user explicitly asks for documented, verified, or "correct" implementation
Implementing features where the framework's recommended approach matters (forms, routing, data fetching, state management, auth)
Reviewing or improving code that uses framework-specific patterns
Any time you are about to write framework-specific code from memory

When NOT to use:

SKILL.md on GitHub