source-driven-development

Verify framework-specific code decisions by reading project dependency files to detect exact versions, fetching the relevant official documentation, and citing full-source URLs for every implementation choice. This ensures code follows documented patterns instead of deprecated APIs.

Preventing deprecated API bugs during web framework development requires checking project dependency files for exact versions and fetching precise official documentation pages before implementing features. This approach avoids memory-based coding errors and undocumented behavior.

To implement an authenticated React form handler, read the project's package.json to detect the exact React version, fetch the current official docs for that version, and write code following the documented lifecycle patterns with full API reference URLs.

Yes, documentation verification works for routing, state management, data fetching, forms, and authentication tasks. It applies to framework and library development by reading dependency files, fetching authoritative docs, and citing full-source URLs for every framework-specific decision.

You need to cite official documentation URLs in code review for every non-obvious framework-specific decision. This includes routing, state management, data fetching, forms, and authentication patterns where exact versions determine the recommended API.

Memory-based coding introduces bugs in framework development because stale training data leads to using deprecated APIs, migration mismatches, and undocumented behavior. Verifying against official dependency-aware documentation prevents these errors from propagating into production code.