<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Chris Bora</title>
    <description>The latest articles on DEV Community by Chris Bora (@cbora).</description>
    <link>https://dev.to/cbora</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3376365%2F80f14d7c-3569-4208-8917-167f0d9336f4.jpeg</url>
      <title>DEV Community: Chris Bora</title>
      <link>https://dev.to/cbora</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/cbora"/>
    <language>en</language>
    <item>
      <title>Beyond Prompting: A Framework for Building Reliable AI Systems</title>
      <dc:creator>Chris Bora</dc:creator>
      <pubDate>Tue, 22 Jul 2025 16:57:59 +0000</pubDate>
      <link>https://dev.to/cbora/beyond-prompting-a-framework-for-building-reliable-ai-systems-295i</link>
      <guid>https://dev.to/cbora/beyond-prompting-a-framework-for-building-reliable-ai-systems-295i</guid>
      <description>&lt;p&gt;As developers, we're all excited by the speed that LLMs offer. But anyone who has tried to build a production-grade feature with them has likely run into a hard truth: they are fundamentally unreliable.&lt;/p&gt;

&lt;p&gt;After building three separate AI apps, I found myself spending more time debugging AI hallucinations than writing my own code. I realized we need to move beyond "prompt engineering" and towards a more structured "Intent Engineering."&lt;/p&gt;

&lt;p&gt;I want to share a simple, pragmatic framework that has saved me countless hours and made my AI-generated code dramatically more robust. I call it WBS: What-Boundaries-Success.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The Problem:&lt;/strong&gt; A vague prompt like "build a login endpoint" forces the AI to guess at a dozen critical details.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The WBS Framework:&lt;/strong&gt; Instead, you provide a structured spec:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. What (The Intent):&lt;/strong&gt;&lt;br&gt;
    - "Handle user login with email/password."&lt;br&gt;
    - "Issue a JWT on success."&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Boundaries (The Constraints):&lt;/strong&gt;&lt;br&gt;
    - "Must use bcrypt for password hashing."&lt;br&gt;
    - "Max 5 login attempts per IP per hour."&lt;br&gt;
    - "Do not expose user PII in error logs."&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Success (The Verifiable Outcome):&lt;/strong&gt;&lt;br&gt;
    - "A valid login returns a 200 with a JWT."&lt;br&gt;
    - "An invalid login returns a 401."&lt;br&gt;
    - "The 6th attempt from an IP within an hour returns a 429."&lt;/p&gt;

&lt;p&gt;By defining the solution space before generation, you're not just hoping for a good result; you're engineering one. You're giving the AI a "reasoning layer."&lt;/p&gt;

&lt;p&gt;I wrote a much deeper post about the journey that led me to this framework and the bigger theories behind it (like the "Reasoning Ceiling" and "Bora's Law").&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;You can read the full story and theory here:&lt;/strong&gt; &lt;a href="https://chrisbora.substack.com/p/how-i-vibe-coded-3-saas-apps-with" rel="noopener noreferrer"&gt;https://chrisbora.substack.com/p/how-i-vibe-coded-3-saas-apps-with&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I'm now building this framework into a full-fledged tool called The ReasoningAPI. Hope this framework is useful for your own projects!&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
