source-driven-development

To verify framework patterns against official documentation, fetch current docs, extract the documented patterns, implement accordingly, and surface citations with full URLs for every decision.

Source-driven development resolves every framework-specific pattern strictly from official documentation rather than memory, providing sources for every decision to ensure accuracy and trust.

Yes, documentation-backed implementation is framework-agnostic and applicable across any framework or library where correctness matters, including boilerplate, starter code, and critical features.

To implement boilerplate code with citations, identify the exact versions and official docs for your target stack, implement only patterns shown in the official docs, and attach full citations to every decision.

Outdated code creeps into framework implementations when decisions rely on memory instead of current official documentation, making source-driven verification necessary to prevent deprecated patterns.

The best way to ensure trustworthy code across frameworks is to ground every implementation decision in official documentation with citations, enabling auditable code paths traceable to primary references.