> 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/how-to-build-competitive-robots/how-to-compete/design-philosophy.md). # Design Philosophy ### Design Philosophy Modular design philosophy also plays a key role in competitive success. Instead of hard-mounting everything to a central chassis, design your robot in layers or sections—drivetrain, intake, lift, and outtake—that can be independently removed or replaced. This approach simplifies troubleshooting and makes it easier to iterate between competitions. Standardizing mounting hole patterns and using quick electrical disconnects (like Anderson Powerpoles or JST connectors) can dramatically reduce pit repair time and improve robot reliability. Strategy should always guide design. The most successful teams don’t just build the “coolest” robot—they build the robot that best executes their chosen scoring path. That might mean prioritizing cycle speed and reliability over complexity or designing for field control tactics like freight hoarding, zone blocking, or rapid parking. A robot that runs a consistent four-cycle pattern every match will often outperform a robot that *can* do seven cycles but frequently fails. Finally, serviceability is critical. Your robot should be designed for easy maintenance between matches. Color-coded wiring, clean cable management, and accessible fasteners make a huge difference when time is short in the pit. Use thread locker or nylon lock nuts on high-vibration areas like drivetrains or intakes to reduce the chance of loosening bolts. Design with the assumption that something *will* break, and ask yourself: how quickly can we fix it? By combining these advanced design strategies with the core mechanical principles outlined above, your team can build not just a functional robot—but a consistently competitive one. --- # 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/how-to-build-competitive-robots/how-to-compete/design-philosophy.md?ask=&goal= ``` `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.