source-driven-development

Ground implementation decisions on official documentation with verifiable citations.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Coldaine/agent-skills-vscode --skill source-driven-development-coldaine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: source-driven-development
Source: https://github.com/Coldaine/agent-skills-vscode/tree/main/skills/source-driven-development
Command: npx skills add https://github.com/Coldaine/agent-skills-vscode --skill source-driven-development-coldaine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifies that implementation decisions are grounded in current, official documentation, preventing reliance on outdated patterns or memory-based heuristics and ensuring verifiable sources are available for review.

Core Features & Use Cases

  • Authoritative decisions: every code pattern is backed by official docs with explicit citations.
  • Version-aware guidance: detects dependency versions and validates patterns against the correct docs.
  • Audit-ready outputs: surfaces sources in code comments and user-facing guidance for traceability.

Quick Start

Fetch the relevant official documentation for your framework and implement code that matches the documented patterns with citations.

Frequently Asked Questions about source-driven-development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I ensure my code patterns match official framework documentation?

Source-driven development grounds implementation decisions in official documentation by fetching authoritative docs, extracting framework patterns, and surfacing verifiable citations directly in code comments and user-facing guidance.

Can I validate framework patterns against the specific dependency versions in my project?

Version detection validates framework patterns against correct official documentation by identifying dependency versions in your project, ensuring code patterns for forms, routing, and auth match the right docs.

What is the best way to add citations for code quality and framework patterns?

Adding citations for code quality involves extracting documented framework patterns and embedding explicit source references in code comments, creating audit-ready outputs that trace implementation decisions back to official documentation.

How do I stop relying on outdated memory-based heuristics for library implementations?

Preventing reliance on outdated patterns requires fetching current official documentation for your specific framework or library, validating implementation decisions against those sources, and providing verifiable citations for every code pattern.

Does source-driven development work for data fetching and auth implementations?

Source-driven development applies across framework-specific coding tasks including data fetching, auth, forms, and routing, ensuring every implementation decision is backed by current official sources with explicit verifiable citations.