avonni-experience-components

Toolset

This skill works exclusively with the experience toolset of the Avonni MCP. All MCP tool calls must include toolset: "experience" where applicable. Do not use this skill for standard Avonni LWC components, Avonni Dynamic Components, or Avonni Flow Screen Components.

Package Namespace

Avonni Experience components are delivered by a managed package whose namespace is either avxp or avcmpbuilder, depending on which package the user's org has installed. The namespace is the prefix of every Avonni component definition in a view's content.json (e.g. avxp:xpcButton or avcmpbuilder:xpcButton).

Detect it once per task in Step 1 by running:

node <skill_base_directory>/scripts/namespace.mjs <path-to-content.json>

The script checks, in order: the AVONNI_XP_PACKAGE_NAMESPACE env var, the namespaces already used by Avonni nodes in the view, and the packages installed in the org (via the Salesforce CLI), falling back to avxp. If it exits with an ambiguity error (both packages installed, no other signal), ask the user which package their site uses before continuing. If it warns that no Avonni Experience package was detected in the org, relay that warning to the user — the components you generate will not render on the site until a package is installed — then continue normally.

Wherever this skill or its references write <namespace>: (or show avxp: in an example), use the detected namespace. Never hardcode a namespace, and never mix both namespaces in the same view.