<?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: shitianfang</title>
    <description>The latest articles on DEV Community by shitianfang (@shitianfang).</description>
    <link>https://dev.to/shitianfang</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%2F1026686%2Fa40ffe41-ff7e-47c2-bd54-eb8df8abbada.png</url>
      <title>DEV Community: shitianfang</title>
      <link>https://dev.to/shitianfang</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/shitianfang"/>
    <language>en</language>
    <item>
      <title>How We Stopped Merge Hell in Our AI-First Dev Team</title>
      <dc:creator>shitianfang</dc:creator>
      <pubDate>Tue, 07 Apr 2026 01:17:43 +0000</pubDate>
      <link>https://dev.to/shitianfang/how-we-stopped-merge-hell-in-our-ai-first-dev-team-44ae</link>
      <guid>https://dev.to/shitianfang/how-we-stopped-merge-hell-in-our-ai-first-dev-team-44ae</guid>
      <description>&lt;h2&gt;
  
  
  The Problem No One Talks About
&lt;/h2&gt;

&lt;p&gt;Everyone's excited about vibe coding. But here's what happens &lt;br&gt;
when a team of 3 uses Claude Code / Cursor simultaneously:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Dev A's agent: &lt;code&gt;GET /api/users/:id&lt;/code&gt; → &lt;code&gt;{ userId, name }&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Dev B's agent: &lt;code&gt;GET /api/users/:id&lt;/code&gt; → &lt;code&gt;{ user_id, username }&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Dev C's frontend: expects &lt;code&gt;{ id, displayName }&lt;/code&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Merge day = disaster. Every. Single. Time.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why This Happens
&lt;/h2&gt;

&lt;p&gt;AI agents are stateless. Each session starts fresh with no &lt;br&gt;
knowledge of what your teammates' agents decided. They make &lt;br&gt;
reasonable but incompatible assumptions about the same API.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Fix: Shared Living Specs
&lt;/h2&gt;

&lt;p&gt;I built &lt;a href="https://coware.team" rel="noopener noreferrer"&gt;Coware&lt;/a&gt; around one idea: &lt;br&gt;
every agent reads the same spec before writing code.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Paste one prompt into your AI agent&lt;/li&gt;
&lt;li&gt;Agent reads &lt;code&gt;/llms.txt&lt;/code&gt; → auto-setup&lt;/li&gt;
&lt;li&gt;Scans codebase → generates interface specs (Markdown)&lt;/li&gt;
&lt;li&gt;Specs sync to server → every teammate's agent pulls them&lt;/li&gt;
&lt;li&gt;All agents code against the same contract&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Results
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;API merge conflicts: &lt;strong&gt;zero&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;Time re-explaining context to agents: &lt;strong&gt;zero&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;Setup: &lt;strong&gt;30 seconds, one paste&lt;/strong&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Open source, self-hostable, works with Claude Code, Cursor, &lt;br&gt;
Copilot, Windsurf.&lt;/p&gt;

&lt;p&gt;👉 &lt;a href="https://coware.team" rel="noopener noreferrer"&gt;coware.team&lt;/a&gt;&lt;br&gt;&lt;br&gt;
👉 &lt;a href="https://github.com/livespecs/coware-living-spec" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Curious how other teams handle this — what's your workflow?&lt;/p&gt;

</description>
      <category>agents</category>
      <category>ai</category>
      <category>showdev</category>
      <category>vibecoding</category>
    </item>
  </channel>
</rss>
