> For the complete documentation index, see [llms.txt](https://docs.protoboard.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.protoboard.xyz/start-here/core-workflow.md). # Core Workflow The canonical product flow: Build, Validate, Fix, Ship. Everything in Protoboard follows one loop: **Build, Validate, Fix, Ship.** You will repeat this cycle many times as your design evolves, starting rough and tightening until every connection is green and your bill of materials is ready to order. {% hint style="info" %} Treat validation output as a to-do list, not a failure report. Each cycle gets you closer to a confident design. {% endhint %} *** ## Build Start by creating a new board and adding parts from the **Parts Bin**, the searchable catalog of ProtoPart definitions available in the left activity bar. You can also create blank parts and define them manually if your component is not in the library yet. Once you have parts on the canvas, connect them by dragging **harnesses** between them. Each harness carries one or more **interface links** that pair compatible interfaces (like I2C, UART, SPI, USB, or power). Protoboard auto-detects matches, but you can also configure links manually in the Inspector. At this stage, focus on getting the right parts placed and the intended connections roughed in. You do not need everything perfect; that is what the next step is for. {% hint style="success" %} **ProtoBot can help:** Ask ProtoBot to search for parts, suggest connections, or even lay out an entire subsystem based on your requirements. Open it from the AI icon in the left activity bar. {% endhint %} *** ## Validate Run the **Design Rule Check (DRC)** by opening the **Board Review** panel (shield icon in the left activity bar). The DRC inspects every connection on your board and checks electrical, mechanical, and data compatibility across all domains. Each interface link gets a status: **CONFIGURED** (green, all good), **PARTIALLY\_CONFIGURED** (amber, needs attention), **NOT\_CONFIGURED** (red, no functions mapped), or **INCOMPATIBLE** (red, cannot connect). The Board Review panel groups issues by severity. **Errors** block your design from shipping, while **Warnings** are things you should review but may choose to accept. Read the DRC results from top to bottom. Errors first, then warnings. Each issue includes a description of what is wrong and, in many cases, a suggested fix. {% hint style="success" %} **ProtoBot can help:** Ask ProtoBot to summarize your validation results, explain specific errors, or walk you through what each status means. {% endhint %} *** ## Fix Work through the issues flagged by the DRC. The most common fixes include: * **Resource allocation**: Assigning specific pins, ports, or channels on a part to the functions required by an interface link. * **Adapters**: Adding a bridge component when two parts are close to compatible but need voltage level shifting, protocol conversion, or physical adaptation. * **Resource reallocation**: Moving a function to a different resource when there is a conflict (e.g., two interfaces trying to use the same pin). * **Part substitution**: Swapping a part for a better-fit alternative when incompatibilities cannot be resolved. After each fix, re-run the DRC to see your progress. The goal is to get every connection to **CONFIGURED** (green) with no remaining errors. Warnings are worth reviewing, but they will not block you from moving to the next phase. {% hint style="success" %} **ProtoBot can help:** Ask ProtoBot to auto-allocate resources, suggest adapter components, or even apply a batch of fixes for you. It can resolve many common issues in seconds. {% endhint %} *** ## Ship Once your board is fully validated, you are ready to export. Open the **BOM** panel (cart icon in the left activity bar) to see every part in your design with cost estimates and supplier information. From there you can: * **Export to CSV** for import into procurement tools or spreadsheets * **Export to PDF** for documentation, review meetings, or archival * **Share your board** using the share button in the top bar so teammates can view and collaborate on the design * **Take a screenshot** of your canvas layout via the Project menu for presentations or reports The BOM is your order-ready checklist. Combined with a green DRC, it means you can buy parts with confidence that they will work together as designed. {% hint style="success" %} **ProtoBot can help:** Ask ProtoBot to generate a BOM summary, flag any sourcing concerns, or prepare your board for handoff to a teammate. {% endhint %} *** ## The loop in practice Most real projects go through this cycle several times: 1. **First pass**: Rough out parts and connections, run DRC, fix the obvious issues. 2. **Refinement**: Swap parts for better fits, tighten resource allocations, resolve warnings. 3. **Final check**: Full DRC with all connections green, BOM reviewed, board shared with the team. Each pass takes less time as your design stabilizes. The first cycle might take 30 minutes; the last might take 2. *** ## Related pages * [Quickstart (10 minutes)](/start-here/quickstart-10-minutes.md) * [Validation (DRC)](/user-guide/validation-drc.md) * [BOM + Export](/user-guide/bom-and-export.md) * [Glossary](/start-here/glossary.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.protoboard.xyz/start-here/core-workflow.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.