> For the complete documentation index, see [llms.txt](https://www.ctrlaltftc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.ctrlaltftc.com/introduction-to-controls.md). # Why Control Theory is A Must Have What are control systems, and why do we use them? ## Why Controls? *Control theory* is a field of engineering that deals with designing controllers (typically implemented in software) to move a system to the desired state. Some systems are easy to control, some are difficult to control, and some are even impossible to control. Knowing which systems to design for and implementing a controller for them is a crucial skill that proves useful in many real-world jobs. It enables your robot to perform more reliably and efficiently. Implementing robust controls in your robot not only improves autonomous performance but also provides the peace of mind that your robot will behave as expected. --- # 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.ctrlaltftc.com/introduction-to-controls.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 `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.