source-driven-development

To verify code quality against official documentation, the skill detects project stacks and versions, mapping them to authoritative sources like official docs and language references to mandate citations for technical patterns.

The best way to prevent outdated patterns is source-driven development, which detects project versions and mandates explicit verification of all technical patterns against authoritative sources like official docs and changelogs.

You resolve conflicts by applying a structured framework that cross-references your existing code against official documentation, providing an authoritative path to update outdated technical patterns.

Yes, the source-driven approach works with framework versions like Go and Terraform by automatically detecting the environment versions and mapping them to the matching authoritative documentation.

You should use official documentation instead of third-party tutorials to eliminate the risk of implementing features based on outdated patterns or memory, ensuring all technical patterns are explicitly verified against authoritative sources.