<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Writing on Vibe Coding</title><link>https://vibecoding.rest/category/writing/</link><description>Recent content in Writing on Vibe Coding</description><generator>Hugo</generator><language>en</language><atom:link href="https://vibecoding.rest/category/writing/index.xml" rel="self" type="application/rss+xml"/><item><title>Doc Co-Authoring</title><link>https://vibecoding.rest/skills/doc-coauthoring/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/doc-coauthoring/</guid><description>&lt;p&gt;Doc Co-Authoring packages a structured process for writing technical specs, PRDs, decision docs, and proposals: gathering context up front, iteratively building sections through brainstorming and editing, then stress-testing the draft by having a fresh, context-free Claude read it as a real reader would.&lt;/p&gt;</description></item><item><title>Internal Comms</title><link>https://vibecoding.rest/skills/internal-comms/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/internal-comms/</guid><description>&lt;p&gt;Internal Comms packages format- and tone-specific guidelines for recurring internal writing tasks — progress/plans/problems updates, company newsletters, FAQ answers, leadership updates, and incident reports — loading the matching template based on which type of communication is requested.&lt;/p&gt;</description></item></channel></rss>