Source Driven Development
Ground framework, SDK and API code in the current official docs before writing it, and cite them. Use before code against an external package, CLI or cloud API, when reviewing a PR that uses one, or before stating a version, price, model fact or security advisory.
Install
/plugin marketplace add frankxai/claude-skills-libraryThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add frankxai/claude-skills-library --skill source-driven-developmentgit clone --depth 1 https://github.com/frankxai/claude-skills-library.git /tmp/claude-skills-library
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills-library/absorbed/engineering/source-driven-development ~/.claude/skills/source-driven-developmentPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Source-driven development Memory goes stale and the estate has paid for it: three Next.js security PRs cited advisories that do not exist, and public pages carried invented benchmarks. On this machine a framework or API claim is either checked against its source today or marked unverified. ## When it applies - Writing or reviewing code against a library, SDK, CLI or cloud API (Next.js, Cloudflare Workers, Supabase, Stripe or Polar, Vercel, MCP servers). - Stating a version, price, quota, model capability or deprecation. - Citing a CVE or GitHub security advisory. Skip it for pure logic, renames and moves where no version matters. ## The loop 1. **Pin the version.** Read the lockfile or manifest (`pnpm-lock.yaml`, `package.json`, `pyproject.toml` with `uv.lock`, `wrangler.toml`). Write down what you found. If the version is missing, say so instead of picking one. 2. **Fetch the exact page, in spend order.** Context7 first (already paid). Then the vendor docs page with the built-in fetch tool. A metered connector only after naming the built-in call that failed. Fetch the page for the API you are using, not the homepage. 3. **Rank sources.** Official reference beats official changelog or blog, which beats web standards (MDN), which beats compatibility tables. Stack Overflow, tutorials, AI summaries and your own recall are leads, never citations.
Details
- Skill name
source-driven-development- Repository
- frankxai/claude-skills-library
- Path
absorbed/engineering/source-driven-development/SKILL.md- License
- MIT
- Repo updated
- 18 November 2026
FAQ
What does the Source Driven Development skill do?
Ground framework, SDK and API code in the current official docs before writing it, and cite them. Use before code against an external package, CLI or cloud API, when reviewing a PR that uses one, or before stating a version, price, model fact or security advisory.
How do I install the Source Driven Development skill?
Claude Code plugin: /plugin marketplace add frankxai/claude-skills-library. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Source Driven Development popular?
It lives in frankxai/claude-skills-library, which has 48 GitHub stars and 6 forks.
Related skills
Acos Meta
48frankxai/claude-skills-library
ACOS self-description and configuration skill. Documents how ACOS works, how to extend it, how to add new skills/commands/agents, and how to debug the hook system. Use when building new ACOS capabilities, understanding the system architecture, or onboarding to ACOS for the first time.
Acos Visual Gen
48frankxai/claude-skills-library
Generate research-grounded visuals using the InfoGenius pipeline. Use when creating infographics, diagrams, educational visuals, or any image that benefits from factual accuracy. Supports 8 visual styles (3D, technical, minimalist, photorealistic, futuristic, vintage, cartoon, standard) and 4 audience levels.
Agent Harness Construction
48frankxai/claude-skills-library
Shape an agent's tools, observations, and recovery without adding a second coordinator. Use when defining a tool, a skill, a hook, or a worktree lane.
Sparc Methodology
48frankxai/claude-skills-library
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) development methodology with multi-agent orchestration. Use when running a structured spec-to-code workflow or decomposing a feature through the SPARC phases.
Performance Analysis
48frankxai/claude-skills-library
Performance analysis, bottleneck detection, and optimization recommendations. Use when profiling slow code or systems, hunting a performance regression, or producing an optimization plan with measurable targets.
Systematic Debugging
430xranx/agentbrief
Structured methodology for finding root causes before writing fixes
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.