import{_ as t,c as a,o,a0 as i}from"./chunks/framework.FdfEk_gD.js";const d=JSON.parse('{"title":"Hands-On Tutorial","description":"","frontmatter":{},"headers":[],"relativePath":"user/tutorial.md","filePath":"user/tutorial.md"}'),n={name:"user/tutorial.md"};function r(s,e,l,h,u,p){return o(),a("div",null,[...e[0]||(e[0]=[i(`<h1 id="hands-on-tutorial" tabindex="-1">Hands-On Tutorial <a class="header-anchor" href="#hands-on-tutorial" aria-label="Permalink to &quot;Hands-On Tutorial&quot;">​</a></h1><p>The best way to understand Responsible Vibe is to experience it. We&#39;ll build something simple, enhance it, then fix a bug. Three different workflows, three different approaches.</p><h2 id="prerequisites" tabindex="-1">Prerequisites <a class="header-anchor" href="#prerequisites" aria-label="Permalink to &quot;Prerequisites&quot;">​</a></h2><p>Make sure you&#39;ve got Responsible Vibe configured with your AI agent. If not, check the <a href="./agent-setup.html">Quick Setup</a> first.</p><h2 id="part-1-greenfield-development" tabindex="-1">Part 1: Greenfield Development <a class="header-anchor" href="#part-1-greenfield-development" aria-label="Permalink to &quot;Part 1: Greenfield Development&quot;">​</a></h2><p>Let&#39;s build something from scratch. This triggers the <strong>Greenfield workflow</strong> – the full engineering process for new projects.</p><h3 id="the-challenge" tabindex="-1">The Challenge <a class="header-anchor" href="#the-challenge" aria-label="Permalink to &quot;The Challenge&quot;">​</a></h3><div class="language- vp-adaptive-theme"><button title="Copy Code" class="copy"></button><span class="lang"></span><pre class="shiki shiki-themes github-light github-dark vp-code" tabindex="0"><code><span class="line"><span>Ask your AI: &quot;Build a simple dice game. Two players take turns rolling dice, highest total wins.&quot;</span></span></code></pre></div><p><em>Hint: In order to not get just another Next.js app, you may instruct it to build for the terminal in a future stage</em></p><h3 id="what-you-ll-experience" tabindex="-1">What You&#39;ll Experience <a class="header-anchor" href="#what-you-ll-experience" aria-label="Permalink to &quot;What You&#39;ll Experience&quot;">​</a></h3><p>Your AI won&#39;t immediately start coding. Instead, it&#39;ll:</p><ol><li><p><strong>Ask clarifying questions</strong>: &quot;How many dice per roll? Best of how many rounds? Should we track scores across games?&quot;</p></li><li><p><strong>Design the architecture</strong>: &quot;I&#39;m thinking a Game class, Player class, and a simple CLI interface. Does that sound right?&quot;</p></li><li><p><strong>Plan the implementation</strong>: &quot;Let me break this into phases: core game logic, player management, CLI interface, then testing.&quot;</p></li><li><p><strong>Build systematically</strong>: Following the plan it just created, not jumping around randomly.</p></li></ol><p>This is the <strong>Greenfield workflow</strong> in action – comprehensive planning before implementation.</p><h3 id="key-observation" tabindex="-1">Key Observation <a class="header-anchor" href="#key-observation" aria-label="Permalink to &quot;Key Observation&quot;">​</a></h3><p>Notice how your AI is asking <em>you</em> questions instead of making assumptions. It&#39;s treating you as the product owner, not just someone who wants code written.</p><h2 id="part-2-feature-enhancement" tabindex="-1">Part 2: Feature Enhancement <a class="header-anchor" href="#part-2-feature-enhancement" aria-label="Permalink to &quot;Part 2: Feature Enhancement&quot;">​</a></h2><p>Now let&#39;s add something that wasn&#39;t in the original scope. This triggers the <strong>EPCC workflow</strong> (Explore → Plan → Code → Commit).</p><h3 id="the-challenge-1" tabindex="-1">The Challenge <a class="header-anchor" href="#the-challenge-1" aria-label="Permalink to &quot;The Challenge&quot;">​</a></h3><div class="language- vp-adaptive-theme"><button title="Copy Code" class="copy"></button><span class="lang"></span><pre class="shiki shiki-themes github-light github-dark vp-code" tabindex="0"><code><span class="line"><span>Ask your AI: &quot;Add a high-score tracking system.</span></span>
<span class="line"><span>Players should see their win/loss record across games.&quot;</span></span></code></pre></div><h3 id="what-you-ll-experience-1" tabindex="-1">What You&#39;ll Experience <a class="header-anchor" href="#what-you-ll-experience-1" aria-label="Permalink to &quot;What You&#39;ll Experience&quot;">​</a></h3><p>Different workflow, different approach:</p><ol><li><p><strong>Explore</strong>: &quot;Let me understand the current code structure and see how to integrate scoring...&quot;</p></li><li><p><strong>Plan</strong>: &quot;I&#39;ll need to modify the Player class, add persistent storage, and update the CLI to show stats.&quot;</p></li><li><p><strong>Code</strong>: Focused implementation of just the scoring feature</p></li><li><p><strong>Commit</strong>: Clean up and finalize the enhancement</p></li></ol><p>This is <strong>EPCC</strong> – more iterative, focused on extending existing functionality rather than building from scratch.</p><h3 id="key-observation-1" tabindex="-1">Key Observation <a class="header-anchor" href="#key-observation-1" aria-label="Permalink to &quot;Key Observation&quot;">​</a></h3><p>The AI adapts its process based on context. It&#39;s not following the same heavy planning process as the greenfield project because it&#39;s working with existing code.</p><h2 id="part-3-bug-fixing" tabindex="-1">Part 3: Bug Fixing <a class="header-anchor" href="#part-3-bug-fixing" aria-label="Permalink to &quot;Part 3: Bug Fixing&quot;">​</a></h2><p>Time to break something and fix it. This triggers the <strong>Bugfix workflow</strong>.</p><h3 id="create-the-bug" tabindex="-1">Create the Bug <a class="header-anchor" href="#create-the-bug" aria-label="Permalink to &quot;Create the Bug&quot;">​</a></h3><p>First, let&#39;s introduce a bug manually:</p><ol><li>Find the dice rolling logic in your code</li><li>Change something subtle (maybe make it always roll 1, or break the scoring)</li><li>Save the file</li></ol><h3 id="the-challenge-2" tabindex="-1">The Challenge <a class="header-anchor" href="#the-challenge-2" aria-label="Permalink to &quot;The Challenge&quot;">​</a></h3><div class="language- vp-adaptive-theme"><button title="Copy Code" class="copy"></button><span class="lang"></span><pre class="shiki shiki-themes github-light github-dark vp-code" tabindex="0"><code><span class="line"><span>Ask your AI: &quot;There&#39;s a bug in the dice game.</span></span>
<span class="line"><span>Players are complaining the dice rolls seem unfair.&quot;</span></span></code></pre></div><h3 id="what-you-ll-experience-2" tabindex="-1">What You&#39;ll Experience <a class="header-anchor" href="#what-you-ll-experience-2" aria-label="Permalink to &quot;What You&#39;ll Experience&quot;">​</a></h3><p>Yet another workflow approach:</p><ol><li><p><strong>Reproduce</strong>: &quot;Let me run the game and see if I can reproduce the issue...&quot;</p></li><li><p><strong>Analyze</strong>: &quot;I found the problem – the dice rolling logic is hardcoded to return 1.&quot;</p></li><li><p><strong>Fix</strong>: Targeted fix for just the bug, not a rewrite</p></li><li><p><strong>Verify</strong>: &quot;Let me test this fix to make sure it works correctly...&quot;</p></li></ol><p>This is the <strong>Bugfix workflow</strong> – systematic debugging rather than random code changes.</p><h3 id="key-observation-2" tabindex="-1">Key Observation <a class="header-anchor" href="#key-observation-2" aria-label="Permalink to &quot;Key Observation&quot;">​</a></h3><p>The AI follows a methodical debugging process instead of just guessing at fixes. It reproduces first, then analyzes, then fixes.</p><h2 id="what-you-just-learned" tabindex="-1">What You Just Learned <a class="header-anchor" href="#what-you-just-learned" aria-label="Permalink to &quot;What You Just Learned&quot;">​</a></h2><p>You experienced three different engineering methodologies:</p><ul><li><strong>Greenfield</strong>: Comprehensive planning for new projects</li><li><strong>EPCC</strong>: Iterative development for feature additions</li><li><strong>Bugfix</strong>: Systematic debugging for problem resolution</li></ul><p>Your AI automatically picked the right approach based on what you were trying to do. No configuration needed – it just works.</p><h2 id="the-real-magic" tabindex="-1">The Real Magic <a class="header-anchor" href="#the-real-magic" aria-label="Permalink to &quot;The Real Magic&quot;">​</a></h2><p>This isn&#39;t just about following different steps. It&#39;s about your AI thinking like an engineer:</p><ul><li><strong>Asking the right questions</strong> at the right time</li><li><strong>Planning before implementing</strong> when it matters</li><li><strong>Adapting the process</strong> to the situation</li><li><strong>Maintaining context</strong> across the entire development lifecycle</li></ul><p>Most AI tools make you faster at writing code. Responsible Vibe makes your AI better at engineering software.</p><h2 id="next-steps" tabindex="-1">Next Steps <a class="header-anchor" href="#next-steps" aria-label="Permalink to &quot;Next Steps&quot;">​</a></h2><ul><li><strong><a href="./workflow-selection.html">Automatic Workflow Selection</a></strong> – How the AI picks the right methodology</li><li><strong><a href="./advanced-engineering.html">Advanced Engineering</a></strong> – Project docs, variables, and branch management</li><li><strong><a href="./../workflows.html">Interactive Workflows</a></strong> – Explore all available methodologies</li></ul><hr><p><em>Try this tutorial with your own project ideas. The workflows adapt to any domain – web apps, CLI tools, games, whatever you&#39;re building.</em></p>`,50)])])}const c=t(n,[["render",r]]);export{d as __pageData,c as default};
