> For the complete documentation index, see [llms.txt](https://help.arkance-systems.com/class-feeder/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.arkance-systems.com/class-feeder/eng/manual/element-classification/element-selection-by-category.md).

# Element Selection by Category and Type

Area on the left side of Class Feeder dialogue enables users to select entities by their category and type according to Revit default categories. Selection of individual types of entities is also possible.

After selecting categories or types, all instances of selected types are displayed in the lower part of selection area. Individual instances can be selected. To classify selected instances, pick the right code from the classification table and click *Classify* button.

<figure><img src="/files/EPVwGBl9yB3t4yXmvEGU" alt=""><figcaption><p>Element selection by category and type</p></figcaption></figure>

{% hint style="info" %}
Right clicking the area of category and opens context menu containing additional selection options.
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.arkance-systems.com/class-feeder/eng/manual/element-classification/element-selection-by-category.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.