Avonni Components, for every Salesforce screen
Five component lines for the four places you build: Lightning pages, screen flows, Experience Sites, and your own code. Start where you are building today.
Where are you building?
Five lines, each with its own hub. Pick the surface you work on, and the quickstart is one click away.
App Builder Components
Sixteen ready-made components you drag onto a Lightning page and configure in the App Builder. Nothing to build, nothing to code.
Dynamic Components
Compose your own component: pick the data, the layout, and what happens on click, then place it on any App, Record or Home page.
Flow Screen Components
Over seventy components for screen flows: collect data, guide a wizard, show a calendar or a map without leaving the flow.
Experience Sites Components
Over forty components for Experience Cloud sites, with the same data sources and interactions as the rest of the suite.
LWC Components
Production-ready building blocks for developers writing their own Lightning Web Components, including data driven ones that query records with no Apex.
Not sure which line you need?
Three pages answer it: the decision path, the five lines side by side, and the package that carries the one you picked.
Build it with an AI assistant
Describe what you want in plain language, and Claude, Cursor or GitHub Copilot builds real Avonni components on all four surfaces. Setup takes about ten minutes, once.
Set it up once
One MCP server, one set of skills. Your assistant then looks up the real component knowledge instead of guessing.
Prompt libraries
Copy-paste prompts organized by goal, one library per surface.
For AI agents
Everything here is machine readable: Markdown URLs, a full index, and an endpoint that answers questions about the docs.
See what others have built
Projects built end to end in a real org, with the screenshots and the configuration behind each one.
