<?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: Harish .s</title>
    <description>The latest articles on DEV Community by Harish .s (@harish_s_93e5d1c9d87ae5a).</description>
    <link>https://dev.to/harish_s_93e5d1c9d87ae5a</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.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4035195%2F0e3722ee-57e2-400b-ac1b-f8624657eb07.jpg</url>
      <title>DEV Community: Harish .s</title>
      <link>https://dev.to/harish_s_93e5d1c9d87ae5a</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/harish_s_93e5d1c9d87ae5a"/>
    <language>en</language>
    <item>
      <title>Spotting AI UI is too easy</title>
      <dc:creator>Harish .s</dc:creator>
      <pubDate>Sat, 18 Jul 2026 11:32:34 +0000</pubDate>
      <link>https://dev.to/harish_s_93e5d1c9d87ae5a/spotting-ai-ui-is-too-easy-3l29</link>
      <guid>https://dev.to/harish_s_93e5d1c9d87ae5a/spotting-ai-ui-is-too-easy-3l29</guid>
      <description>&lt;p&gt;There is a weird uncanny valley with LLM-generated UI right now. The code functions perfectly, but if you look at a lot of new SaaS apps, the design usually screams "AI slop."&lt;/p&gt;

&lt;p&gt;It usually comes down to these four dead giveaways:&lt;/p&gt;

&lt;p&gt;The Bubble Effect: The AI blindly slaps rounded-xl on absolutely everything.&lt;/p&gt;

&lt;p&gt;Amnesia Colors: By prompt #4, the LLM forgets your exact hex code and drifts into a generic "Tailwind Blue."&lt;/p&gt;

&lt;p&gt;Dirty Shadows: Heavy, muddy box shadows that look like 2012 Bootstrap.&lt;/p&gt;

&lt;p&gt;Zero Taste: Safe, boring typography with no real spacing logic.&lt;/p&gt;

&lt;p&gt;When you don't aggressively constrain an AI, it defaults to the mathematical average of the internet. And the average of the internet looks cheap.&lt;/p&gt;

&lt;p&gt;The Immediate Fix&lt;/p&gt;

&lt;p&gt;If you are vibecoding a SaaS right now, stop letting the AI guess your styles. Create a DESIGN.md file in your root folder and paste these constraints in it:&lt;/p&gt;

&lt;p&gt;ALWAYS use crisp, tight borders. Max border-radius is rounded-md. No bubbly UI.&lt;/p&gt;

&lt;p&gt;PRIMARY BRAND COLOR is strictly your hex code. Never use default Tailwind blues.&lt;/p&gt;

&lt;p&gt;SHADOWS: Use modern, layered shadows. No heavy drop shadows.&lt;/p&gt;

&lt;p&gt;TYPOGRAPHY: Use tight tracking on headers and generous line-height on body text.&lt;/p&gt;

&lt;p&gt;Just tell Cursor/Claude to reference DESIGN.md for all styling.&lt;/p&gt;

&lt;p&gt;The Next Step (My Architectural Experiment)&lt;/p&gt;

&lt;p&gt;While the manual file trick works, the AI still suffers from token drift over long chat sessions. Lately, I have been building a local MCP server that acts as a global design governance layer. It physically locks the AI into your specific design rules so it cannot hallucinate bad UI.&lt;/p&gt;

&lt;p&gt;I built a live prototype to visualize how this governance interface works. Please check it out here and join the waitlist if you want early access: &lt;a href="https://no-name-till-now.lovable.app" rel="noopener noreferrer"&gt;https://no-name-till-now.lovable.app&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I am curious how other solo devs are handling this right now. Are you manually cleaning up the Tailwind CSS after the AI does its thing, or have you found a better way to enforce strict design systems?&lt;/p&gt;

</description>
      <category>ai</category>
      <category>vibecoding</category>
      <category>uidesign</category>
      <category>cursor</category>
    </item>
    <item>
      <title>Spotting AI UI is too easy (and how to fix it in Cursor/Bolt)</title>
      <dc:creator>Harish .s</dc:creator>
      <pubDate>Sat, 18 Jul 2026 11:28:34 +0000</pubDate>
      <link>https://dev.to/harish_s_93e5d1c9d87ae5a/spotting-ai-ui-is-too-easy-and-how-to-fix-it-in-cursorbolt-4h76</link>
      <guid>https://dev.to/harish_s_93e5d1c9d87ae5a/spotting-ai-ui-is-too-easy-and-how-to-fix-it-in-cursorbolt-4h76</guid>
      <description>&lt;p&gt;There is a weird uncanny valley with LLM-generated UI right now. The code functions perfectly, but if you look at a lot of new SaaS apps, the design usually screams "AI slop."&lt;/p&gt;

&lt;p&gt;It usually comes down to these four dead giveaways:&lt;/p&gt;

&lt;p&gt;The Bubble Effect: The AI blindly slaps rounded-xl on absolutely everything.&lt;/p&gt;

&lt;p&gt;Amnesia Colors: By prompt #4, the LLM forgets your exact hex code and drifts into a generic "Tailwind Blue."&lt;/p&gt;

&lt;p&gt;Dirty Shadows: Heavy, muddy box shadows that look like 2012 Bootstrap.&lt;/p&gt;

&lt;p&gt;Zero Taste: Safe, boring typography with no real spacing logic.&lt;/p&gt;

&lt;p&gt;When you don't aggressively constrain an AI, it defaults to the mathematical average of the internet. And the average of the internet looks cheap.&lt;/p&gt;

&lt;p&gt;The Immediate Fix&lt;/p&gt;

&lt;p&gt;If you are vibecoding a SaaS right now, stop letting the AI guess your styles. Create a DESIGN.md file in your root folder and paste these constraints in it:&lt;/p&gt;

&lt;p&gt;ALWAYS use crisp, tight borders. Max border-radius is rounded-md. No bubbly UI.&lt;/p&gt;

&lt;p&gt;PRIMARY BRAND COLOR is strictly your hex code. Never use default Tailwind blues.&lt;/p&gt;

&lt;p&gt;SHADOWS: Use modern, layered shadows. No heavy drop shadows.&lt;/p&gt;

&lt;p&gt;TYPOGRAPHY: Use tight tracking on headers and generous line-height on body text.&lt;/p&gt;

&lt;p&gt;Just tell Cursor/Claude to reference DESIGN.md for all styling.&lt;/p&gt;

&lt;p&gt;The Next Step (My Architectural Experiment)&lt;/p&gt;

&lt;p&gt;While the manual file trick works, the AI still suffers from token drift over long chat sessions. Lately, I have been building a local MCP server that acts as a global design governance layer. It physically locks the AI into your specific design rules so it cannot hallucinate bad UI.&lt;/p&gt;

&lt;p&gt;I built a live prototype to visualize how this governance interface works. Please check it out here and join the waitlist if you want early access: &lt;a href="https://no-name-till-now.lovable.app" rel="noopener noreferrer"&gt;https://no-name-till-now.lovable.app&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I am curious how other solo devs are handling this right now. Are you manually cleaning up the Tailwind CSS after the AI does its thing, or have you found a better way to enforce strict design systems?&lt;/p&gt;

</description>
      <category>ai</category>
      <category>design</category>
      <category>ui</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
