source-driven-development

The source-driven-development skill ensures that implementation decisions are grounded in authoritative documentation rather than assumptions or outdated knowledge. It addresses a common problem in software development: frameworks, libraries, and best practices evolve rapidly, while code written from memory often reflects obsolete APIs or deprecated patterns. Instead of relying on historical knowledge alone, this skill requires verification against official sources before implementation. The goal is to produce code that is trustworthy, traceable, and aligned with the intended behavior of the technologies being used.

The skill provides a structured workflow centered around detecting the technology stack, identifying exact framework versions, retrieving the most relevant official documentation, and implementing code according to documented patterns. It prioritizes authoritative sources such as official documentation, official blogs and changelogs, web standards references, and compatibility references. The process emphasizes precision by requiring feature-specific documentation instead of broad searches. It also highlights version-sensitive behavior, warns against ambiguity, surfaces documentation conflicts when they occur, and encourages source citation so users can verify implementation decisions themselves.

This skill is useful for developers building production applications, creating reusable project templates, implementing framework-specific features, or reviewing code quality. It is particularly valuable when correctness and long-term maintainability are important, such as when building boilerplate structures, authentication systems, routing logic, state management workflows, or framework-driven application patterns. Teams, technical reviewers, and developers who need transparent and verifiable implementation decisions benefit most from its approach.