source-driven-development

Implements framework code verified against official documentation with cited sources.

Updated Sep 5, 2026
One-click install
npx skills add https://github.com/nntoan/ultra-omp --skill source-driven-development-nntoan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: source-driven-development
Source: https://github.com/nntoan/ultra-omp/tree/main/packages/proflow/skills/source-driven-development
Command: npx skills add https://github.com/nntoan/ultra-omp --skill source-driven-development-nntoan

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 framework-specific 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, composer.json, 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, and avoids deprecated patterns. - Source Citation: Adds full-URL citations in code comments and conversation, and explicitly flags anything that could not be verified. - 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 source instead of relying on a possibly outdated useState approach. ## Quick Start Ask the assistant to implement a framework-specific feature using source-driven development so every pattern is verified against the official documentation for your detected versions.

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 best practices?▼

Detect exact versions from the project's dependency file, fetch the relevant official documentation page, and implement the documented API signatures. Cite full URLs in code comments so every pattern can be verified against the source.

How to avoid using deprecated APIs when coding with React or Django?▼

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 framework documentation?▼

Official documentation sites come first, followed by official blogs and changelogs, then web standards references like MDN, and compatibility tables like caniuse.com. Stack Overflow answers, blog posts, and training data are never cited as primary sources.

When should I not verify code against documentation?▼

Skip verification when correctness does not depend on a specific version, such as renaming variables or moving files, and for pure logic like loops and data structures that works identically across versions. Also skip it when the user explicitly prioritizes speed over verification.

What happens when documentation conflicts with existing project code?▼

The conflict is surfaced to the user with both options explained: adopt the modern documented pattern or stay consistent with the existing codebase. The Skill never silently picks one approach over the other.