Avonni Components

List Components

List all known Avonni components name and description, for a given toolset. WHEN TO USE THIS TOOL: - When you need to know the components available in a toolset. - When you need to know the name/description of a component before calling #get_component_docs. EXAMPLE USAGE: - List all components in the "dynamic" toolset. - Pick one or several components that best fit a usage description. - Create a Dynamic Component, without knowing which component(s) to use. - Write LWC code based on a usage de

Get Component Docs

Get detailed documentation for a specific Avonni component. AGENT INSTRUCTIONS: - If you don't know the exact name of a component, call #list_components first. WHEN TO USE THIS TOOL: - When you already called #list_components and you need more information on a specific component. - When you know the exact name of a component and you need more information on its properties, slots, etc. EXAMPLE USAGE: - Create a new component. - Update an existing component. - Explain how to use a component. -

Get Component Styles

Get the available styling hooks (CSS variables) for an Avonni component. WHEN TO USE THIS TOOL: - When you want to add styling to an Avonni component. - When the user asks for the styling options of an Avonni component. AGENT INSTRUCTIONS: - For "dynamic", "flow", and "experience" toolsets: after calling this tool, call #get_style_tokens to retrieve the design tokens relevant to the hooks you plan to use. Tokens are fetched separately and not included in this response. EXAMPLE USAGE: - Add st

Get Style Tokens

Get the design tokens (CSS variable values) available for styling Avonni components. WHEN TO USE THIS TOOL: - After calling #get_component_styles for a "dynamic", "flow", or "experience" component, to retrieve the design tokens you can use as values for the styling hooks. - When styling multiple components: call this tool once for all needed token categories instead of fetching tokens per component. - When the user asks which design token values are available. AGENT INSTRUCTIONS: - Call this t

Get Type

Get the fields of a specific object type (lwc toolset only). WHEN TO USE THIS TOOL: - When you called #get_component_docs for a "lwc" component and you need to know the API of a type it uses. EXAMPLE USAGE: - You called #get_component_docs for the "avonniDdList" component and the documentation says the type of the "mapping" attribute is "DdListMapping". You need to know the definition of "DdListMapping". So you call #get_type with the name "DdListMapping".

List Utils

List all public utility functions available in the Avonni LWC package. WHEN TO USE THIS TOOL: - When you need to know which utility functions are available. - When you need to find the right utility function before calling #get_util_docs. EXAMPLE USAGE: - List all available utility functions. - Find a utility function that removes the page header.

Get Util Docs

Get detailed documentation for a specific Avonni LWC utility function. AGENT INSTRUCTIONS: - If you don't know the exact name of the utility function, call #list_utils first. WHEN TO USE THIS TOOL: - When you need the full signature (params, return type) of a utility function. EXAMPLE USAGE: - Get the documentation for the "removePageHeader" utility function. - Explain how to call a utility function and what arguments it accepts.

List Interactions

List all known interactions that can be used on Avonni Dynamic Components or Flow Screen Components, and a description of when to use them. WHEN TO USE THIS TOOL: - When you need to know the interactions available for a Dynamic Component or Flow Screen Component. - When you need to validate the name of an interaction before calling #get_interaction_docs. - When you want to use an interaction property of a Dynamic or Flow Screen Component. EXAMPLE USAGE: - List all interactions for a Dynamic Co

Get Interaction Docs

Get detailed documentation for a specific Dynamic Component or Flow Screen Component interaction. REQUIREMENTS: - If you don't know the exact interaction name, call #list_interactions first. - #get_interaction_docs accepts a single interaction name. Call it once per interaction if you need several. WHEN TO USE THIS TOOL: - When you already know which interaction to use and you need more information on its properties. EXAMPLE USAGE: - Create a new interaction. - Update an existing interaction.