source-driven-development

Validate framework code against official documentation for detected versions.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/luyzkk/Anti-Vibe-Coding --skill source-driven-development-luyzkk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: source-driven-development
Source: https://github.com/luyzkk/Anti-Vibe-Coding/tree/main/skills/source-driven-development
Command: npx skills add https://github.com/luyzkk/Anti-Vibe-Coding --skill source-driven-development-luyzkk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Source-Driven Development prevents framework-specific bugs and deprecated patterns by forcing every non-trivial implementation decision to be backed by official documentation for the exact detected version.

Core Features & Use Cases

  • Doc-anchored implementation: Detects the stack and versions, fetches the relevant official documentation pages, and implements only what the docs specify.
  • Citation-first workflow: Adds full-url citations in code comments and conversation, and explicitly flags anything that cannot be verified as UNVERIFIED.
  • Version-accuracy guardrails: Refuses to guess when versions are ambiguous and surfaces conflicts between existing code and current documentation.

Quick Start

Run the skill to implement a framework-specific change by providing the file or module you want to verify against official docs, for example: "Use source-driven-development to implement and cite the recommended pattern for handling React form submission in src/components/CheckoutForm.tsx."

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 framework implementation follows official documentation?

Source-driven development validates framework-specific code decisions against official documentation for detected versions. It fetches relevant doc pages to ensure implementations use correct, non-deprecated patterns for routing, state management, and data fetching.

What is the best way to avoid deprecated framework patterns during refactoring?

Anchor implementation decisions to official documentation to avoid deprecated framework patterns. By detecting stack versions and fetching corresponding docs, this approach guarantees refactored code uses current, supported patterns and surfaces conflicts with existing code.

How do I add code citations for framework patterns in my project?

Add full-url citations in code comments to reference framework patterns directly from official documentation. This citation-first workflow validates implementation against detected versions and explicitly labels unverifiable code gaps as UNVERIFIED.

Does source-driven development work with ambiguous framework versions?

Source-driven development refuses to guess when framework versions are ambiguous. It applies version-accuracy guardrails that surface conflicts between existing code and current documentation, ensuring only verified patterns are implemented.

Can I use official documentation to verify routing and auth implementation?

Yes, you can verify routing and auth implementation by fetching targeted official documentation pages for your detected framework versions. This ensures features are implemented using correct patterns and adds explicit citations for each decision.