> 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-methodologies/slots-and-tabs.md).

# Slots and Tabs

Slot and tab construction involves interlocking parts like a 3D puzzle. Tabs on one piece fit into slots on another, aligning the parts automatically. When glued, bolted, or clamped together, this method creates fast, rigid assemblies without complex tools.

#### How It Works

* CAD parts are designed with matching cutouts and tabs.
* Cut from flat sheet stock (metal, polycarb, plywood).
* Tabs insert into slots and are fastened with screws, rivets, glue, or welding.

#### Pros

* **Fast Assembly:** Self-aligning joints reduce the need for jigs.
* **Repeatable:** Great for building multiple identical bots or testbeds.
* **Good for Non-Metal:** Works well with plastic or wood prototypes.

#### Cons

* **Hard to Modify:** Once joined, the structure isn’t easily reconfigurable.
* **Flex Risk:** Thin materials may wobble or deform under load.
* **Cutting Precision Needed:** Slots and tabs must be toleranced correctly for your cutting process.

#### FTC Tips

* Add \~0.1–0.2mm clearance between tabs and slots depending on cutter type.
* Use interlocking fingers or “keyed” features to lock parts rotationally.
* Add fillets or dog-bones to inner corners to match laser/waterjet cut radius.
* Secure tabs with nylon lock nuts or rivets—design so they sit flush to avoid snagging.


---

# 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-methodologies/slots-and-tabs.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.