Source Driven Development

This tackles the problem of writing framework code from stale training data by forcing every implementation decision to trace back to official documentation. It detects your stack versions from dependency files, fetches the specific docs pages for what you're building, then implements using current patterns with inline citations. The workflow is detect, fetch, implement, cite. Use it when framework correctness matters: forms, auth, routing, anything that'll become a template others copy. It won't let you ship a deprecated React pattern just because it feels familiar, and it surfaces version conflicts between docs and existing code instead of silently picking one. The citation overhead pays off when you avoid debugging phantom APIs that changed two versions ago.