# Competitive Robotics

Whether you're joining [Gilmour's Moonshots](https://ga-moonshots.netlify.app/) or a different FIRST Technology Challenge (FTC) team, we hope this guide will ease the process.&#x20;

## **Getting Started**

* **Jump In Early:** Don't wait! Attend team meetings, observe our workshops, and get a feel for different roles. Identify areas that ignite your interest and offer your help.
* **Choose Your Path:** Our team operates through various sub-groups, each playing a crucial role in our robot's success:
  * **Marketing Team:** Be the face of the team, recruit new members, manage logistics, and prepare presentations for judges. Hone your communication and organizational skills.
  * **Software Team:** Dive into the world of coding, working alongside hardware engineers and the drive team. Maintain our codebase, troubleshoot issues, and post questions on online forums to expand your knowledge.
  * **Hardware Team:** Design and build robot components using CAD software, 3D printing, and various hand tools. Develop hands-on engineering skills and fix technical issues during competitions.
  * **Drive Team:** Take the spotlight by operating the robot during competitions. Strategize gameplays, execute maneuvers based on calls, and practice extensively to become a well-coordinated unit

## **Additional Resources:**

* Moonshots' website: <https://ga-moonshots.netlify.app/>
* FTC official website: <https://www.firstinspires.org/robotics/ftc>
* FTCLib documentation: <https://docs.ftclib.org/ftclib/>
* FTCSim: <https://ftcsim.org/>
* Programming Resources: <https://ftc-docs.firstinspires.org/en/latest/programming_resources/index.html#programming-tutorials>


---

# Agent Instructions: 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:

```
GET https://gilmour.online/compsci/competitive-robotics.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
