> For the complete documentation index, see [llms.txt](https://docs.wcproducts.com/welcome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wcproducts.com/welcome/system-and-structure/gear-rack/overview-and-features.md). # Overview and Features These FRC gear racks are designed to provide precise and controlled linear motion for your robot, an advantage over the sometimes unpredictable nature of pneumatics. They're made from lightweight yet robust 6061-T6 aluminum, coming in two tooth pitches (10DP and 20DP) to suit your gearing needs. And, at 35.5 inches each, you can stack them infinitely for extended travel distances!

**Notable Features** * Precise and controlled linear motion * 10DP and 20DP options * \#10-32 clearance holes * Infinite stacking * Can be stacked to increase gear face width --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://docs.wcproducts.com/welcome/system-and-structure/gear-rack/overview-and-features.md?ask=&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 `build a script that syncs our docs to a CMS` 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.