import{_ as t,c as o,o as i,ae as s}from"./chunks/framework.CBTkueSR.js";const m=JSON.parse('{"title":"Qoder","description":"","frontmatter":{},"headers":[],"relativePath":"en/qoder/index.md","filePath":"en/qoder/index.md"}'),n={name:"en/qoder/index.md"};function a(r,e,d,c,l,u){return i(),o("div",null,[...e[0]||(e[0]=[s('<h1 id="qoder" tabindex="-1">Qoder <a class="header-anchor" href="#qoder" aria-label="Permalink to &quot;Qoder&quot;">​</a></h1><ul><li><a href="./prompt.html">prompt</a></li><li><a href="./Quest Action.html">Quest Action</a></li><li><a href="./Quest Design.html">Quest Design</a></li></ul><h2 id="summary-of-product-tool-documents" tabindex="-1">Summary of Product Tool Documents <a class="header-anchor" href="#summary-of-product-tool-documents" aria-label="Permalink to &quot;Summary of Product Tool Documents&quot;">​</a></h2><p>This directory defines the core specifications for the AI programming assistant &quot;Qoder&quot;, designed for pair programming with users in a specialized agent IDE. Qoder operates in two distinct modes, each with its unique purpose and set of instructions:</p><ul><li><p><strong><code>Quest Design.md</code></strong>: This file defines Qoder&#39;s &quot;Design Mode&quot;. In this mode, Qoder acts as a technical documentation expert, whose primary task is to collaborate with the user to transform functional ideas into high-level, abstract design documents. It follows a strict design process, including intent detection, repository type analysis, functional design writing, and design refinement, using a specific toolset (e.g., <code>search_codebase</code>, <code>read_file</code>, <code>search_replace</code>) to assist the design process.</p></li><li><p><strong><code>Quest Action.md</code></strong>: This file defines Qoder&#39;s &quot;Action Mode&quot;, an autonomous agent running in the background. Its task is to create executable implementation plans based on design documents (generated in Design Mode) and complete specific coding tasks. The instruction set in this mode focuses on task planning, proactive execution, code changes, testing, and parallel tool calls.</p></li><li><p><strong><code>prompt.md</code></strong>: This is a more general system prompt that integrates and elaborates on Qoder&#39;s identity, communication guidelines, planning methods, tool usage rules (especially strict rules for parallel calls and file editing), testing guidelines, and error handling. It appears to be the foundational code of conduct shared by both modes.</p></li></ul><p>In summary, the <code>qoder</code> directory, through the separation of Design Mode (planning) and Action Mode (execution), builds a structured, phased AI development workflow aimed at systematically transforming users&#39; abstract ideas into verified, executable code.</p>',6)])])}const h=t(n,[["render",a]]);export{m as __pageData,h as default};