> For the complete documentation index, see [llms.txt](https://www.ftcwiki.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.ftcwiki.org/design-style/design-guidelines/how-to-design-a-clean-robot.md). # How to Design a Clean Robot A robot can function just fine while still being cluttered, difficult to maintain, or even unsafe. “Clean” design goes beyond looks—it's about structure, serviceability, and thoughtful planning. A clean robot is easier to fix, debug, and upgrade. Judges and alliance partners notice. Clean design demonstrates engineering maturity. #### Why Cleanliness Matters * **Serviceability:** Clean designs allow for quicker swaps, easier cable tracing, and faster troubleshooting between matches. * **Consistency:** A well-structured robot is easier to program because sensors, mechanisms, and encoders behave predictably. * **Judge Appeal:** A tidy robot signals that your team understands engineering best practices and cares about quality. #### Common Signs of a Messy Robot * Wires crossing over mechanisms or dangling loosely * Screws that are impossible to reach without full disassembly * Mechanisms attached at awkward angles without alignment * Zip ties, tape, and hot glue holding critical components #### Hallmarks of a Clean Build * Thoughtful cable routing with strain relief and bundling * Standardized hardware sizes and symmetrical placement * Easy access to high-maintenance parts like batteries and motors * Components mounted squarely and parallel to each other --- # 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://www.ftcwiki.org/design-style/design-guidelines/how-to-design-a-clean-robot.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.