# 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/).

![](https://4236247329-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LMNZy_5ZTcBLB5brrEe%2F-MUuCfL1dUp6uJRp_CSX%2F-MUuEZgAtgaJac8u6fex%2Fadd-on-docs-local-components.png?alt=media\&token=cb8bd6f4-910c-4642-a625-9dc0be3cafd8)

{% 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: 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:

```
GET https://build.localwp.com/building/using-local-components.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.