Source-driven development
Use when an approach should be grounded in official documentation, not remembered patterns.
--- name: source-driven-development description: Grounds every implementation decision in official documentation. Use when you want to verify an approach against the official docs before implementing it, or when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters. ---