skills.rest
ToanPV90
ToanPV90COMMUNITY
Explore all skills by this author →
GitHub

source-driven-development

Detect stack versions and verify framework patterns against official documentation.

Updated Apr 15, 2026
Search Tags:#authentication#routing#Context7 MCP#official documentation#framework patterns#version detection#code citations
One-click install
npx skills add https://github.com/ToanPV90/dotfiles --skill source-driven-development-toanpv90
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: source-driven-development
Source: https://github.com/ToanPV90/dotfiles/tree/main/claude/.claude/skills/source-driven-development
Command: npx skills add https://github.com/ToanPV90/dotfiles --skill source-driven-development-toanpv90

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents incorrect or outdated framework-specific code by forcing every implementation decision to be validated against official documentation instead of relying on memory or stale training data.

Core Features & Use Cases

  • Version-aware stack detection: Reads dependency files to identify the exact framework/library versions before making any recommendations.
  • Authoritative documentation fetching: Uses Context7 MCP (or official-doc web fallbacks) to retrieve the relevant patterns directly from primary sources.
  • Conflict surfacing and citation enforcement: Requires full, linkable citations and explicitly highlights mismatches between existing code patterns and current docs.
  • Unverified-by-default behavior: Flags anything not found in authoritative sources rather than guessing.

Use cases: implementing framework-specific forms, routing, data fetching, state management, and authentication patterns when correctness depends on current “documented” guidance.

Quick Start

Ask the AI to implement your feature using source-driven development and include official doc citations for every framework-specific pattern, starting by detecting your stack versions from your dependency files.

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 framework-specific code matches official documentation?▼

Framework-specific code matches official documentation by detecting exact stack versions from dependency files and validating patterns against primary sources using Context7 MCP. It enforces citation-first behavior, surfacing conflicts between existing code and current docs while flagging unknowns as unverified.

What is source-driven development for framework patterns?▼

Source-driven development is a technique that prevents incorrect or outdated framework code by validating implementation decisions against official documentation. It applies to forms, routing, data fetching, state management, and authentication where API behavior changes across versions.

Can I use Context7 MCP to verify routing and authentication patterns?▼

Yes, Context7 MCP verifies routing and authentication patterns by retrieving guidance directly from official documentation. If unavailable, precise official-doc web fallbacks fetch authoritative patterns for your exact framework versions.

Do I need Context7 MCP to detect stack versions for source-driven development?▼

No, stack version detection reads dependency files directly to identify exact framework and library versions. Context7 MCP is required separately for authoritative documentation fetching and citation enforcement, with official-doc web fallbacks available.

Why does framework-specific code break after library updates?▼

Framework-specific code breaks after library updates because API behavior and best practices change across versions, causing outdated patterns to fail. Source-driven development prevents this by detecting exact stack versions and verifying patterns against current official documentation.

What are the limitations of relying on training data for framework patterns?▼

Relying on training data for framework patterns risks generating incorrect or outdated code because stale data does not reflect current API behavior. Source-driven development overcomes this by flagging anything not found in authoritative sources as unverified rather than guessing.

Related Skills

Explore More Software Engineering Skills→
LauughterLauughter

source-driven-development

Detects dependency manifest versions and implements patterns from official docs with source citations.

Community
Advanced
luyzkkluyzkk

source-driven-development

Validate framework code against official documentation for detected versions.

Community
Advanced
LazyIsEfficientLazyIsEfficient
15

source-driven-development

Identify framework versions from dependency files and verify code against official documentation.

Official
Intermediate
motoki317motoki317
4

Fact Check

Verify user claims against Context7 and web sources, producing discrepancy reports.

Community
Advanced