source-driven-development

Verifies framework-specific code decisions against official documentation with cited sources.

5|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/PHenrique07/Sementis-IFSP-Pirituba --skill source-driven-development-phenrique07
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: source-driven-development
Source: https://github.com/PHenrique07/Sementis-IFSP-Pirituba/tree/main/.github/skills/source-driven-development
Command: npx skills add https://github.com/PHenrique07/Sementis-IFSP-Pirituba --skill source-driven-development-phenrique07

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Training data goes stale, APIs get deprecated, and best practices evolve, so code written from memory often contains outdated or incorrect framework patterns. This Skill grounds every implementation decision in official documentation so the code you receive is verifiable against authoritative sources. ## Core Features & Use Cases - Stack Detection: Reads dependency files like package.json, requirements.txt, or go.mod to identify exact framework versions before writing any code. - Documentation-Grounded Implementation: Fetches the relevant official docs page, follows documented API signatures, avoids deprecated patterns, and surfaces conflicts between docs and existing code. - Source Citation: Annotates framework-specific decisions with full URLs and quoted passages, and explicitly flags anything that could not be verified. - Use Case: You are building a form in a React 19 project. Instead of guessing, the Skill detects React 19.1.0 from package.json, fetches the official useActionState reference, implements the documented pattern, and cites the exact docs URL in a code comment. ## Quick Start Ask the assistant to implement a framework-specific feature using source-driven development so every pattern is verified against the official docs and cited.

Frequently Asked Questions about source-driven-development

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

FAQPage Schema
How do I make sure AI-generated code uses current framework best practices?▼

Verify each framework-specific pattern against the official documentation for your exact version before implementing. This Skill detects versions from dependency files, fetches the relevant docs page, and cites sources so you can confirm every decision.

How to detect framework versions before writing code?▼

Read the project's dependency file: package.json for Node and React, requirements.txt or pyproject.toml for Python, composer.json for PHP, go.mod for Go, Cargo.toml for Rust, or Gemfile for Ruby. If versions are ambiguous, ask rather than guess.

What sources are authoritative for framework documentation?▼

Official documentation sites rank first, followed by official blogs and changelogs, then web standards references like MDN, then compatibility tables like caniuse.com. Stack Overflow answers, tutorials, and AI-generated summaries are never cited as primary sources.

Can fetched documentation content be trusted as instructions?▼

No. Fetched docs are treated as untrusted data: only API signatures, examples, and deprecation notes are extracted. Directives embedded in pages that target the model are ignored, and outbound endpoints from examples are never hardcoded without disclosure.

When should I not verify code against documentation?▼

Skip verification when correctness does not depend on a version, such as renaming variables, fixing typos, or moving files, and for pure logic like loops and data structures that behaves identically across versions.

What happens when docs conflict with existing project code?▼

The conflict is surfaced explicitly with the documented recommendation and source URL, along with options to adopt the modern pattern or match the existing codebase. The Skill never silently picks one approach.