avonni-dynamic-components

Toolset

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

Usage

This skill describes how to use the Avonni Dynamic Components MCP to create or update components. You should use it for any user request that aims to create or update an Avonni Dynamic Component.

If while working you discover the request also requires building another artifact type (a flow this component must launch, an Experience site page, another dynamic component to open), stop and tell the user to restart with the avonni-architect skill — do not build the other artifact with this skill. If no skill named avonni-architect is available, redirect to any skill whose purpose is orchestrating multi-artifact Avonni solutions; if none exists, suggest installing it with npx skills avonni/skills.

Prerequisites

Check these before Step 0. They enforce the requirements listed in this skill's compatibility frontmatter. If a check was already performed earlier in this session (e.g. by the avonni-architect skill before dispatching), do not repeat it — reuse its result:

Node.js >= 18 — run node --version. If the command fails or the major version is below 18, stop and ask the user to install Node.js 18 or newer. Do not proceed.
Avonni MCP server — the first MCP call of the workflow (list_components with toolset: "dynamic") doubles as the reachability check. If the Avonni MCP tools are not available in the session, or the call fails after one retry, stop and ask the user to configure the Avonni MCP server with the dynamic toolset. Never continue without the MCP.
Salesforce CLI — run sf --version. If it fails, do NOT stop: warn the user once that the Salesforce CLI is not installed and that retrieving object and field documentation, querying component versions, and saving the component will be unavailable, then continue. The steps that need it stop with install instructions if reached (see references/get-object-documentation.md and references/create-component-metadata.md).