<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Prompt Engineering on Jamie Ede</title>
    <link>https://www.jamieede.com/tags/prompt-engineering/</link>
    <description>Recent content in Prompt Engineering on Jamie Ede</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 21 May 2026 12:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.jamieede.com/tags/prompt-engineering/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Docs-only guardrails when RAG retrieval finds nothing</title>
      <link>https://www.jamieede.com/posts/docs-only-guardrails-empty-rag-retrieval/</link>
      <pubDate>Thu, 21 May 2026 12:00:00 +0000</pubDate>
      <guid>https://www.jamieede.com/posts/docs-only-guardrails-empty-rag-retrieval/</guid>
      <description>&lt;p&gt;When &lt;a href=&#34;https://www.jamieede.com/astra-chat&#34; &gt;Astra Docs Chat&lt;/a&gt;&#xA; cannot find relevant chunks in Astra DB, the model may still answer from general knowledge: confident, plausible, and sometimes wrong for Astra-specific APIs. The parent post flagged tightening this with a stricter &amp;ldquo;docs only&amp;rdquo; prompt. This post covers practical guardrails at the prompt, retrieval, flow, and UX layers.&lt;/p&gt;&#xA;&lt;p&gt;Context: &lt;a href=&#34;https://www.jamieede.com/posts/building-astra-docs-chat-rag-over-datastax-on-langflow-and-cloudflare-pages/&#34; &gt;Building Astra Docs Chat&lt;/a&gt;&#xA;&lt;/p&gt;&#xA;&lt;p&gt;Related: &lt;a href=&#34;https://www.jamieede.com/posts/langflow-rag-astra-db-ingest-and-chat-flows/&#34; &gt;Langflow chat flow&lt;/a&gt;&#xA; · &lt;a href=&#34;https://www.jamieede.com/posts/streaming-chat-ui-hugo-without-react/&#34; &gt;Streaming chat UI&lt;/a&gt;&#xA;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Status:&lt;/strong&gt; planned for v2; not deployed in current production chat.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
