source-driven-development

To verify framework documentation during refactoring, analyze project dependency files to identify the exact stack version, then cross-reference implementation decisions against official sources. This prevents outdated patterns and ensures code correctness by requiring authoritative citations for every framework-specific pattern used.

Source-driven development is a practice that grounds software implementation decisions in official framework documentation. It eliminates the risk of using hallucinated best practices or outdated training data by requiring dependency analysis and authoritative source verification for feature development and boilerplate generation.

To implement version-aware features with conflicting patterns, identify the project stack and version from dependency files to ensure compatibility. The process surfaces discrepancies between existing codebase patterns and modern official recommendations for user review before proceeding.

Yes, this approach works with specific framework versions like React 19 by automatically identifying the project stack and version from dependency files. It fetches the latest official documentation and cites relevant hooks to ensure version-specific API usage is correct and maintainable.

A limitation of relying on official documentation for boilerplate generation is that it requires dependency analysis and authoritative source verification, which may surface discrepancies between existing codebase patterns and modern recommendations. This forces user review of conflicts rather than automated resolution.