> 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/designing-your-add-on.md).

# Designing your Add-on

We've made it easy to powerfully integrate your ideas into Local. This section is all about how to craft the best experience around your ideas. Following our standard UI conventions will help ensure your Add-on feels less like an addition, and more like a true part of Local.

The most important step in the Add-on design process is taking the time to define exactly what your Add-on is going to do. What goal is it trying to achieve? What problem is it trying to solve? Who is it for? Once you know the answers to these questions, you can start creating your Add-on with confidence and clarity!

{% hint style="success" %}
When designing your add-on, always focus on what a non-technical user would be thinking -- even if your target user is technical! The benefits of not **needing** to think about how to complete even a seemingly simple task are high and worth the up-front effort.
{% 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/designing-your-add-on.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.