source-driven-development

To prevent deprecated code patterns during framework refactoring, ground implementation decisions in official, version-specific documentation to ensure code correctness and maintainability. This approach requires dependency detection and authoritative source verification to avoid hallucinated APIs.

Source-driven development for API stability is a technique that forces the AI to ground every framework-specific coding decision in official documentation. It verifies authoritative sources to prevent the use of outdated or hallucinated APIs, ensuring code correctness.

To implement code matching current framework version best practices, use version-aware implementation that automatically detects project dependencies. This ensures code matches the specific framework version in use and requires authoritative citation for every framework-specific decision.

Yes, you can use official documentation citations to resolve codebase conflicts during verification. This process surfaces discrepancies between existing codebase patterns and modern documentation, allowing you to make informed architectural choices.

Yes, authoritative source verification applies to all framework-specific coding tasks where API stability and best practices are critical. It requires dependency detection and direct links to official documentation to verify code correctness.