> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/support-resources/tips-and-tricks/design-studio/element-repository.md).

# Element Repository

Use this section to learn tips and tricks for working with the Element Repository. These help you to create, manage, reuse, and update elements to support stable and maintainable test automation.

<details>

<summary><strong>Enable Self-Healing for Dynamic UI Elements</strong></summary>

Enable **Self-Healing** with **Custom Attributes** in the element details to improve element identification when UI attributes change dynamically, resulting in more stable test executions.

</details>

<details>

<summary><strong>Use Custom Properties for Reliable Element Identification</strong></summary>

Configure [**Custom Properties**](https://docs.avoautomation.com/avo-assure/create-and-execute-tests-with-design-studio/working-with-element-repository-section/features-in-element-repository/element-identifier-order/custom-property.md) to define additional element attributes when default attributes are insufficient, improving the accuracy and reliability of element identification.

</details>


---

# 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.avoautomation.com/avo-assure/support-resources/tips-and-tricks/design-studio/element-repository.md?ask=<question>&goal=<user_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.
