Skip to main content

How to Write Good Prompts for the Divi AI Agent

Learn how to phrase requests the Divi AI Agent handles well, with dozens of copy-and-paste prompts you can adapt.

The Divi AI Agent is good at a request that says what you want and where you want it.

It is weakest when it has to guess. Most disappointing results are not the Agent failing at a hard job - they are the Agent doing a reasonable job of a vague one.

This article shows you the shape of a request that works, then gives you a library of more than eighty ready-made prompts you can copy, paste, and adapt.

If you have not opened the Agent yet, start with the first-run walkthrough in this collection; if you want the map of what the Agent is capable of rather than how to phrase it, read what the Divi AI Agent can do.

What a Good Request Looks Like

Four habits separate a request that lands from one that comes back not quite right.

Say What "Done" Looks Like

The Agent has to decide when it has finished. If your request has no finish line, it invents one. Give it the outcome, not the mood.

Weak: Make the hero better.

Better: Rewrite the hero heading to be under 10 words, lead with the customer benefit, and keep the button text as it is.

Point at the Thing You Mean

"The button" is ambiguous on a page with nine buttons. Name the module, name the section it sits in, or attach it to the conversation as context so there is nothing to resolve.

Pinning the exact module is faster and more accurate than describing it, and it is covered in the article on context, commands, and attachments in this collection.

Weak: Change the button color.

Better: In the pricing section, set the middle card's button background to #1B2A4A and leave the other two cards alone.

Scope It

A page-wide request gets a page-wide answer. If you only want one section touched, say so. If you genuinely do want the whole page swept, say that too, so the Agent does not stop at the first match.

Weak: Fix the spacing.

Better: Set the top and bottom padding on every section on this page to 80px, and do not change any padding inside the rows.

Say What Not to Touch

This is the habit most people skip, and it is the one that saves the most cleanup. A short exclusion at the end of a request is worth more than a long description at the start.

Weak: Restyle the testimonial cards.

Better: Restyle the three testimonial cards with a 12px radius and a soft shadow. Do not change their text, images, or widths.

Ask First, Then Build

On a page you did not build, or for a change you are not sure about, ask before you build. In Ask mode, the Agent reads your page, explains what it finds, and proposes an approach without touching anything, so you can correct its understanding before any change is made.

Many of the prompts below are deliberately written as analysis first - "list them before you change anything" - and those are the ones worth running in Ask mode.

Once its answer matches what you had in mind, switch to Build and ask for the change. Ask mode and Build mode are covered in full in their own article.

Prompts You Can Copy

Every prompt below corresponds to something the Agent can actually do. Swap in your own module names, colors, and numbers. Several groups cover a Divi feature that has its own article - Presets, Global Variables, Loop Builder, Dynamic Content, Canvases, Workspaces, the Divi Library, and the Theme Builder - and those articles explain the feature itself.

Building Something New

  • Build a three-column pricing section below the hero, with a highlighted middle plan and a button on every card.

  • Create a testimonial section with three quote cards, each showing a photo, a name, a role, and the quote.

  • Add a two-column row under the last section, with an image on the left and a heading, paragraph, and button on the right.

  • Add a four-column CSS Grid row below the intro section and leave the columns empty for now.

  • Show me the premade Flex and Grid structures available, then apply the one closest to a two-thirds and one-third split to the second row.

  • Insert the saved section named Client Logos from my Divi Library at the bottom of this page.

Editing an Existing Layout

  • List the sections on this page in order with a one-line summary of what each contains, before changing anything.

  • Move the testimonials section so it sits directly above the footer call to action, and leave everything else where it is.

  • Duplicate the second pricing card twice, then change only the plan names to Starter, Team, and Enterprise.

  • Delete the empty row between the About section and the contact form, and nothing else.

  • Lock the header section so it cannot be edited by accident, then tell me which modules on this page are already locked.

  • Find every module on this page whose text mentions our old company name, and list them before you change any of them.

Design and Styling

  • Read the design system on this page and tell me which colors, fonts, and spacing values are actually in use.

  • Give every button in the pricing section a 6px border radius and 16px of vertical padding, keeping their current colors.

  • Set the hero section background to a 45-degree gradient running from #1B2A4A to #33507F.

  • Add a hover state to the three feature cards that deepens the shadow and lifts the card slightly.

  • Find repeated styles on this page that would be worth turning into a preset, and list them without creating anything yet.

  • Add an interaction so that clicking the Get Started button applies my Highlighted preset to the pricing card beside it.

Working With Presets

  • Create a Module Preset from the styles on the first button, then apply it to every other button on this page.

  • List the Module Presets that exist for the Text module and summarize what each one changes.

  • Make the preset named Card Shadow the default for every new Blurb module I add.

  • Clone the Primary Button preset, rename the copy to Secondary Button, and change only its background to transparent.

  • Turn the heading styles on the second section into an Option Group Preset and suggest a sensible name for it.

  • Remove the Card Shadow preset from the third blurb only, and leave the other two exactly as they are.

Working With Global Variables and Colors

  • List my Global Variables and tell me which of them this page actually uses.

  • Create a colors Global Variable named Brand Navy and set it to #1B2A4A.

  • Change the value of the Brand Navy variable to #14213D everywhere on the site that uses it.

  • Scan this section for hard-coded color and spacing values and offer to convert them into Global Variables.

  • Add #F5F1E8 and #2E4057 to my Global Colors and name them Sand and Slate.

  • Show me my Global Colors, then replace every use of the light gray background on this page with the Sand color.

Images and Media

  • Generate a wide, calm photograph of an empty office for the hero background and import it into my Media Library.

  • Fetch three stock photos of a bakery interior and put one in each of the three blurb modules.

  • Search my Media Library for images with "team" in the name and list what you find before adding any of them.

  • Describe what is in the image I attached, then write one sentence of alt text for it.

  • Compare this page against the reference screenshot I attached and list the differences before fixing any of them.

  • Import the images I attached into the Media Library and use the first one in the hero image module.

Responsive and Mobile

The Agent can write a value at one breakpoint without disturbing the others, and it can change your breakpoints itself.

  • Set the hero heading to 48px on desktop, 36px on tablet, and 28px on phone.

  • Reduce the top and bottom padding on every section to 40px on phone only, and leave desktop untouched.

  • Switch the builder to tablet view so I can see what you are changing as you change it.

  • Show me my current breakpoint settings and tell me where the phone breakpoint ends.

  • Change the tablet breakpoint to end at 1024px and leave the other breakpoints alone.

  • Read this page at phone width and list anything that looks cramped or too wide, without changing it yet.

Accessibility

  • Add descriptive alt text to every image on this page, based on what is actually in each image.

  • List the heading levels on this page in order and tell me where the hierarchy skips a level.

  • Make the hero heading an H1 and demote the section headings below it to H2.

  • Add an aria-label to each icon-only social link so a screen reader announces where it goes.

  • Tell me the text and background colors used in the hero, and whether that combination is likely to be hard to read.

  • Change the button labeled "Click here" to a label that says where it goes, and keep its styling exactly as it is.

Content and Copy

  • Rewrite the hero heading to be under 10 words and lead with the customer benefit.

  • Shorten every blurb description on this page to two sentences, and do not change the headings above them.

  • Replace "Acme Ltd" with "Acme Group" in every module on this page.

  • Read the text file I attached and use it to fill in the three service descriptions on this page.

  • Read the About page at this address and draft a shorter version of that copy for this page's intro paragraph.

  • Proofread every heading and paragraph on this page and fix typos only. Do not reword anything.

Loops and Dynamic Content

  • Turn the blog row into a loop that shows the six most recent posts in the News category.

  • Show me the loop settings on this module and explain in plain language what each filter is doing.

  • Order this loop by title ascending, and exclude any post tagged Archive.

  • List the Dynamic Content options available for this post type.

  • Set the heading in this loop item to pull from the post title, and the text beneath it from the excerpt.

  • List which modules on this page already have a loop enabled.

Canvases and Workspaces

  • Create a canvas called Mobile Menu and make it global so it is available on every page.

  • Switch to the Popup canvas, add a two-field signup form there, then switch back to the main canvas.

  • List my canvases and tell me which one is currently active.

  • Save my current panel arrangement as a workspace called Copy Editing.

  • Switch to my Design workspace and turn on Wireframe view.

  • Set the builder interface to dark mode and zoom the canvas to 75%.

Pages, Posts and Menus

  • Create a page called Pricing, leave it as a draft, and tell me its link when you are done.

  • Search for every page with "service" in the title and list them with their permalinks.

  • Set every hero button on this page to link to the Contact page.

  • Create a navigation menu called Footer Menu with items for Home, About, Services, and Contact.

  • Assign the Main Menu to the primary theme location.

  • Reorder the main menu so that About is second and Contact is last.

Theme Builder

  • List my Theme Builder templates and tell me which parts of the site each one applies to.

  • Create a Theme Builder template for the blog archive with a custom header and footer.

  • Set this template to apply only to posts in the Case Studies category.

  • Turn off the custom footer on the Shop template so those pages fall back to the default footer, and leave its header alone.

  • Show me my site-wide Theme Options and tell me which of them are not set.

  • Rename the Global Header template to Main Header, and do not change its display conditions.

Learning and Troubleshooting

  • Search Divi's documentation for how Option Group Presets differ from Module Presets and summarize the answer.

  • Explain what the Sizing options on this row are doing, without changing any of them.

  • Tell me which setting is making this section full width, and show me where it is. Do not change it.

  • Walk me through what you changed in the pricing section earlier in this chat.

  • Tell me what theme is active on this site and which post types support the Divi Builder.

  • Explain what would happen if I made this canvas global, before I decide whether to do it.

Turn Your Best Prompts Into Commands

Once a prompt earns its place - the one you paste before every handover, the one that sweeps a page for stray colors - save it as a Command instead of retyping it. Typing / in the composer opens the picker, and the saved text drops straight into your message so you can add the page-specific detail at the end. For more information, check out the [saving prompts as commands] article.

Teach It Your Preferences Once

If you keep adding the same sentence to the end of every request, such as: never use pure black, always ask before deleting anything, keep headings in sentence case, etc., that belongs in a Rule rather than in your prompts.

Rules are standing instructions the Agent applies without you repeating them, which makes every prompt in the library above shorter. For more details, check the How to Use Rules in the Divi AI Agent article.

Pro tips:

  • Match the model to the job. A simple sweep like fixing typos or replacing a company name across a page runs perfectly well on a cheaper, faster model.

  • Save the more expensive models for layout generation and design work, where the extra reasoning actually shows. Choosing a model has its own article in this collection: choosing a model.

Did this answer your question?