https://roboco.io/en/tags/documentation/ Recent content in Documentation on ROBOCO Hugo en-us Thu, 10 Sep 2026 10:00:00 +0900 https://roboco.io/en/posts/vibe-coding-documentation/ Thu, 10 Sep 2026 10:00:00 +0900 https://roboco.io/en/posts/vibe-coding-documentation/ <blockquote> <p>The purpose of documentation is communication. Vibe coding brings more participants into that conversation.</p> </blockquote> <figure><img src="https://roboco.io/posts/images/Dohyun.png"><figcaption> <h4>Dohyun Jung - Principal Consultant, ROBOCO</h4> </figcaption> </figure> <hr> <h2 id="tldr">TL;DR</h2> <ul> <li>The same documentation principles apply to vibe coding. Let agents handle writing and organization to gain the benefits of good practices with less effort.</li> <li>Distinguish documents that must stay current from one-off documents whose job ends when their purpose is fulfilled. Not every document needs updating.</li> <li>Split documentation into short Markdown files and connect them through folder indexes, rules, and skills. Make them discoverable when the work calls for them.</li> <li>Use lists for frequent, quick reference. Use narrative prose when readers need context and careful review.</li> <li>Documents let people and agents share intent and decision criteria with one another. People should focus on defining the purpose and judging the results.</li> </ul> <hr> <p>As I have said several times, the principles of software development still apply to vibe coding. Define the problem and design a solution. Implement and verify it. Review the outcome and improve it. These steps are necessary whether a person or an agent performs them. What changes is who does the work and what it costs.</p>