source-driven-development

Verifying code implementation against official documentation requires identifying precise questions, detecting stack versions, retrieving authoritative references, and tracking citations before writing code to prevent outdated patterns.

Avoiding outdated framework knowledge requires applying a source-driven workflow that evaluates source hierarchies, detects version-specific behavior, and verifies official references to ground implementation decisions in authoritative documentation.

Researching version-specific approaches for external APIs involves detecting the active version, retrieving official API documentation, and establishing citation practices with explicit uncertainty handling to ensure traceable implementation references.

Yes, you can use source-driven development for unfamiliar libraries by applying a source verification workflow to retrieve official documentation, evaluate source hierarchies, and implement features with traceable references.

You should not rely on existing framework knowledge when dealing with version-sensitive behavior, undocumented external APIs, or unfamiliar libraries, as outdated assumptions can cause incorrect technical patterns without authoritative source grounding.