> For the complete documentation index, see [llms.txt](https://docs.avonnicomponents.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avonnicomponents.com/experience-cloud/build-with-ai/prompt-library.md). # Prompt Library {% hint style="warning" %} 🚧 **Early access.** Build with AI is rolling out gradually and improving with every release. Something unclear, missing, or broken? [Tell us](/experience-cloud/help/how-do-i-contact-support.md): your feedback directly shapes what we improve next. {% endhint %} Every prompt on this page is ready to paste into Claude, Cursor, or GitHub Copilot once your assistant is set up. Copy one, swap in your own objects and fields, and send. The assistant verifies every component and interaction against the MCP server before generating, so you can be ambitious. {% hint style="info" %} **How to adapt a prompt:** replace the objects (`Case`, `Order`, `Account`) and groupings with yours, and describe the outcome you want. You don't need to name properties or settings: the assistant looks up what exists and configures it. Data visibility follows your org's sharing rules: portal users only see records they have access to. {% endhint %} ## Customer support portal The pages your customers visit when something needs fixing. > Add a Kanban of the customer's Cases grouped by status to my support page. > Add a case list to my support portal page, with a button that opens a screen flow in a dialog for creating a case. > Add a Data Table of the customer's Cases with a Download action for the attached file on each row. ## Self-service account pages Let customers find their own answers before they open a case. > Add a Data Table of the customer's open Orders to the account page, and navigate to the record when a row is clicked. > Add a Profile Card showing the logged-in user's details at the top of the page. > Add a Record Detail of the customer's subscription with the key fields. ## Content and engagement Make the site feel alive, not like a database with a login. > Add a Banner with a title, a background image, and a call-to-action button to the home page. > Add a Gallery of product images to the home page. > Add a Feed and a Publisher to the community page so members can post and comment. > Add a Video Player with our onboarding video to the getting-started page. ## Navigation and structure > Add a Navigation menu with links to the support, orders, and account pages. > Organize the FAQ page content into an Accordion with a section per topic. > Add Tabs to the account page separating orders, invoices, and settings. ## Complete use cases When a request spans several artifacts, `avonni-architect` plans and builds all the pieces in the right order. > Add a case list to my support portal page, and a screen flow for creating a case that opens from a button. > Build an order tracking experience: a Data Table of the customer's Orders, and a screen flow in a side panel to report a problem with an order. *** ## Make these prompts yours * **Name real objects and fields.** "A Data Table of `Order` records filtered on the logged-in user's account" beats "a table of orders". * **Iterate in the same conversation.** Follow up with "change the grouping to priority" or "add a search bar": the assistant updates the same page. * **Think portal-first.** Say who sees the page ("customers", "partners") and the assistant configures the data scope accordingly, within your sharing rules. {% hint style="success" %} Not set up yet? The whole thing takes a few minutes: Setup. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.avonnicomponents.com/experience-cloud/build-with-ai/prompt-library.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.