source-driven-development

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

Verify framework-specific implementation decisions against official documentation with source citations.

Updated May 3, 2026

Search Tags:#best practices #versioning #documentation #api #frameworks #verification #citations

Ready to run

npx skills add https://github.com/kevindree/geehoo-gateway --skill source-driven-development-kevindree

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: source-driven-development
Source: https://github.com/kevindree/geehoo-gateway/tree/main/.github/skills/source-driven-development
Command: npx skills add https://github.com/kevindree/geehoo-gateway --skill source-driven-development-kevindree

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill keeps implementation decisions grounded in official documentation so you avoid outdated APIs, incorrect patterns, and unsupported assumptions.

Core Features & Use Cases

Detects the project stack and version from dependency files before coding.
Guides you to fetch the most relevant official docs for the exact feature you need.
Helps you implement framework-specific code, surface conflicts, and cite authoritative sources.
Use it when building boilerplate, reviewing framework code, or modernizing patterns that may have changed.

Quick Start

Use the source-driven-development skill to verify the correct documented approach for this feature and return implementation guidance 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 verify framework-specific code against official documentation?▼

To verify framework-specific code against official documentation, inspect dependency files to detect the exact project stack and version, then fetch targeted official docs to guide the implementation and cite authoritative sources.

What is the best way to prevent outdated API usage when modernizing existing code?▼

Preventing outdated API usage when modernizing existing code requires dependency inspection to determine the exact framework version, followed by looking up relevant official documentation to validate implementation patterns and surface version conflicts.

How do I build framework boilerplate without unsupported code assumptions?▼

Building framework boilerplate without unsupported code assumptions involves detecting the project version from dependency files, fetching the most relevant official documentation for the exact feature, and explicitly handling any unverified patterns during implementation.

Why does framework-specific logic fail after a version upgrade?▼

Framework-specific logic fails after a version upgrade when implementation decisions are not grounded in official documentation, leading to the use of deprecated APIs, incorrect patterns, and unsupported assumptions from previous versions.

Can I review framework-specific code for unsupported patterns using source citations?▼

Reviewing framework-specific code for unsupported patterns using source citations is possible by inspecting project dependencies, looking up the exact official documentation for the detected version, and explicitly flagging any unverified code patterns.

When do I need to check official documentation for version-sensitive development tasks?▼

Checking official documentation for version-sensitive development tasks is needed when building boilerplate, modernizing existing code, or reviewing framework-specific logic to ensure all implementation decisions remain grounded and avoid incorrect patterns.