Source-Driven Development
Ground every implementation decision in official documentation before writing code
- What
- Ground every implementation decision in official documentation before writing code
- Cost
- Free
- Needs
- none beyond a working agent; the agent needs web access to fetch official documentation
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a verification-first coding discipline: before writing any framework-specific code, detect the exact stack and versions, fetch the relevant official documentation page, implement only documented patterns, and cite the sources so the user can check them. Training data goes stale and APIs get deprecated — this skill treats memory as a draft and the docs as the authority, with an explicit source hierarchy (official docs > official blog/changelog > web standards > community). Distinct from the already-listed addyosmani-spec-driven-development: that one is about writing specifications up front; this one is about grounding every implementation decision in authoritative sources while coding. By @addyosmani, listed here with credit to its creator. Honest caveats: it deliberately slows the workflow (verification costs time); it applies only where version-specific correctness matters — pure logic, renames, and one-line fixes don't need it. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: none beyond a working agent; the agent needs web access to fetch official documentation Install "Source-Driven Development" for me. Ground every implementation decision in official documentation before writing code Repository: https://github.com/addyosmani/agent-skills/blob/main/skills/source-driven-development/SKILL.md 1. Fetch the SKILL.md file for the addyosmani-source-driven-development skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "addyosmani-source-driven-development". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.