source-driven-development — make Claude cite the docs

← Skills · From the community

Slash command /source-driven-development

make Claude cite the docs

Forces every framework-specific decision to be checked against official documentation and cited, instead of recalled from training data. Training data goes stale and APIs get deprecated; this makes Claude show you the source so you can check it yourself.

both ⏱ ~2-4 hours per deprecated-API rabbit hole View source ↗

In practice

You ask for an authentication flow using a library Claude knows well — and it writes the version that was correct eighteen months ago, confidently, with no sign anything is wrong. You lose an afternoon to a deprecation warning that turns out to be load-bearing. With this skill, the same request comes back with links to the current official docs beside each decision, and the outdated pattern never gets written.

The failure this fixes is the one most likely to embarrass you: Claude being confidently out of date. Wrong code announces itself. Deprecated-but-working code doesn’t, until it’s in production.

This skill changes the posture. Every framework-specific decision must be backed by official documentation, cited inline, so you can click through and check. Nothing gets implemented from memory.

Why this one matters here

Two reasons specific to us:

1. It is the discipline we already ask of ourselves. This hub has a standing rule that a documented keystroke which does nothing costs more credibility than the missing tip was worth. Same idea, applied to code.
2. Citations are auditable. “Claude said so” is not a defence. A link to the vendor’s current documentation is.

If you read one related tip, make it make Claude prove it — this skill is that instinct, automated and always on.

Worth knowing

• It is slower. Checking sources costs time. That’s the trade, and it’s worth it exactly when correctness beats speed — not on a throwaway script.
• Installing gives you 25 skills, not one. doubt-driven-development on this page is in the same bundle.
• If /plugin install fails with a Permission denied (publickey) error, the marketplace is trying to clone over SSH. Use the HTTPS form instead: /plugin marketplace add https://github.com/addyosmani/agent-skills.git. Worth knowing on a locked-down bank laptop where you may have no SSH key at all.

Access

Public — no access request needed. MIT licensed.

Get this skill running

Copy-paste into Claude Code. The marketplace + install steps run once per machine; the last one is how you call the skill day-to-day.

1. 1 Access

   Public repo — no access request needed.

2. 2 Add the marketplace — once per machine

   /plugin marketplace add addyosmani/agent-skills

3. 3 Install the skill

   /plugin install agent-skills@addy-agent-skills

4. 4 Use it

   /source-driven-development

Next skill →

/teach — a tutor that remembers where you got to

Turns the current folder into a teaching workspace and Claude into a tutor that keeps your progress in files. Learning is treated as a multi-session thing — you can stop, come back next week, and pick up where you left off instead of re-explaining what you already know.

Open it → Back to all skills