> 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/modularity.md).

# Modularity

Building your robot with modular subsystems saves hours during testing and events. Modularity means each mechanism can be treated like a black box—built, tested, and repaired independently. Standardization ensures that parts and tools are consistent across your design.

#### What Is Modularity?

A modular subsystem is self-contained:

* It bolts on with a few screws or brackets
* Has a single set of wires or cables going in/out
* Can be removed without disturbing unrelated systems

**Examples:** A fully removable arm module, drivetrain pods, intake trays, or even pre-wired electronics boards.

#### Benefits of Modularity

* **Faster Repairs:** Replace a broken part without taking apart the whole robot.
* **Parallel Development:** Mechanical and electrical team members can work on different modules simultaneously.
* **Easier Iteration:** Test different versions of a mechanism without redesigning the whole robot.
* **Consistent Mounting:** Use standard hole spacings and brackets (e.g., 16mm grid, extrusion mounts).

#### Standardization Tips

* Use common motor types (e.g., all GoBILDA 312 RPM)
* Stick to one bolt size per use-case (M4 for structure, M3 for electronics)
* Use keyed motor shafts or set screw flats consistently
* Design 2D brackets and spacers around common thicknesses (3mm, 6mm, etc.)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.ftcwiki.org/design-style/design-guidelines/modularity.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.