source-driven-development

To ensure code matches official documentation, this Skill analyzes dependency files to detect your active framework stack and versions, then fetches official docs to implement code with explicit citations and flag any conflicts with existing code.

Source-driven development is a practice that grounds implementation decisions in official documentation by fetching exact API signatures and usage examples, ensuring your codebase remains free from outdated or deprecated patterns.

You can detect your project stack and fetch official docs by analyzing dependency files to identify active framework versions, then extracting precise API signatures and usage examples to anchor subsequent code generation.

Yes, this approach works with any framework or library where correctness matters. It detects the specific stack and versions from your dependency files to fetch the precise official documentation for that exact environment.

The best way to handle documentation gaps is to flag conflicts between official docs and existing code automatically, providing explicit guidance on migrations or alternative official patterns to resolve the discrepancies.

Citing official docs when implementing code provides authoritative, source-sited reasoning for every decision. It ensures traceability, prevents outdated patterns, and clarifies exact API signatures for future maintenance.