Overview

Connect your AI assistant to the Avonni MCP server and install the Avonni Skills to build and update Avonni components on your Experience Site pages from plain-language prompts.

🚧 Early access. Build with AI is rolling out gradually and improving with every release. Something unclear, missing, or broken? Tell us: your feedback directly shapes what we improve next.

Describe what you want in plain language, and your AI assistant (Claude, Cursor, or GitHub Copilot) adds real, working Avonni components to your Experience Site pages. Two tools make that possible:

🧠 Avonni MCP server

A hosted documentation service that gives the assistant accurate, always up-to-date knowledge of all 44 Experience Cloud Components: their properties, interactions, and styling.

🛠️ Avonni Skills

Step-by-step workflows that teach the assistant how to add Avonni components to a site page and configure them correctly.

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.

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 interaction types, and produce page content that Experience Builder rejects. 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, interactions, and styling for the experience package, plus the dynamic, flow, and lwc packages.	No more invented properties or interaction names. The assistant looks up the real configuration 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 produces valid page content and follows the correct order of operations instead of improvising.

Fast today, maintainable tomorrow

An AI assistant could also build your portal features as custom code, fast. The difference shows up after the demo: custom code is yours to maintain forever, and on a customer-facing site, that risk is public. Avonni components avoid the trap:

✍️ Configuration, not code	A prompt produces page content: which components, which data, which interactions, with your site's branding through design tokens. No custom JavaScript running in front of your customers.
🛡️ The complexity is Avonni's to maintain	Data Table, Kanban, Calendar, and the rest live in the managed package: tested, versioned, updated with every release. Update the package, and what the AI built keeps working.
🧩 Your site builders stay in control	What the AI builds is a normal Experience Builder page, using the same components your team already configures by hand. Anyone can open it, understand it, and evolve it.

What the assistant produces

The avonni-experience-components skill works on your site page's content file. It adds the Avonni component to the page and configures its data, appearance, and interactions. Nothing is deployed: you review the file, deploy it with your usual process, then open the page in Experience Builder to check the result and publish the site.

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.

Example: "Add a case list to my support portal page, and a screen flow for creating a case that opens from a button." The architect builds the flow first, then adds the components to the page with the button wired to open that flow.

In this section