<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Workflow on Vibe Coding</title><link>https://vibecoding.rest/tags/workflow/</link><description>Recent content in Workflow on Vibe Coding</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 09 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://vibecoding.rest/tags/workflow/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>Get Shit Done</title><link>https://vibecoding.rest/skills/get-shit-done/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/get-shit-done/</guid><description>&lt;p&gt;Get Shit Done is a lightweight meta-prompting and context-engineering system for Claude Code, built around spec-driven development rather than ad hoc prompting.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Spec-first workflows tend to produce more predictable output than freeform prompting, especially on larger features. Packaging that discipline as a skill makes it the default instead of something re-explained per task.&lt;/p&gt;</description></item><item><title>n8n Skills</title><link>https://vibecoding.rest/skills/n8n-skills/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/n8n-skills/</guid><description>&lt;p&gt;n8n Skills lets Claude directly understand and operate n8n automation workflows — reading, editing, and reasoning about workflow graphs rather than treating them as opaque JSON.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;n8n workflows are graphs of connected nodes that are awkward to reason about as raw exported JSON. A skill that understands the workflow model can edit and debug workflows the way a human building them in the n8n UI would.&lt;/p&gt;</description></item><item><title>Breaking Big Tasks Into Agent-Sized Steps</title><link>https://vibecoding.rest/posts/breaking-down-big-tasks/</link><pubDate>Mon, 09 Feb 2026 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/posts/breaking-down-big-tasks/</guid><description>&lt;p&gt;Vague, large prompts produce vague, large diffs — and vague diffs are the hardest kind to review. The fix isn&amp;rsquo;t a cleverer prompt; it&amp;rsquo;s decomposition.&lt;/p&gt;&#10;&lt;h2 id="signs-a-task-is-too-big"&gt;Signs a task is too big&lt;/h2&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;You can&amp;rsquo;t describe what &amp;ldquo;done&amp;rdquo; looks like in one sentence&lt;/li&gt;&#10;&lt;li&gt;The task touches more than two or three unrelated parts of the system&lt;/li&gt;&#10;&lt;li&gt;You&amp;rsquo;d need to check in multiple times even if a human were doing it&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;If any of these are true, break it down before prompting.&lt;/p&gt;</description></item><item><title>What Vibecoding Actually Means</title><link>https://vibecoding.rest/posts/what-is-vibecoding/</link><pubDate>Mon, 12 Jan 2026 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/posts/what-is-vibecoding/</guid><description>&lt;p&gt;The term &amp;ldquo;vibecoding&amp;rdquo; gets used two very different ways. One camp treats it as a punchline — typing vague prompts and accepting whatever an AI spits out, bugs and all. The other treats it as a real discipline: directing an AI collaborator with enough precision and judgment that the result is actually production-worthy.&lt;/p&gt;</description></item></channel></rss>