
source-driven-development
Grounds every implementation decision in official documentation
by addyosmaniFree
Description
source-driven-development is an agent skill from Addy Osmani's agent-skills collection that requires every framework-specific code decision to be backed by official documentation. The agent should not implement from memory. It verifies an approach against the documentation, cites its sources, and lets the user see them. The reasoning is that training data goes stale, APIs get deprecated and best practices change, so a pattern that traces back to an authoritative source the user can check is more trustworthy than one that does not. The skill applies when a user wants code that follows current best practices for a framework, when building boilerplate or starter code that will be copied across a project, when a user asks for a documented, verified or correct implementation, when implementing features where the framework's recommended approach matters, such as forms, routing, data fetching, state management or authentication, when reviewing code that uses framework-specific patterns, and any time the agent is about to write framework-specific code from memory.…
Highlights
- Verifies framework decisions against official docs
- Cites sources the user can check
- Covers forms, routing, data fetching and auth
- Avoids implementing from memory
Ratings & Reviews
No ratings yet
Be the first to rate source-driven-development.
People also visit

architecture-decision-records
Capture architectural decisions as numbered ADR markdown files in docs/adr/

brand-discovery
Run a structured, resumable multi-session brand identity interview across 8

codebase-onboarding
Analyze an unfamiliar codebase and generate a structured onboarding guide

coding-standards
Baseline cross-project coding conventions for naming, readability, immutability
source-driven-development FAQ
What does the source-driven-development skill do?
It makes an agent check framework-specific code decisions against official documentation and cite the sources before it implements them.
How do I install it?
Run: npx skills add https://github.com/addyosmani/agent-skills --skill source-driven-development
Why not write from memory?
The skill says training data goes stale, APIs get deprecated and best practices evolve, so patterns should trace to a source the user can check.
Which areas does it cover?
Framework features such as forms, routing, data fetching, state management and authentication, plus boilerplate that will be copied across a project.
What security checks has it passed?
skills.sh lists three audits: Gen Agent Trust Hub Pass, Socket Pass and Snyk Warn. A Warn or Fail is worth reading before you install.
What are the best source-driven-development alternatives?
Popular alternatives to source-driven-development include research, architecture-decision-records and brand-discovery. See all source-driven-development alternatives





