**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-gutenberg
👁️ 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 Gutenberg
**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-block or multi-page corrections) instead of rewriting 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 native Gutenberg blocks. Parses Divi's shortcode-based content from post_content, maps each module to its closest core block equivalent, generates a migration plan for approval, and writes clean block markup to the target pages. Use this skill whenever someone wants to move from Divi to Gutenberg, eliminate the Divi dependency, switch to native blocks, or simplify their WordPress stack by removing Elegant Themes' builder.
## What This Skill Does
Divi stores everything as nested shortcodes directly in `post_content` — a fundamentally different approach from JSON-based builders. The content is a hierarchy of `[et_pb_section]`, `[et_pb_row]`, `[et_pb_column]`, and `[et_pb_module]` shortcodes with settings as attributes. Converting this to Gutenberg blocks means parsing that shortcode tree, extracting content and settings, and generating the equivalent `<!-- wp:block -->` markup.
This is one of the more complex migrations because Divi shortcodes often contain escaped HTML, base64-encoded content, and deeply nested attribute strings that need careful parsing.
**Handles:**
- et_pb_section → Group block with layout settings
- et_pb_row/et_pb_column → Columns and Column blocks
- et_pb_tabs/et_pb_tab → Group with heading blocks
- et_pb_toggle → Details block (WP 6.3+)
- et_pb_code → Custom HTML block
- et_pb_sidebar → Widget block
- et_pb_gallery → Gallery block
- et_pb_counters → HTML approximation
- Fullwidth variants (et_pb_fullwidth_*) → full-width Group blocks
**Preserves:**
- All text content and inline HTML formatting
- Image URLs, alt text, and links
- Heading text and hierarchy
- Button labels, URLs, and targets
- Video URLs and embed sources
- List content
- Code block contents
- Basic color settings where Gutenberg supports them
## What This Skill Does NOT Do
- **Divi's visual design layer** — Divi applies extensive CSS through its settings (gradient backgrounds, custom fonts from 800+ Google Fonts choices, box shadows with specific blur/spread, text shadow, filters, transforms). Gutenberg supports some of these; many will be simplified or lost.
- **Specialty sections** — Divi's specialty section layouts (sidebar + content combinations) have no direct Gutenberg equivalent.
- **Global modules** — Stored as `et_pb_layout` post type. These are resolved to inline content during migration; Gutenberg reusable blocks can be created manually afterward.
- **Divi Builder plugin modules** — Modules added by Divi-specific plugins (Divi Toolbox, Divi Supreme, etc.) are flagged.
- **Theme customizer settings** — Divi theme customizer values (global fonts, colors, sizing) don't transfer to block themes.
- **Dynamic content** — Divi's dynamic content features need separate solutions.
- **Contact forms** — et_pb_contact_form needs a forms plugin (WPForms, etc.).
- **Divi Library layouts** — Template library layouts stored in et_pb_layout post type are not auto-migrated.
- **Advanced design settings** — Rounded corners, CSS filters, blend modes, and transforms have limited Gutenberg support.
## 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)
- WordPress 6.0+ (6.3+ recommended for Details block support)
- A block-compatible theme ready for post-migration (if switching from Divi theme)
- Read access to scan Divi content
- Write access to create duplicates with Gutenberg content
## Trigger Phrase
- "migrate divi to gutenberg"
## Alternative Triggers
- "convert divi to blocks"
- "switch from divi to gutenberg"
- "remove divi builder"
- "rebuild divi pages with blocks"
- "divi to block editor"
- "decommission divi"
- "get off divi"
## Source Builder: Divi
Divi stores content as shortcodes in `post_content`. The module structure follows a strict hierarchy:
- Map background colors to Group block style attributes
- Flag unmappable modules with `<!-- MIGRATION NOTE: ... -->`
4. Assemble complete block markup
5. Take a `respira_get_snapshot` checkpoint of the target before any write, so the page can be restored exactly if the conversion needs unwinding
6. Create duplicate via `respira_create_page_duplicate` or `respira_create_post_duplicate`
7. Write the block markup to the duplicate via `respira_update_page` or `respira_update_post`
8. Surgical fixes (not a rewrite): when a single block lands wrong — a heading, a button label, a column width — locate it with `respira_find_element` and correct it in place with `respira_update_element`. For repeated corrections across many blocks or several migrated pages, batch them with `respira_batch_update` rather than regenerating and re-writing whole pages.
9. Report: modules converted, items flagged, layout changes made
### Phase 4: Post-Migration Verification
1. Summarize all migrations
2. For each migrated page:
- Link to edit in Gutenberg
- Flagged items
- Layout simplification notes
3. Post-migration checklist:
- [ ] Open each duplicate in block editor — verify blocks parse correctly
- [ ] Check responsive preview
- [ ] Verify all images and media
- [ ] Test links and buttons
- [ ] Recreate forms with a dedicated forms plugin
- [ ] Recreate sliders if needed (or use a block-based slider)
- [ ] Plan theme switch if on Divi theme (do this after all pages are verified)
- [ ] Check page speed improvement
- [ ] Review for Divi shortcode remnants in content
## Safety Model
- Read-only analysis first — full content scan before any changes
- Explicit user confirmation required before creating duplicates
- Original Divi pages are never modified or deleted
- All migrated content goes to draft duplicates only
- Never auto-publishes migrated pages
- Takes a `respira_get_snapshot` checkpoint before each write
- Explicit rollback: restore the snapshot via `respira_restore_snapshot`, or delete the draft duplicates if they are not wanted
- Warns about theme dependency if using Divi theme
## Honest Disclaimer
This skill converts Divi page content to Gutenberg blocks and creates draft duplicates for review.
It cannot:
- Replicate Divi's visual design precision in Gutenberg
- Convert specialty section layouts perfectly
- Migrate contact forms, sliders, or animations
- Handle third-party Divi plugin modules
- Switch your theme for you (if on Divi theme)
- Replace manual review and fine-tuning
It can:
- Convert 60-75% of standard Divi modules to clean blocks
- Extract all text, images, and links from shortcode markup
- Eliminate Divi dependency for simpler pages
- Dramatically improve page load speed
- Parse complex Divi shortcode encoding
- Provide a clear map of manual work needed
- Keep original pages completely safe
## Tooling
**Core WordPress tools**
- `respira_get_site_context`
- `respira_list_plugins`
- `respira_list_pages`
- `respira_list_posts`
- `respira_read_page`
- `respira_read_post`
- `respira_get_builder_info`
- `respira_extract_builder_content`
- `respira_find_builder_targets`
- `respira_create_page_duplicate`
- `respira_create_post_duplicate`
- `respira_update_page`
- `respira_update_post`
- `respira_get_snapshot`
- `respira_restore_snapshot`
- `respira_find_element`
- `respira_update_element`
- `respira_batch_update`
## Telemetry
After run completion, send fire-and-forget usage tracking to:
