source-driven-development

To verify framework-specific code against official documentation, inspect dependency files to detect the exact project stack and version, then fetch targeted official docs to guide the implementation and cite authoritative sources.

Preventing outdated API usage when modernizing existing code requires dependency inspection to determine the exact framework version, followed by looking up relevant official documentation to validate implementation patterns and surface version conflicts.

Building framework boilerplate without unsupported code assumptions involves detecting the project version from dependency files, fetching the most relevant official documentation for the exact feature, and explicitly handling any unverified patterns during implementation.

Framework-specific logic fails after a version upgrade when implementation decisions are not grounded in official documentation, leading to the use of deprecated APIs, incorrect patterns, and unsupported assumptions from previous versions.

Reviewing framework-specific code for unsupported patterns using source citations is possible by inspecting project dependencies, looking up the exact official documentation for the detected version, and explicitly flagging any unverified code patterns.

Checking official documentation for version-sensitive development tasks is needed when building boilerplate, modernizing existing code, or reviewing framework-specific logic to ensure all implementation decisions remain grounded and avoid incorrect patterns.