source-driven-development
Verifies every framework-specific implementation decision against official documentation before writing code, citing sources and avoiding outdated or deprecated patterns.
What it does
Grounds every implementation decision in official documentation. Use when you want to verify an approach against the official docs before implementing it, or when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters.
Quality judgment
Exceptionally thorough: clear process pipeline, source hierarchy, explicit anti-patterns, rationalization table, verification checklist, and prompt-injection hygiene for fetched docs. Concrete examples (React 19 useActionState, Django auth) ground the abstract process. Trigger conditions are well-scoped with useful 'when NOT to use' guidance; only minor deduction for examples being concentrated in one ecosystem.