Skill Claude CodeCodex
Design and orchestrate multi-artifact Avonni solutions. MUST activate when a request spans more than one Avonni artifact type (Dynamic Component, Flow Screen Components, Experience site components) or describes a business use case rather than a single named artifact — e.g. a component plus the flow it launches. Do NOT…
Skill Claude CodeCodex
Create or update Avonni Dynamic Components. Use when the user asks to build, generate, or modify a dynamic component, or when working with Dynamic Component JSON, queries, resources, or metadata files. Do NOT use when the request spans multiple Avonni artifact types or describes an end-to-end use case (a component…
Skill Claude CodeCodex
Add, update, or remove Avonni components inside an existing Salesforce Digital Experience site. Use when the user wants to place Avonni components on a site page, when editing a site view's content.json that contains avxp: or avcmpbuilder: components, or when wiring those components to records, navigation, or styling.…
Skill Claude CodeCodex
Add, update, or remove Avonni Flow Screen Components inside a Salesforce flow. Use when the user wants Avonni components in a screen flow, when editing flow XML that contains avcmpbuilder extensions, or when creating a new screen flow built around Avonni components. Does not cover general flow logic (decisions…
Skill Claude CodeCodex
Integrate Avonni components into the code of an LWC component (HTML, JS, CSS). Covers MCP tool usage, attribute/event/type/slot resolution, styling hooks, and validation — not general LWC creation. Trigger when: user asks to add, use, or style an Avonni component in their code; when writing or editing LWC that…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: