avonni-flow-components

Toolset

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

Scope

This skill governs only the Avonni screen component fields inside a flow — <fields> elements whose extensionName starts with avcmpbuilder:. It covers how to discover, configure, validate, and write those fields into a .flow-meta.xml file.

It does not cover general flow logic. When a request also requires decisions, assignments, loops, record operations, or other flow elements, build the Avonni screen fields with this skill and handle the rest of the flow outside of it. When updating an existing flow, never restructure, reformat, or rewrite anything outside the Avonni component fields you were asked to change.

If the request also requires building the artifact that launches or hosts this flow (a Dynamic Component, an Experience site page), stop and tell the user to restart with the avonni-architect 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: