<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Openclaw on ROBOCO</title>
    <link>https://roboco.io/en/tags/openclaw/</link>
    <description>Recent content in Openclaw on ROBOCO</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 27 Mar 2026 00:00:00 +0900</lastBuildDate>
    <atom:link href="https://roboco.io/en/tags/openclaw/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>OpenClaw&#39;s Five-Layer Gatekeeping: Quality Control in the Age of AI Agents</title>
      <link>https://roboco.io/en/posts/openclaw-gatekeeping-architecture/</link>
      <pubDate>Fri, 27 Mar 2026 00:00:00 +0900</pubDate>
      <guid>https://roboco.io/en/posts/openclaw-gatekeeping-architecture/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;Thousands of PRs pouring into a 310K-star project, plus parallel commits from eight AI agents. The secret to keeping quality from collapsing amid that chaos is five layers of automated gatekeeping.&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;figure&gt;&lt;img src=&#34;https://roboco.io/posts/images/Dohyun.png&#34;&gt;&lt;figcaption&gt;&#xA;      &lt;h4&gt;Dohyun Jung - Principal Consultant, ROBOCO&lt;/h4&gt;&#xA;    &lt;/figcaption&gt;&#xA;&lt;/figure&gt;&#xA;&#xA;&lt;hr&gt;&#xA;&lt;p&gt;In an earlier post I analyzed &lt;a href=&#34;https://roboco.io/en/posts/openclaw-agents-md-productivity-secrets/&#34;&gt;the productivity principles embedded in OpenClaw&amp;rsquo;s AGENTS.md&lt;/a&gt;. The heart of that piece was &amp;ldquo;writing the rules down.&amp;rdquo; But writing rules and &lt;strong&gt;enforcing&lt;/strong&gt; them are entirely different problems.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Line Between Repository Rules and Personal Taste in the Vibe Coding Era</title>
      <link>https://roboco.io/en/posts/vibe-coding-rules-vs-taste/</link>
      <pubDate>Thu, 26 Mar 2026 17:26:21 +0900</pubDate>
      <guid>https://roboco.io/en/posts/vibe-coding-rules-vs-taste/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;The job of AGENTS.md is not to clone your developers. It is to pin down only the boundaries where accidents must be prevented.&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;figure&gt;&lt;img src=&#34;https://roboco.io/posts/images/Dohyun.png&#34;&gt;&lt;figcaption&gt;&#xA;      &lt;h4&gt;Dohyun Jung - Principal Consultant, ROBOCO&lt;/h4&gt;&#xA;    &lt;/figcaption&gt;&#xA;&lt;/figure&gt;&#xA;&#xA;&lt;p&gt;Teams that adopt vibe coding soon run into a similar question. Once you start putting an &lt;code&gt;AGENTS.md&lt;/code&gt; or &lt;code&gt;CLAUDE.md&lt;/code&gt; in every repository to tell AI agents the rules, it becomes murky how far you should pin things down as shared rules and where you should leave things to individual taste. Draw that line wrong and two problems appear at once: the safety rules that absolutely must hold get loose, while choices that are really just preferences become needlessly rigid.&lt;/p&gt;</description>
    </item>
    <item>
      <title>OpenClaw: Nine Best Practices from the World&#39;s Largest Vibe Coding Project</title>
      <link>https://roboco.io/en/posts/openclaw-vibe-coding-best-practices/</link>
      <pubDate>Sat, 14 Mar 2026 10:00:00 +0900</pubDate>
      <guid>https://roboco.io/en/posts/openclaw-vibe-coding-best-practices/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;&amp;ldquo;I used to lead a team. I had a lot of software engineers under me. Even then, I had to accept that they would not write code exactly the way I wanted it written.&amp;rdquo; – Peter Steinberger&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;figure&gt;&lt;img src=&#34;https://roboco.io/posts/images/Dohyun.png&#34;&gt;&lt;figcaption&gt;&#xA;      &lt;h4&gt;Dohyun Jung - Principal Consultant, ROBOCO&lt;/h4&gt;&#xA;    &lt;/figcaption&gt;&#xA;&lt;/figure&gt;&#xA;&#xA;&lt;hr&gt;&#xA;&lt;p&gt;OpenClaw is the most-starred software repository on GitHub (310K+ stars) and the definitive case study in large-scale AI-assisted &amp;ldquo;vibe coding.&amp;rdquo;&lt;sup id=&#34;fnref:2&#34;&gt;&lt;a href=&#34;#fn:2&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;2&lt;/a&gt;&lt;/sup&gt; Built by Austrian developer Peter Steinberger using three to eight parallel AI agent instances,&lt;sup id=&#34;fnref:3&#34;&gt;&lt;a href=&#34;#fn:3&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;3&lt;/a&gt;&lt;/sup&gt; the project demonstrates that a single developer can orchestrate a 300K+ LOC TypeScript monorepo, more than 20 messaging integrations, and native apps for three platforms — while barely reading most of the code.&lt;sup id=&#34;fnref1:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
