<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
    <channel>
        <title>AI Programming - Tag - Daily Deep Think</title>
        <link>https://blog.baifan.site/en/tags/ai-programming/</link>
        <description>AI Programming - Tag - Daily Deep Think</description>
        <generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>blog@baifan.site (ByF)</managingEditor>
            <webMaster>blog@baifan.site (ByF)</webMaster><lastBuildDate>Tue, 17 Feb 2026 14:00:00 &#43;0800</lastBuildDate><atom:link href="https://blog.baifan.site/en/tags/ai-programming/" rel="self" type="application/rss+xml" /><item>
    <title>A New Playbook for AI Programming: UI First, Then the PRD</title>
    <link>https://blog.baifan.site/en/ui-first-ai-programming-prd/</link>
    <pubDate>Tue, 17 Feb 2026 14:00:00 &#43;0800</pubDate><author>
                    <name>ByF</name>
                </author><guid>https://blog.baifan.site/en/ui-first-ai-programming-prd/</guid>
    <description><![CDATA[<div class="featured-image">
                <img src="/pictures/note/ui-first-ai-featured.svg" referrerpolicy="no-referrer">
            </div><!-- more -->
<p>Everyone knows the standard Vibe Coding flow by now: write user stories → produce a PRD → AI generates the backend → AI generates the frontend → demo and verify. It works, but at delivery time the UI interaction experience often falls far short of expectations. Where does it go wrong? In the PRD itself.</p>
<h2 id="1-the-fundamental-problem-with-prds" class="headerLink">
    <a href="#1-the-fundamental-problem-with-prds" class="header-mark"></a>1. The Fundamental Problem with PRDs</h2><p>PRDs (Product Requirements Documents) were never that friendly to humans in the first place. Three reasons:</p>]]></description>
</item>
</channel>
</rss>
