# Conversational build Conversational mode is the primary way to use Build. You describe what you want the app's purpose, its features, its users and Build produces a structured, working codebase. From there, the conversation continues: each follow-up prompt adds to or modifies the existing code rather than starting over. *** ### Initial generation Your first prompt drives the entire architecture. Build reads it and produces a plan routes, data models, components, APIs before writing any code. You can see this plan in the chat before files start appearing. A well-formed initial prompt describes: * What the app does and who uses it * The main pages or views * Key features and workflows * Any specific technical requirements (database, auth method, real-time features) ``` Build a project management tool where teams can create projects, assign tasks to members, set due dates, and track progress with a Kanban board. Include user authentication and email notifications when a task is assigned. ``` You don't need to specify the full stack unless you have a preference. Build will choose sensible defaults and note them in its planning output. *** ### Iterating with follow-up prompts After the initial generation, each prompt is treated as an instruction to modify the existing codebase. Build adds, changes, or removes code incrementally it doesn't regenerate from scratch. ``` Create an admin panel where site owners can manage users and revoke access. ``` ``` Add CSV export component to the task table. ``` --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.codemate.ai/build/conversational-build.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.