Prompt Library

Copy-paste prompts for building Dynamic Components with your AI assistant, organized by goal.

🚧 Early access

Build with AI is rolling out gradually and improving with every release. Something unclear, missing, or broken? Tell us: your feedback directly shapes what we improve next.

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 property against the MCP server before generating, so you can be ambitious.

How to adapt a prompt: replace the objects (Account, Case, Opportunity) 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.

Record page essentials

Components that give a record page its core information at a glance.

Create a Dynamic Component for the Account record page showing a Data Table of the account's open Cases with inline editing.

Open cases on the account. Subject, Priority and Status are editable in place: hover a cell and the pencil appears.

Build a component with a Map of the account's billing address and an Avatar with the account owner's details.

The billing address on a map, the account owner beside it.

Add an Activity Timeline of the record's recent Tasks and Events.

Tasks and events on one timeline, grouped by week, most recent first.

Dashboards and metrics

Turn Salesforce data into something the team actually looks at.

Build a dashboard component with a Chart of Opportunities by stage and a Pivot Table of revenue by region and quarter.

Both halves of the dashboard: amount by stage above, revenue by region and quarter below, with a grand total.

Create a component showing this month's closed-won Opportunities in a List, sorted by amount.

This month's closed-won opportunities, largest amount first.

Team productivity

Working views for people who live in Salesforce all day.

Create a Kanban of my team's Opportunities grouped by stage, with drag and drop between columns.

Opportunities grouped by stage. Cards drag between columns to move a deal.

Build a List of today's new Leads with a button on each row that opens the record.

Every row carries its own Open action.

Create a Repeater of my open Tasks displayed as cards, ordered by due date.

One card per open task, soonest due date first. Each status carries its own icon and color: blue for in progress, grey for not started, orange for waiting.

Look and feel

Styling requests work in plain language too.

Restyle my component to match our brand: white cards, rounded corners, and our primary color on buttons.

The same component before and after the restyle: white card, rounded corners, and the brand color on the button.

Make the Data Table denser and add a search bar.

The same table with a search bar above it and tighter rows.

Complete use cases

When a request spans several artifacts, avonni-architect plans and builds all the pieces in the right order.

Create a screen flow for logging a customer visit, and a Dynamic Component with a button on the record page that launches it.

The record-page component. Its Log a visit button launches the screen flow the same prompt asks for.

Build a case management component with a Kanban of Cases, plus a screen flow to escalate a case that opens from each card.

Cases by status. Escalate sits on each card's menu, and opens the escalation flow.

---

Make these prompts yours

• Name real objects and fields. "A Data Table of Invoice__c records filtered on Status__c = 'Overdue'" beats "a table of invoices".
• Iterate in the same conversation. Follow up with "make the columns sortable" or "change the grouping to owner": the assistant updates the same component.
• Chain goals. Start with the component, then ask for the flow it should launch. The architect keeps the pieces wired together.

Not set up yet? The whole thing takes a few minutes: Setup.