> For the complete documentation index, see [llms.txt](https://docs.avonnicomponents.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avonnicomponents.com/dynamic-components/build-with-ai/overview.md).

# Overview

{% hint style="warning" %}

#### 🚧 **Early access**

Build with AI is rolling out gradually and improving with every release. Something unclear, missing, or broken? [Tell us](/dynamic-components/resources/contact-support.md): your feedback directly shapes what we improve next.
{% endhint %}

Describe what you want in plain language, and your AI assistant (Claude, Cursor, or GitHub Copilot) builds real, working Dynamic Components. 

Two tools make that possible:

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>🧠 Avonni MCP server</strong></td><td>A hosted documentation service that gives the assistant accurate, always up-to-date knowledge of every Dynamic Component: properties, interactions, and styling hooks.</td><td></td></tr><tr><td><strong>🛠️ Avonni Skills</strong></td><td>Step-by-step workflows that teach the assistant how to create and update Avonni artifacts, including the Dynamic Component metadata format.</td><td></td></tr></tbody></table>

{% hint style="success" %}
**In short: skills tell the agent what to do; the MCP tells it what's true.** Using one without the other gives worse results. Install both.
{% endhint %}

## Why you need both

AI assistants are trained on public data, so their knowledge of Avonni is incomplete and out of date. Left on their own, they invent property names, guess at styling hooks, and misunderstand the metadata format. The result looks plausible but doesn't work.

The two tools solve different halves of the problem:

|                   | What it provides                                                                                                                                             | What it fixes                                                                                               |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------- |
| **Avonni MCP**    | *Knowledge.* Accurate component documentation, styling hooks, and interactions for the `dynamic` package, plus the `lwc`, `flow`, and `experience` packages. | No more invented properties or styling hooks. The assistant looks up the real API instead of guessing.      |
| **Avonni Skills** | *Process.* Workflows for creating and updating each Avonni artifact type, plus `avonni-architect`, which coordinates multi-artifact use cases.               | The assistant follows Avonni's artifact formats and the correct order of operations instead of improvising. |

## Fast today, maintainable tomorrow

An AI assistant could also build what you're asking for as custom code, fast. The difference shows up after the demo: **custom code is yours to maintain forever.** Dynamic Components avoid that trap:

<table><thead><tr><th width="280"></th><th></th></tr></thead><tbody><tr><td>✍️ <strong>Configuration, not a codebase</strong></td><td>A prompt produces a compact metadata file: which components, which data, which interactions. No custom JavaScript to inherit.</td></tr><tr><td>🛡️ <strong>The complexity is Avonni's to maintain</strong></td><td>Data Table, Kanban, Charts, and the rest live in the managed package: tested, versioned, updated with every release. Update the package, and what the AI built keeps working.</td></tr><tr><td>🧩 <strong>Consistent with everything else</strong></td><td>The AI uses the same components as the Dynamic Component builder, so it all looks, behaves, and evolves together.</td></tr></tbody></table>

## From a single component to a complete use case

Real requirements rarely stop at one artifact. The `avonni-architect` skill turns a business outcome into a plan, then invokes the right skills in dependency order so every piece is wired to the others correctly.

{% hint style="info" %}
**Example:** *"Create a dynamic component with a button that launches a screen flow."* The assistant builds both the Dynamic Component and the flow in one pass, with the component's interaction correctly pointing at the flow.
{% endhint %}

<a class="button primary" data-icon="plug">Set it up in minutes</a>

## In this section


---

# 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.avonnicomponents.com/dynamic-components/build-with-ai/overview.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.