Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
source-driven-development
source-driven-development is an open-source docs skill for Claude Code and compatible agents, published by addyosmani. Its author describes it as: “Grounds every implementation decision in official documentation. Use when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters.”. The project has 88k stars on GitHub and is available under the MIT license. Add it to your setup with `/plugin marketplace add addyosmani/agent-skills`.
What source-driven-development does
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.
Installation
Add source-driven-development to your agent with:
/plugin marketplace add addyosmani/agent-skills Always review a skill's source before installing it. This command comes from the skill's public repository; the linked repo is the source of truth for exact setup steps.
What's inside
The SKILL.md for source-driven-development is organised into these sections:
- Overview
- When to Use
- The Process
- Step 1: Detect Stack and Versions
- Step 2: Fetch Official Documentation
- Step 3: Implement Following Documented Patterns
- Step 4: Cite Your Sources
- Common Rationalizations
- Red Flags
- Verification
When to use it
Reach for source-driven-development when you want docs help from your agent without writing the same instructions every session. Load the skill and the agent picks it up automatically for relevant tasks.
Strengths
- Clear MIT license — safe to read and adapt
- Ships in addyosmani/agent-skills, an established project with 88,280 GitHub stars
- Actively maintained (recent commits)
Topics
Frequently asked questions
- What does source-driven-development do?
- Grounds every implementation decision in official documentation. Use when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters.
- How do I install source-driven-development?
- Run /plugin marketplace add addyosmani/agent-skills in your agent, then reload your skills. Review the source at https://github.com/addyosmani/agent-skills before installing.
- Is source-driven-development free to use?
- Yes. source-driven-development is free and open source under the MIT license, so you can read, run, and adapt it within that license's terms.
- Where does source-driven-development come from?
- source-driven-development ships inside addyosmani/agent-skills, a repository that contains 25 catalogued skills in total. The repository's 88,280 GitHub stars apply to that whole collection, not to this skill on its own.
Related skills
More Docs →Audit and rewrite prose so it stops reading as machine-generated. Use this skill when asked to remove AI-isms, clean up AI writing, edit a draft for AI tells, audit a README, changelog, release note, PR description, or blog post for machine-sounding prose, or make text sound less like AI. Supports a detect-only mode, a rewrite mode, and an edit-in-place mode, with optional voice and context profiles.
Automated Cherry Studio review for local branches, PRs, commits, files, architecture docs, and repository skills. Use for code or documentation reviews that need project-specific naming, main/renderer/shared placement and dependency rules, IpcApi and DataApi boundaries, lifecycle/service ownership, renderer hooks, React/UI conventions, and tests. Supports single-agent review with interactive fix selection or multi-agent reviewer-verifier review with risk-based auto-fix. To diagnose gaps in the skill after a review session, run `/gh-pr-review diag`.
This skill should be used when the user asks to "create AGENTS.md", "update AGENTS.md", "maintain agent docs", "set up CLAUDE.md", or needs to keep agent instructions concise. Enforces research-backed best practices for minimal, high-signal agent documentation.
Rewrite text that sounds AI-generated while keeping the writer's facts, meaning, and voice. Use when editing or reviewing prose for inflated claims, sales language, vague sources, repetitive structure, stock AI words, passive voice, filler, or chatbot artifacts. Based on Wikipedia's "Signs of AI writing."