source-driven-development

Preventing outdated framework-specific code requires grounding implementation choices in official documentation by detecting exact library versions from dependency manifests, fetching authoritative pages, and requiring full-URL citations for every non-obvious decision.

When versions are missing or ambiguous in dependency manifests, version-aware guardrails ask the user instead of guessing, ensuring the agent fetches documentation matching the exact detected library version before implementing patterns.

A four-tier source hierarchy prioritizes official documentation first, then official blog and changelog entries, followed by web standards, and finally compatibility references like caniuse, ensuring implementation decisions rely on the most authoritative framework sources available.

When documentation cannot be found to verify a framework-specific implementation decision, the process requires applying explicit unverified flags to surface the gap, ensuring the user knows which code lacks authoritative documentation backing.

For known domains like Supabase, Neon, or Langfuse, vendor authority deferral skips fetching generic sources and instead routes implementation decisions to the corresponding specialized authority skills to ensure framework-specific code matches vendor standards.

To start building framework code only from official docs, tell your agent to detect your stack from package.json or pyproject.toml, fetch exact official documentation pages, implement the documented approach, and include full-URL citations for each non-obvious decision.