If you find yourself typing the same request more than once, save it as a custom command.
A command is a prompt you write once and reuse - a job you want done, ready to fire off with a slash instead of typing it out again.
Creating a Command
Open the Divi AI Agent by clicking on the Divi AI Agent icon
in the left sidebar.Click the Commands icon
to open the command list.Click Add New Command. The AI Command Editor opens.
Fill in the two fields:
Title - Give this command a short name to identify it in the commands list.
Command - Write the exact instruction the AI agent should follow.
Save the Command by clicking the Save Command button.
Running a Command
Type / anywhere in the AI Agent chat window to open the commands picker, or open the commands list from the Commands icon and choose the command you want to use.
Either way, the saved text is inserted into the chat rather than sent right away - exactly what the Command field's helper text describes. That pause is useful: before you hit send, you can read the command back, tighten it, or add the one detail that's specific to this page, like a section name or a color.
Commands Worth Saving
The prompts below are pulled straight from How to Write Good Prompts for the Divi AI Agent, adapted to read as saved commands. Paste any of them into the Command field as-is.
Add descriptive alt text to every image on this page, based on what is actually in each image. Skip any image that already has meaningful alt text.
Run an accessibility pass on this page: list the heading levels in order and flag any skipped levels, check whether the text and background color combinations are likely to be hard to read, and list every image missing alt text. Don't change anything yet - just report what you find.
Read this page at phone width and list anything that looks cramped or too wide, without changing it yet.
Proofread every heading and paragraph on this page and fix typos only. Do not reword anything.
Read the design system on this page and tell me which colors, fonts, and spacing values are actually in use.
Scan this page for hard-coded color and spacing values and convert them into Global Variables, creating a new one only when nothing existing already matches.
Find every module on this page whose text mentions our old company name, and list them before you change any of them.
Save the ones you reach for often. A command you never reuse isn't worth the trip to the editor - the whole point is skipping the retyping.
Adding Context to a Command
A command can point at something specific instead of describing it in words.
Open the AI Command Editor by clicking on the Command icon
.Click Add New Command.
Give the command a descriptive title.
Click the Add Context icon
. Select the element (attach a preset, variable, or other piece of context ) you want to use as context.
Example:
A color-conversion command can point straight at the Global Variable you want hardcoded values replaced with, instead of you naming it in the command text every time.
Nesting Commands
Commands can also contain each other.
Open the AI Command Editor by clicking on the Command icon
.Click Add New Command.
Give the command a descriptive title.
Click the Commands icon
to open the command list.Choose the commands you want to nest.
Note: Custom Commands already used as a nested command will not be able to be selected more than once.
Editing, Duplicating and Deleting Commands
In the AI Agent chat window, click on the Rules icon
. Hover over a custom rule:
Edit Rule
: Edit the selected rule.Duplicate Rule
: Duplicate the current rule and use it as a starting point for a new rule.Delete Rule
: Delete the selected rule.
If you ask the AI Agent to update or delete a command for you in chat, rather than doing it from the list, it always asks for confirmation first - this is one of the Agent's higher-risk actions. For more details, check the Approvals and Risk Levels in the Divi AI Agent article.
Pro tip: A saved command runs against whatever page you happen to be on when you trigger it, not the page you were looking at when you wrote it. Keep the wording explicit about scope - "on this page," "in the pricing section," "every image here" - so a command that means one page-wide sweep doesn't quietly do something narrower, or wider, on the next page you run it on.