source-driven-development

To ensure code uses official framework documentation, this skill forces every implementation decision to be grounded in version-verified source material, systematically detecting project dependencies to fetch authoritative references and eliminate outdated patterns.

The best way to prevent hallucinated APIs during framework implementation is to use an evidence-based coding approach that requires explicit citations from official, version-specific documentation for every non-trivial code pattern generated.

To resolve discrepancies between existing codebase patterns and modern best practices, this skill identifies conflicts between current implementations and official recommendations, allowing you to make informed architectural decisions based on verified documentation.

Yes, you can automatically detect project dependencies to enforce version-aware coding, ensuring that all generated framework-specific code matches the exact version currently in use within your software engineering environment.

Generated code includes deprecated framework functions when it relies on outdated training data rather than current official documentation; requiring version-verified source material for all implementation decisions prevents this issue.

You need to verify framework-specific code patterns against official source material whenever correctness, modern best practices, and maintainability are critical, applying this to every non-trivial code pattern in your software engineering tasks.