Skip to main content

How To Use KrafterPRO + Divi AI Agents.

Divi AI Agents runs inside the Visual Builder as your logged-in admin. KrafterPRO can't pre-approve or block what it does — but it can (a) feed it your live design system as rules so it builds on-token, and (b) score, log and roll back every session afterward. So your job is: set the rules once, prefix each build, then verify with KrafterPRO.


KrafterPRO + Divi AI Agents — Mini Manual

What you get

Divi AI already sees your tokens, colours and presets (it reads the same Divi stores KrafterPRO writes). What it doesn't know on its own: which token to use when, the type-vs-colour rule, "never invent a new variable," and it has no score or undo. KrafterPRO supplies all of that.

1. One-time setup — the Always-On rule

  1. In wp-admin: KrafterPRO → AI tab → "Divi AI" card → Always-On rules for Divi AI.
  2. If you see a Send to Divi AI button (Divi 5.12+), click it. Otherwise click Copy, then in the Visual Builder open Divi AI → Saved site rules, paste, and switch Always-On on.
  3. Do not paste this into the Build chat — that makes Divi AI generate a page from the rules.

This is your safety net: presets still get named even on builds where you forget the prefix.

2. Every build — the prefix

  1. From the same card, copy Build command for Divi AI (the "governed-build" prefix). Save it once into Divi AI → Reusable commands as governed-build.
  2. At the start of every Build, run governed-build, then continue with your actual request in the same message.
  3. It does two things: names your live presets in chat (so generate_layout is allowed to apply presets afterward) and sets a definition of done — no raw px/rem/hex on type, every heading/text on a preset.

3. Clean-up commands (use as needed)

Save these from Commands for Divi AI into Reusable commands and run one at a time on a finished page:

Command Use it to
Audit this page against our design system List every hardcoded value and name the token/preset it should bind
Replace hardcoded spacing/colour with our variables Rebind px/hex to your scale tokens
Consolidate repeated styles into our presets Fold repeated one-off styling into presets
Fix text contrast to WCAG AA Move failing text onto your colour-role presets
Standardise headings to our type presets without changing colour Size/weight/line-height from type presets; colour stays put

4. After every Divi AI session — verify

  1. Design Health — run it to score what actually changed.
  2. Protect → Activity log — every mutation the agent made is recorded, with actor.
  3. Rollback — if a run went wrong, revert it in one step.
  4. Optional belt-and-braces: KrafterPRO → Apply design system to bind and clean anything the agent left as inline styles.

5. Re-sync the rules when the system changes

After Brand Studio edits or an Import, go back to the Divi AI card and Send / re-copy the Always-On rule so the vocabulary matches the live kit.

Do / Don't

  • ✅ Prefix every Build with governed-build; keep Always-On enabled as the fallback.
  • ✅ Run clean-up commands on finished pages, one at a time.
  • ✅ Design Health after every session.
  • ❌ Don't paste rules into the Build chat.
  • ❌ Don't let the agent invent new variables/presets — the rules tell it to stop and report instead.
  • ❌ Don't skip the post-session check; that's where KrafterPRO earns its keep.

Want this as a published one-page artifact (styled, shareable link) or a Markdown file in the repo for your docs?

WPTierz Laurent

Markdown MD

Would be great to have a tutorial for this!

One-Page artifact please.