**Version:** 2.0.0 **Updated:** 2026-06-30 **Freshly updated:** v2.0.0 weaves in the current Respira safety and precision flow — `respira_find_builder_targets` to inventory and scope the Divi source pages up front, a `respira_get_snapshot` checkpoint before any write, and
Installs just this skill. Get the whole plugin for auto-invocation.
⚡ How it fires
How this skill gets triggered: by you, by Claude, or both.
Fires itselfClaude auto-loads it when your prompt matches the work.
You can call itInvoke it directly when you want it.
Slash command/migrate-divi-to-bricks
👁️ Context preview
The summary Claude sees to decide when to auto-load this skill.
**Version:** 2.0.0 **Updated:** 2026-06-30 **Freshly updated:** v2.0.0 weaves in the current Respira safety and precision flow — `respira_find_builder_targets` to inventory and scope the Divi source pages up front, a `respira_get_snapshot` checkpoint before any write, and
# Migrate Divi to Bricks
**Version:** 2.0.0
**Updated:** 2026-06-30
**Freshly updated:** v2.0.0 weaves in the current Respira safety and precision flow — `respira_find_builder_targets` to inventory and scope the Divi source pages up front, a `respira_get_snapshot` checkpoint before any write, and surgical fixes via `respira_find_element` + `respira_update_element` (and `respira_batch_update` for multi-element or multi-page corrections) instead of re-injecting whole pages. Rollback is now explicit (restore the snapshot, delete the draft duplicates). Reflects the current 16 supported builders.
Converts Divi-built WordPress pages to Bricks Builder. Parses Divi's shortcode-based content from post_content, maps each module to its Bricks element equivalent, generates a migration plan for approval, and writes clean Bricks JSON to the target pages. Use this skill whenever someone wants to move from Divi to Bricks, replace the Divi Builder with Bricks, or rebuild Divi pages in Bricks.
## What This Skill Does
This is a cross-format migration — Divi stores content as nested shortcodes in `post_content`, while Bricks uses a JSON array in `_bricks_page_content_2`. The skill must parse Divi's shortcode hierarchy, understand each module's purpose and settings, then reconstruct that intent as Bricks elements with proper parent-child relationships and settings.
The format gap makes this complex, but both builders are feature-rich visual editors, so most Divi modules have strong Bricks equivalents. The result is cleaner, faster-rendering content in Bricks' modern architecture.
**Handles:**
- et_pb_section → Bricks Section element
- et_pb_row/et_pb_column → Bricks Container elements (with flex layout)
- et_pb_text → Bricks Text Basic element
- Spacing (margin, padding) — converted from Divi's format to Bricks'
- Background images and overlays
- Border and shadow settings
- Button labels, URLs, targets
- CSS classes
## What This Skill Does NOT Do
- **Specialty sections** — Divi's specialty section layouts (sidebar + content) need manual layout setup in Bricks.
- **Global modules** — Divi's global modules (`et_pb_layout` post type) are resolved to inline content. Bricks templates must be set up separately.
- **Third-party Divi modules** — Plugins extending Divi (Divi Toolbox, Divi Supreme, etc.) are flagged for manual recreation.
- **Divi theme customizer** — Global fonts, colors, and spacing from the Divi theme customizer don't transfer. These need to be set in Bricks theme settings.
- **Dynamic content** — Divi's dynamic content needs Bricks' dynamic data system configured separately.
- **Contact forms** — et_pb_contact_form needs to be rebuilt using Bricks' form element or a forms plugin.
- **Divi Library layouts** — Stored as `et_pb_layout` post type; not auto-migrated to Bricks templates.
- **Motion effects** — Scroll effects and animations differ between builders.
- **Divi theme dependency** — If using the Divi theme (not just plugin), you are switching to Bricks theme — a complete theme change.
## Requirements
- Respira for WordPress plugin installed and connected
- MCP connection active (desktop or WebMCP)
- Divi theme or Divi Builder plugin active (to read source content)
- Bricks theme installed and active (to write target content)
- Read access to scan Divi content
- Write access to create duplicates with Bricks content
## Trigger Phrase
- "migrate divi to bricks"
## Alternative Triggers
- "convert divi to bricks"
- "switch from divi to bricks"
- "rebuild divi pages in bricks"
- "move from divi to bricks"
- "divi to bricks migration"
- "replace divi with bricks"
## Source Builder: Divi
Divi stores content as shortcodes in `post_content`. The module structure follows a strict hierarchy:
- Map Divi attributes to Bricks settings (colors, spacing, typography)
- Generate unique IDs and proper parent references
- Flag unmappable modules with comments
4. Take a `respira_get_snapshot` checkpoint of the target before any write, so the page can be restored exactly if the conversion needs unwinding
5. Create duplicate via `respira_create_page_duplicate` or `respira_create_post_duplicate`
6. Write Bricks JSON to the duplicate via `respira_inject_builder_content` with `builder=bricks`
7. Surgical fixes (not a re-inject): when a single element lands wrong — a heading, a button label, a container width — locate it with `respira_find_element` and correct it in place with `respira_update_element`. For repeated corrections across many elements or several migrated pages, batch them with `respira_batch_update` rather than re-injecting whole pages.
