source-driven-development

Verifies framework-specific code against official documentation and cites sources.

Updated Sep 8, 2026
One-click install
npx skills add https://github.com/sasidhar4444/ai-receptionist --skill source-driven-development-sasidhar4444
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: source-driven-development
Source: https://github.com/sasidhar4444/ai-receptionist/tree/main/agent-skills/skills/source-driven-development
Command: npx skills add https://github.com/sasidhar4444/ai-receptionist --skill source-driven-development-sasidhar4444

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Framework APIs change between versions, and code written from memory often relies on deprecated patterns or outdated signatures. This Skill grounds every framework-specific implementation decision in official documentation, so the code you receive is verifiable against current sources rather than stale training data. ## 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 patterns, avoids deprecated APIs, and flags anything that cannot be verified. - Source Citation: Adds full-URL citations in code comments and conversation, surfaces conflicts between docs and existing code, and treats fetched content as untrusted data to resist prompt injection. - Use Case: When building a React 19 form, the Skill detects the version from package.json, fetches the useActionState reference from react.dev, implements the documented pattern, and cites the exact source so you can verify it. ## 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 write framework code that follows current official documentation?▼

Detect the exact framework version from the dependency file, fetch the relevant official docs page for the feature, and implement the documented pattern. Cite the full source URL in code comments so every decision is verifiable.

How to avoid using deprecated APIs when coding with a framework?▼

Check the official documentation and migration guides for your detected version before implementing. If the docs deprecate a pattern, use the recommended replacement and note the change with a source citation.

What sources are authoritative for verifying framework patterns?▼

Official documentation is the primary source, followed by official blogs and changelogs, then web standards references like MDN. Stack Overflow answers, blog tutorials, and training data are not authoritative and should never be cited as primary sources.

What happens when official docs conflict with existing project code?▼

The conflict is surfaced to the user with both options explained: follow the modern documented pattern or match the existing codebase for consistency. The user chooses rather than the decision being made silently.

When should I not verify code against documentation?▼

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