> For the complete documentation index, see [llms.txt](https://docs.raidrobotics.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.raidrobotics.org/design/materials/sheet-goods.md).

# Sheet Goods

In FRC (FIRST Robotics Competition), sheet goods play a critical role in robot construction due to their versatility and ease of fabrication. Commonly used materials include aluminum, polycarbonate, plywood, and HDPE, each selected based on the required strength, weight, and application. Sheet goods are typically used for components like structural panels, electronics mounting boards, gussets, belly pans, and custom brackets. They are often cut using CNC routers, laser cutters, or waterjets for precise shapes and patterns, enabling rapid prototyping and customization. Proper selection and effective use of sheet goods can significantly impact a robot’s durability, weight, and overall performance on the field.

We have standardized on a few types and variations of materials to reduce the amount of materials we have to keep in stock.


---

# 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://docs.raidrobotics.org/design/materials/sheet-goods.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.
