> For the complete documentation index, see [llms.txt](https://docs.realmacsoftware.com/elements-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmacsoftware.com/elements-docs/using-elements/components/common-controls.md).
# Common Controls
Learn the Inspector controls shared by built-in components
Common Controls are reusable Inspector groups that behave consistently across built-in components. Learning them once makes it easier to size, position, style, animate, and link components throughout a project.
The available groups depend on the selected component. Some components use a specialised variant with different defaults—for example, Image starts at 100% width, while a general component starts at Auto.
{% hint style="info" %}
Many values are responsive. When a control supports breakpoints, set the Base value first and add overrides only where the design needs to change.
{% endhint %}
### How Common Controls Work
* **Theme values** use colours, spacing, typography, shadows, and borders defined in Theme Studio.
* **Custom values** accept valid CSS values where the control provides a manual mode.
* **Responsive controls** can be overridden at different breakpoints.
* **State controls** let you edit Static, Start, End, Normal, Hover, or other states without changing the state visitors initially see.
* **Conditional controls** appear only after the related feature is enabled or a compatible Type or Style is selected.
Individual component pages document any specialised defaults or behaviour that differs from these shared guides.
---
# 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.realmacsoftware.com/elements-docs/using-elements/components/common-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.