> For the complete documentation index, see [llms.txt](https://docs.beoble.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.beoble.io/development/using-ui-toolkit.md).

# Using UI-Toolkit

UI Toolkit is basically our base UI that is built in a way that is easy to modify. 

It is built on top of react-js and is free for you to customize in any possible way! (yes, it is just a code)

### Get PlugIn Key

To use the beoble customized UI toolkit for the web, you need to get a plugin key.

Currently, you can request any beoble admin to get a plugin key.

{% hint style="info" %}
We are working on building a dashboard for admins and are going to provide it ASAP
{% endhint %}

### Get Repository Access

You can reach out to beoble admin to claim your access to the UI toolkit repository.

{% hint style="info" %}
We are working on building a dashboard for admins and are going to provide it ASAP
{% 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://docs.beoble.io/development/using-ui-toolkit.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.