> For the complete documentation index, see [llms.txt](https://community.threekit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.threekit.com/platform-documentation/catalog-2.0-docs/project-data/assets/asset-editor/editor-layout-modes/logic-editor.md).

# Logic Editor

Simply put, Logic Mode is used to make assets configurable.

Logic Mode consists of three main components. The Logic Editor, which allows for creation of Attributes and Rules, is used to enforce configuration requirements on an Asset. The second component is the Preview Pane, which provides the visual representation and reflects changes based on manipulation of the Visual Attributes present in the Configurator Viewer, which is the third component of the Logic Mode interface. Similar to the Asset Panel, the Logic Editor and the Configurator Viewer are collapsible to allow for a larger preview area.

![](/files/qdKEEfIwJzWZs245GMKV)

The Logic Editor is an extremely versatile tool, providing the artist with the ability to automate manipulation of the Asset properties, and the properties of its corresponding Operators.

**Primary uses of Logic Mode**

Logic Mode is used to enforce configuration requirements by mapping Item Attributes to Visual Attributes.

Logic Mode can also be used to make the artist workflow more efficient. For example, exposing an attribute for manipulation on a Material Asset lays the foundation for re-using the same Asset on multiple Catalog Items.


---

# 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://community.threekit.com/platform-documentation/catalog-2.0-docs/project-data/assets/asset-editor/editor-layout-modes/logic-editor.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.