> For the complete documentation index, see [llms.txt](https://help.vectary.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.vectary.com/documentation/design-process/design-mode/primitives.md).
# Primitives
## **Overview**
**Primitives** are basic geometric shapes that serve as building blocks for 3D modeling. These shapes, such as boxes, spheres, and cylinders, come with adjustable parametric settings, allowing for modifications in size, subdivisions, and other attributes. Primitives are commonly used as starting points for creating more complex models.
* Box
* Sphere
* Cone
* Cylinder
* Tube
* Torus
* Polyhedron
* Plane
* [3D Text](/documentation/design-process/design-mode/3d-text.md)
Primitive shapes can be modified directly on the canvas or through the right panel settings.
{% embed url="" %}
## **Primitive adjustment**
Adjust the shape of the primitive using the purple handles.
These modifications can also be performed in the right panel for precise control.
The number of segments (polygons) in the primitive can be modified using the input fields:
{% hint style="success" %}
A higher segment count increases the geometric detail, allowing for smoother transformations
{% endhint %}
---
# 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://help.vectary.com/documentation/design-process/design-mode/primitives.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.
