source-driven-development

Source-driven development validates framework code by detecting exact library versions from dependency files, then retrieving targeted official documentation pages to verify API signatures and implementation patterns for correctness.

Source-driven development is a technique that validates non-trivial framework-specific code decisions against authoritative documentation for detected versions. Use it during code review to detect deprecated APIs, misapplied patterns, or unverified implementations across ecosystems like React, Vue, Django, and Go.

Yes, you can check for deprecated React or Vue APIs by requiring source citations from official reference pages. The process detects your framework version, retrieves relevant migration guides or API docs, and explicitly flags unverified areas or conflicts in the code.

You ensure implementation matches verified API signatures by locating deep official documentation pages for your detected Django or Symfony version, implementing patterns exactly as shown, and adding verifiable source citations in code comments to confirm correctness.

Yes, source-cited coding works with Rust and Ruby on Rails by reading dependency files such as Cargo.toml or Gemfile to identify exact versions. It then fetches relevant official documentation to validate framework APIs and mark any unverified areas explicitly.

Limitations include the inability to verify logic outside framework APIs, potential gaps in official docs for edge cases, and the need to explicitly flag unverified areas when documentation conflicts arise or when no authoritative source can be found for a specific pattern.