source-driven-development

Name: source-driven-development
Availability: InStock
Author: lauughter

Detects dependency manifest versions and implements patterns from official docs with source citations.

Updated Dec 27, 2025

Search Tags:#documentation #verification #code-quality #framework-agnostic #citation #official-docs #version-detection

Ready to run

npx skills add https://github.com/Lauughter/Python_training --skill source-driven-development-lauughter

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: source-driven-development
Source: https://github.com/Lauughter/Python_training/tree/main/.claude/skills/source-driven-development
Command: npx skills add https://github.com/Lauughter/Python_training --skill source-driven-development-lauughter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Grounds all implementation decisions with official documentation. This approach prevents outdated patterns and ensures code decisions can be audited against canonical sources across any framework or library where correctness matters.

Core Features & Use Cases

Enforces source-driven development by validating code decisions against primary sources.
Detects stack versions from dependency manifests, guiding precise doc references.
Provides end-to-end workflows for researching, implementing, and citing patterns with official sources.

Quick Start

Follow the four-step process: detect the stack and versions from your dependency files, fetch the exact official docs, implement patterns per the docs, and cite your sources.

Frequently Asked Questions about source-driven-development

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

FAQPage Schema

How do I validate code patterns against official documentation?▼

You validate code patterns against official documentation by parsing dependency manifests to detect exact versions, fetching the relevant official docs, implementing patterns per the docs, and providing explicit source citations to ensure code decisions can be audited against canonical sources.

What is source-driven development and when do I need it?▼

Source-driven development is an approach that grounds all implementation decisions with official documentation to prevent outdated patterns. You need it across any framework or library where correctness matters, including boilerplate generation, review of framework-specific patterns, and version migrations.

How do I detect exact framework versions from dependency manifests for documentation references?▼

Detecting exact framework versions from dependency manifests involves parsing the dependency files in your project to identify the precise versions installed. This version detection guides accurate references to official documentation for implementation and review.

Can I use source-driven development for framework version migrations?▼

Yes, you can use source-driven development for framework version migrations. Its scope explicitly covers version migrations across any framework or library, using version detection from manifests to fetch the exact official docs and implement migration patterns with explicit citations.

What's the best way to prevent outdated code patterns across different frameworks?▼

Preventing outdated code patterns across different frameworks is best achieved by enforcing source-driven development, which validates code decisions against primary sources. This framework-agnostic approach requires fetching official docs for your exact versions and implementing patterns with explicit source citations.