source-driven-development

To verify framework patterns against official documentation, identify the exact framework versions from your dependency file, fetch the matching official docs, implement the documented APIs exactly, and cite the source URLs for each decision to maintain a verification trail.

Framework code uses deprecated patterns when implemented from memory without verification. Detecting exact versions from your dependency file and fetching the corresponding official documentation prevents using incorrect or outdated API patterns.

Detecting framework versions requires analyzing your project's dependency file. Once exact versions are identified, fetch the specific official documentation for each pattern, implement the code accordingly, and attach full URL citations to maintain a verification trail.

The best way to surface conflicts between official documentation and existing code is to fetch the specific docs for your detected framework versions, compare them against current implementations, and explicitly reveal discrepancies to guide resolution.

Source-driven development works with any framework specified in a dependency file. It identifies the framework and exact versions from your project dependencies, fetches the specific official documentation for each pattern, and implements the code accordingly with source citations.

Documentation citations for framework-specific code decisions are needed when grounding implementations in official documentation. Fetching version-specific docs and citing sources prevents deprecated or incorrect patterns, ensuring every framework-specific decision is verified and traceable.