csp-source-driven-developmentlisted

| Tier | Source Type | Examples | |------|-------------|----------| | 1 | Official documentation | react.dev, docs.djangoproject.com, symfony.com/doc | | 2 | Official blog / changelog | react.dev/blog, nextjs.org/blog | | 3 | Web standards references | MDN, web.dev, html.spec.whatwg.org | | 4 | Browser/runtime compatibility | caniuse.com, node.green | **Not authoritative — never cite as primary sources:** - Stack Overflow answers - Blog posts or tutorials (even popular ones) - AI-generated documentation or summaries - Your own training data (that is the whole point — verify it) **Be precise with what you fetch:** ``` BAD: Fetch the React homepage GOOD: Fetch react.dev/reference/react/useActionState BAD: Search "django authentication best practices" GOOD: Fetch docs.djangoproject.com/en/6.0/topics/auth/ ``` After fetching, extract the key patterns and note any deprecation warnings or migration guidance. When official sources conflict with each other (e.g. a migration guide contradicts the API reference), surface the discrepancy to the user and verify which pattern actually works against the detected version. ### Step 3: Implement Following Documented Patterns Write code that matches what the documentation shows: - Use the API signatures from the docs, not from memory - If the docs show a new way to do something, use the new way - If the docs deprecate a pattern, don't use the deprecated version - If the docs don't cover something, flag it as unverified **When docs