> For the complete documentation index, see [llms.txt](https://docs.besmart.software/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.besmart.software/2d-drafting-and-documentation/smart-documentation/predefined-dimensions-smart-dimensions.md).
# Predefined Dimensions (Smart Dimensions)
**Predefined Dimensions** is a tool that can **automatically dimension elements** in a view according to predefined settings. It can place hundreds of individual dimensions for each specified element or just several dimensions that include many references or a combination of both.
This tool can be used in any user-created Revit views or it can be combined with [**Views**](/2d-drafting-and-documentation/smart-documentation/views-smart-views.md) or [**Assemblies**](/2d-drafting-and-documentation/smart-documentation/assemblies-smart-assemblies.md) configurations to generate new views that come already dimensioned.
{% hint style="info" %}
Predefined Dimensions tool is also known as **Smart Dimensions** and is used in many other Agacad solutions. You can read the full [**Smart Dimensions Technical Documentation here**](/common-for-several-products/smart-dimensions.md).
{% 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://docs.besmart.software/2d-drafting-and-documentation/smart-documentation/predefined-dimensions-smart-dimensions.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.
