source-driven-development

To verify framework patterns against official documentation, detect the framework stack from dependency files, fetch precise docs pages, and extract cited guidance for implementation. This ensures every coding decision is backed by current official docs.

The best way to prevent outdated framework patterns is to apply only patterns that match current official docs. Enforce sourcing from authoritative documentation before coding to eliminate unverified assumptions and deprecated syntax.

To cite official documentation sources in code comments, fetch the precise docs pages for your framework stack and extract cited guidance during implementation. This creates consistent, citable references across projects and teams.

When codebase patterns conflict with official framework documentation, surface the discrepancies for user decision. Ensure all implementation decisions are documented with citations to maintain accuracy and traceability.

To detect the framework stack from dependency files, parse project manifests to identify the exact technologies in use. This automatically anchors subsequent implementation steps to the correct official documentation.

Source-driven development works without external dependencies, relying entirely on detecting the framework stack from your local dependency files and fetching the corresponding official documentation pages for verification.