source-driven-development

1# Source-Driven Development
2 
3## Overview
4 
5Every framework-specific code decision must be backed by official documentation. Don't implement from memory — verify, cite, and let the user see your sources. Training data goes stale, APIs get deprecated, best practices evolve. This skill ensures the user gets code they can trust because every pattern traces back to an authoritative source they can check.
6 
7## When to Use
8 
9- The user wants code that follows current best practices for a given framework
10- Building boilerplate, starter code, or patterns that will be copied across a project
11- The user explicitly asks for documented, verified, or "correct" implementation
12- Implementing features where the framework's recommended approach matters (forms, routing, data fetching, state management, auth)
13- Reviewing or improving code that uses framework-specific patterns
14- Any time you are about to write framework-specific code from memory
15 
16**When NOT to use:**
17 
18- Correctness does not depend on a specific version (renaming variables, fixing typos, moving files)
19- Pure logic that works the same across all versions (loops, conditionals, data structures)
20- The user explicitly wants speed over verification ("just do it quickly")
21 
22## The Process
23 
24```
25DETECT ──→ FETCH ──→ IMPLEMENT ──→ CITE
26  │          │           │            │
27  ▼          ▼           ▼            ▼
28 What       Get the    Follow the   Show your
29 stack?     relevant   documented   sources
30            docs       patterns
31```
32…