> For the complete documentation index, see [llms.txt](https://docs.openbrush.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openbrush.app/user-guide/using-the-open-brush-tools-quick-tools-and-menu-panels/extras-panel/guides-panel.md).
# Guides Panel
* Use the sphere, cube, and pill guides to create perfect shapes.
* Guides are moved and scaled similar to other widgets, using the Grip buttons.
Guides also respect the position and rotation locks on the [Transform Panel](/user-guide/using-the-open-brush-tools-quick-tools-and-menu-panels/extras-panel/transform-panel.md). Lock one or more axes when you need to reposition a guide without changing its height, orientation or alignment on the locked axes.
## Guide Types
Open Brush includes several types of guides:
### Plane Guide
The plane guide creates a flat surface that you can paint on or use as a reference. This is useful for:
* Creating flat surfaces like floors, walls, or tables
* Drawing 2D elements in 3D space
* Aligning objects to a common plane
* Building architectural elements
### Other Guides
* **Sphere guide** - Paint on a spherical surface
* **Cube guide** - Paint along box edges and faces
* **Capsule (pill) guide** - Paint on cylindrical surfaces with rounded ends
### Guide Settings
The Guide Settings allow you to customize how guides behave, including snapping options and visibility settings.
---
# 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.openbrush.app/user-guide/using-the-open-brush-tools-quick-tools-and-menu-panels/extras-panel/guides-panel.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.
