source-driven-development

You validate code patterns against official documentation by parsing dependency manifests to detect exact versions, fetching the relevant official docs, implementing patterns per the docs, and providing explicit source citations to ensure code decisions can be audited against canonical sources.

Source-driven development is an approach that grounds all implementation decisions with official documentation to prevent outdated patterns. You need it across any framework or library where correctness matters, including boilerplate generation, review of framework-specific patterns, and version migrations.

Detecting exact framework versions from dependency manifests involves parsing the dependency files in your project to identify the precise versions installed. This version detection guides accurate references to official documentation for implementation and review.

Yes, you can use source-driven development for framework version migrations. Its scope explicitly covers version migrations across any framework or library, using version detection from manifests to fetch the exact official docs and implement migration patterns with explicit citations.

Preventing outdated code patterns across different frameworks is best achieved by enforcing source-driven development, which validates code decisions against primary sources. This framework-agnostic approach requires fetching official docs for your exact versions and implementing patterns with explicit source citations.