> 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-style.md).

# Design Style

The design of a robot is more than just putting parts together. It's about how all the parts work as a system. The way you approach your robot’s design has a huge impact on how easy it is to build, iterate, fix, and compete with. 

<figure><img src="/files/UTZyLBhcr6Xx8yDXpxP1" alt=""><figcaption><p>FTC 6962 Pokébolts Chassis</p></figcaption></figure>

This section dives into the principles that make FTC robots clean, consistent, and competition-ready. Whether you're designing your first bot or refining your 10th, having a clear design style improves reliability and efficiency across the board.

Clean, modular, and serviceable robots are not accidents. Every benefit is the result of intentional design choices. Every bracket, wire, and spacer should have a purpose, and no mechanism should be harder to reach than necessary. In this section, we break down the visual and structural design elements that make great FTC robots stand out, including standard spacing conventions, wiring discipline, fastener choices, and a mindset for mechanical clarity.

Understanding and applying a consistent design language also makes it easier for new team members to contribute, CAD reviewers to catch mistakes, and for everyone to debug or disassemble the robot during matches or inspections. It even helps judges quickly understand how your robot works.

Here, you'll find breakdowns on visual cleanliness, standardization, modularity, wire management, and construction techniques that are easy to maintain and scale. These best practices are not just about aesthetics—they’re about performance, safety, and professionalism.


---

# 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-style.md?ask=<question>&goal=<endgoal>
```

`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.