> For the complete documentation index, see [llms.txt](https://build.localwp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://build.localwp.com/building/using-local-components.md).

# Using local-components

If you need to add UI components to your Local Add-on, we recommend using the [`@getflywheel/local-components`](https://www.npmjs.com/package/@getflywheel/local-components) package which is available on npm.

To see what components are available in `local-components`, check out our [styleguide](https://getflywheel.github.io/local-components/).

![](/files/-MUuEZgAtgaJac8u6fex)

{% hint style="info" %}
`local-components` utilizes [CSS Modules](https://github.com/css-modules/css-modules), which allows multiple versions of `local-components` to be loaded into Local via multiple Add-ons. This allows for your Add-on to look and behave the same even if the user updates Local.
{% 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://build.localwp.com/building/using-local-components.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.