Agent skill · software engineering · addyosmani
source-driven-development
Grounds every implementation decision in official documentation. Use when you want to verify an approach against the official docs before implementing it, or when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters.
Why this skill is useful
Provides a structured approach to implementing code based on the latest official documentation, ensuring accuracy and relevance for specific frameworks.
What it needs
About 6k tokens when loaded. Last updated 2026-08-06. 83,053 stars on the source repository.
What this skill does
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: Correctness does not depend on a specific version (renaming variables, fixing typos, moving files) Pure logic that works the same across all versions (loops, conditionals, data structures) The user explicitly wants speed over verification ("just do it quickly") The Process Step 1: Detect Stack and Versions Read the project's dependency file to identify exact versions: State what you found explicitly: If versions are missing or ambiguous, ask the user. Don't guess — the version determines which patterns are correct. Step 2: Fetch Official Documentation Fetch the specific documentation page for the feature you're implementing. Not the homepage, not the full docs — the relevant page. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills addyosmani/source-driven-development