<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Developer Tools on Vibhu Bhatnagar — PowerShell &amp; Infrastructure Engineer</title><link>https://pwsh.in/tags/developer-tools/</link><description>Recent content in Developer Tools on Vibhu Bhatnagar — PowerShell &amp; Infrastructure Engineer</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Tue, 05 May 2026 10:00:00 +0530</lastBuildDate><atom:link href="https://pwsh.in/tags/developer-tools/index.xml" rel="self" type="application/rss+xml"/><item><title>DESIGN.md: Tell Your AI Agent What to Build, Not Just How to Build It</title><link>https://pwsh.in/posts/design-md-ai-agent-ui/</link><pubDate>Tue, 05 May 2026 10:00:00 +0530</pubDate><guid>https://pwsh.in/posts/design-md-ai-agent-ui/</guid><description>&lt;p>There&amp;rsquo;s a gap that most AI coding workflows ignore. You tell your agent how to write the code — but you never tell it how the UI should &lt;em>look&lt;/em>. The result is functional pages with no coherent style, inconsistent components, and a design that feels assembled rather than considered.&lt;/p>
&lt;p>&lt;code>DESIGN.md&lt;/code> is a plain-text fix for this. Drop one file in your project root and any AI coding agent instantly understands your visual system — colours, typography, component patterns, spacing, the lot.&lt;/p></description></item></channel></rss>