Deep Intelligence April 14, 2026

Respira × Breakdance

Breakdance Deep Intelligence

The deepest Breakdance Builder MCP integration available. 84 elements cataloged across 7 categories. 120+ CSS properties in the schema. Nesting validation catches structural errors. Fuzzy matching corrects AI typos. Content and design data preserved on round-trip. Eight ready-to-use layout patterns.

Plugin 6.3.0 MCP Server 6.3.0 Breakdance 1.x – 2.6+
Download 6.3.0 Read the full story
Registered elements
84
Schema properties
120+
Layout patterns
8
New capability
Full Intelligence

Problem 1

Breakdance had zero intelligence — only generic tree traversal, no validation, no element awareness

Shipped fix

84-element registry, 120+ schema properties, nesting rules, fuzzy matching, 8 layout patterns

Problem 2

AI sends invalid nesting like a Heading inside Columns — stored without error, renders broken

Shipped fix

Nesting validator catches Columns→Column, AdvancedAccordion→Content, AdvancedSlider→Slide rules

Problem 3

Content/design data was flattened into a single blob — round-trip lost Breakdance's native structure

Shipped fix

Simplify/complexify preserves content and design sub-objects with backward-compatible fallback

Builder coverage

Breakdance joins Bricks, Elementor, Divi, Gutenberg, Beaver Builder, Avada, WPBakery, Themify, Brizy, GeneratePress, Flatsome, and Oxygen as the 13th builder with Deep Intelligence — the full treatment of element registry, schema, validator, and pattern library.

The Breakdance logo and brand identity are the property of Soflyy. Their use here is purely illustrative of product compatibility. Respira is not affiliated with, endorsed by, or an officially recognised solution of Breakdance. All trademarks belong to their respective owners.

Deep Intelligence for Breakdance

Breakdance had a solid adapter but zero intelligence. Now it gets the full treatment.

Breakdance is a modern, performance-focused WordPress page builder with 130+ elements, themeless mode, Element Studio for custom components, and deep WooCommerce integration. Its JSON-based tree structure and content/design data split make it powerful — but also meant the intelligence layer had to understand element namespacing, strict nesting rules, numeric ID sequencing, and the content/design data separation to work correctly.

6.3 brings Breakdance from Smart Defaults to Full Intelligence. The element registry now catalogs 84 elements (up from 44 hardcoded) across 7 categories. The schema describes 120+ CSS and content properties. The validator enforces nesting rules, detects duplicate IDs, validates enum values, and uses Levenshtein distance for fuzzy property matching. The adapter preserves the content/design data split on round-trip and tracks _nextNodeId to prevent ID collisions. Eight layout patterns give AI agents ready-made starting points.

The key architectural insight: Breakdance elements use the EssentialElements\\ namespace for all type identifiers, and store element data in data.content (text, URLs, settings) and data.design (typography, spacing, colors) sub-objects. The previous adapter flattened this into a single blob. Now the intelligence layer understands and preserves this structure, so round-trip editing works without data loss.

What changed

AI creates a Column outside of Columns — nesting validator warns that Column should only appear inside Columns.

AI sends backgrondColor: "#333" to a Breakdance Heading — gets a warning: “Unknown property. Did you mean backgroundColor?”

AI injects 20 new elements — _nextNodeId is automatically updated to prevent collisions with the visual editor.

AI edits a Section's padding — design sub-object is preserved separately from content, matching Breakdance's native format.

Every scenario above works automatically in 6.3. Breakdance intelligence activates when Breakdance is detected.

Problem 1 to Fix 1

Only 44 elements recognized out of 130+ available.

The Breakdance adapter had a hardcoded list of 44 elements with no descriptions, no property information, and no category organization. AI agents had no way to discover the full range of available elements or understand their capabilities. Advanced elements like AdvancedAccordion, ContentToggle, and WooCommerce components were entirely missing.

  • What the user experienced

    AI could only work with basic elements. Asking it to create an accordion, slider, or WooCommerce product grid resulted in unknown element types or generic fallbacks.

  • Why it happened

    No element registry existed. The adapter returned a flat array of names without types, properties, or categories. No runtime detection of available elements.

  • What shipped

    84-element registry with dual detection: runtime API via Breakdance's ElementRegistry when available, hardcoded fallback with full metadata. 7 categories, EssentialElements\\ namespace, per-element properties.

  • Benefit

    AI knows every element Breakdance offers, its category, description, and properties. WooCommerce elements are conditionally available. 24-hour transient caching keeps it fast.

Element awareness comparison

AI asks which elements are available for building a page

New in 6.3
Before (hardcoded list) Result
get_available_modules()

Returns 44 elements with name only

Limited
No WooCommerce, no Advanced elements

AdvancedAccordion, ContentToggle, ProductBuilder missing

Incomplete

AI can only use basic elements. No descriptions, no properties, no categories.

After (element registry) Result
get_available_modules()

Returns 84 elements with full metadata

Complete
7 categories, WooCommerce conditional

Every element has type, description, category, properties

Cataloged

AI can discover and use any Breakdance element. Full property schemas available per element type.

The registry uses dual detection: runtime API when Breakdance's ElementRegistry is available, hardcoded fallback with 24-hour transient caching otherwise.

Problem 2 to Fix 2

Invalid nesting stored without error, rendered broken.

Breakdance has strict parent-child rules: Columns must contain Column children, AdvancedAccordion must contain AdvancedAccordionContent. But the data format doesn't enforce these rules — any element can be placed anywhere. When AI created invalid nesting, the data was stored successfully but the page rendered broken or empty sections.

  • What the user experienced

    AI placed a Heading directly inside Columns instead of inside a Column. The section rendered empty. No error indicated why.

  • Why it happened

    No validation layer existed between AI output and Breakdance data storage. Any tree structure was accepted, even structurally invalid ones.

  • What shipped

    Nesting validator with 4 strict parent-child rules. Child-only type enforcement. Duplicate ID detection. Enum validation for 9 CSS properties. Fuzzy matching for unknown property names.

  • Benefit

    Structural errors caught before injection. AI gets actionable warnings instead of silently broken pages. Nesting violations are warnings (non-blocking) so edge cases still work.

Validation behavior comparison

AI creates an accordion with wrong child types

New in 6.3
Before (no validation) Result
inject_content([AdvancedAccordion > Heading])

Invalid child stored in tree

Stored
Accordion renders empty

Breakdance ignores non-AccordionContent children

Broken

Page shows empty accordion. AI thinks edit succeeded. User sees nothing.

After (nesting validation) Result
inject_content([AdvancedAccordion > Heading])

Warning: Heading should not be a direct child of AdvancedAccordion

Warning
AI self-corrects: uses AdvancedAccordionContent

Valid structure injected — accordion renders correctly

Fixed

Nesting error caught before injection. AI gets specific guidance on required child types.

Nesting rules are enforced as warnings, not errors. This means edge cases (custom elements, unconventional layouts) still work, but AI gets clear guidance on expected structure.

Problem 3 to Fix 3

Content and design data lost on round-trip editing.

Breakdance separates element data into data.content (text, URLs, toggle states) and data.design (typography, spacing, colors, layout). The previous adapter flattened everything into a single attributes object. On round-trip (extract → AI edit → inject), the content/design separation was lost, causing Breakdance to misinterpret which properties are content vs. design.

  • What the user experienced

    After AI editing, elements lost their design settings or content appeared in the wrong panel in Breakdance's visual editor.

  • Why it happened

    simplify_structure() merged data.content and data.design into a flat attributes object. complexify_structure() wrote it all back as a single data blob.

  • What shipped

    simplify_structure() now outputs attributes.content, attributes.design, and attributes._raw. complexify_structure() rebuilds the native format. Backward-compatible with old flat format.

  • Benefit

    Round-trip editing preserves Breakdance's native data structure. The visual editor shows content and design in their correct panels after AI edits.

Data structure comparison

AI extracts, edits, and re-injects a Breakdance heading

New in 6.3
Before (flat attributes) Result
extract → {attributes: {text, fontSize, ...}}

Content and design merged into single object

Flattened
inject → {data: {text, fontSize, ...}}

Written back as flat data — Breakdance confused

Lost

Design settings appear in content panel. Visual editor shows wrong values in wrong places.

After (preserved split) Result
extract → {content: {text}, design: {fontSize}}

Content and design preserved as separate keys

Preserved
inject → {data: {content: {...}, design: {...}}}

Native Breakdance format rebuilt correctly

Native

Round-trip preserves native structure. Visual editor works correctly after AI edits.

The new format is backward-compatible: if AI sends flat attributes (old format), complexify_structure() still handles them correctly by treating the entire object as data.

Closing

The deepest Breakdance Builder MCP integration available.

84 elements. 120+ schema properties. Nesting validation. Fuzzy matching. Content/design preservation. _nextNodeId tracking. 8 layout patterns. No other AI tool — no other WordPress MCP server — offers this level of Breakdance-specific intelligence.

And unlike single-builder tools, these capabilities sit alongside Respira’s 131 core tools, 21 WooCommerce tools, and dedicated intelligence for 12 other page builders. The same AI assistant that deep-edits your Breakdance site can also manage WooCommerce, run accessibility audits, analyze SEO, handle media operations, and work with any other supported builder. One tool, one MCP connection, full WordPress control.

Whether you are building with Breakdance 1.x or 2.6+ with its tree_json_string format, Respira detects what you have and adapts. The intelligence layer knows your builder. The AI knows your elements. The validator catches mistakes before they reach your pages.

What shipped in 6.3

Five new intelligence files, one upgraded adapter: registry, schema, validator, patterns, and loader.

The 84-element registry and nesting validator are the headline features, but the content/design data preservation and _nextNodeId tracking matter for daily use. When AI knows that Columns must contain Column children, and that AdvancedAccordion requires AdvancedAccordionContent, errors are caught before they reach the page.

Feature 1

84-element registry with dual detection

Every Breakdance element is now cataloged: layout containers (Section, Columns, Column, Div, Grid), basic elements (Heading, Text, RichText, Button, Image, Video, Icon), 25 blocks (AnimatedHeading, FAQ, Gallery, Tabs, PricingTable, and more), site builders (HeaderBuilder, MenuBuilder, Popup), dynamic elements (PostLoopBuilder, Breadcrumbs, ArchiveTitle), forms, and 13 WooCommerce elements. Runtime detection via Breakdance's ElementRegistry API with hardcoded fallback.

  • 7 categories: Basics (13), Blocks (25), Site (7), Advanced (10), Dynamic (12), Forms (4), WooCommerce (13)
  • WooCommerce elements conditionally included via class_exists('WooCommerce')
  • 24-hour transient caching with manual cache flush support

Feature 2

Nesting validator with fuzzy matching

Breakdance has strict parent-child rules that aren't enforced at the data level. The new validator catches invalid nesting before injection: Columns must contain Column children, AdvancedAccordion must contain AdvancedAccordionContent, AdvancedSlider must contain AdvancedSlide. Child-only types are flagged when placed outside their required parent. And when AI misspells a property name, Levenshtein fuzzy matching suggests the closest known property.

  • Nesting rules for 4 strict parent-child relationships with non-blocking warnings
  • Levenshtein distance with threshold max(3, 40% of input length) for typo detection
  • Enum validation for 9 CSS properties with allowed value lists

Feature 3

Content/design data preservation

Breakdance separates element data into content (text, URLs, settings) and design (typography, spacing, colors) sub-objects. The previous adapter flattened everything into a single attributes blob, losing this structure on round-trip. Now simplify_structure() preserves the split, and complexify_structure() rebuilds it — with backward compatibility for the old flat format.

  • data.content and data.design preserved as separate keys in simplified output
  • _raw key captures other data properties (respiraManaged, html, etc.)
  • Backward-compatible: flat attributes from old format still work in complexify_structure()

  • 120+ schema properties

    The property schema covers typography (fontFamily, fontSize, fontWeight, lineHeight, letterSpacing, textTransform, textAlign, color), layout (display, flexDirection, justifyContent, alignItems, flexWrap, gap, gridTemplateColumns), sizing and spacing (width, height, min/max variants, margin, padding with per-side granularity), backgrounds, borders, effects (boxShadow, textShadow, opacity, filter, transform, transition), and position properties. Responsive breakpoints: Desktop (default), Tablet, Phone.

  • 8 layout patterns

    Full-structure JSON patterns for common layouts: hero section with centered heading and CTA, three-column features with IconBox elements, call-to-action section, testimonial grid with FancyTestimonial, FAQ accordion with AdvancedAccordion, pricing table with three-tier layout, image-text split with Columns, and post loop with PostLoopBuilder. Each uses EssentialElements\ namespace with numeric IDs and proper data.content/data.design split.

  • _nextNodeId tracking

    Breakdance uses an incrementing _nextNodeId counter for new elements. Before this release, injected content could create ID collisions because the counter was not updated. Now after every injection, find_max_node_id() recursively scans the tree for the highest numeric ID and sets _nextNodeId to max + 1.

  • Duplicate ID detection

    The validator tracks every element ID seen during validation. If the same ID appears twice anywhere in the tree — including deeply nested children — a validation error is raised before injection. This prevents the subtle rendering bugs and JavaScript errors that occur when Breakdance encounters duplicate element IDs.

Try it

Example prompts for Breakdance sites

These are real prompts you can paste into Claude, Cursor, or any MCP-connected AI agent. Each one leverages Breakdance Deep Intelligence under the hood.

Build a pricing section

build_page + Breakdance patterns

Prompt

Add a three-column pricing table to the pricing page. Use Breakdance Columns with a PricingTable in each Column. Basic at $9, Pro at $29, Enterprise at $99.

What happens

  1. AI uses the pricing-table pattern as a starting template
  2. Creates EssentialElements\Columns with 3 Column children, each containing PricingTable
  3. Nesting validation confirms Columns contains only Column children
  4. _nextNodeId updated after injection to prevent ID collisions

Find and update content

find_element + update_element

Prompt

Find the hero heading on the homepage and change it to “Build faster with AI”. Also update the font size to 48px.

What happens

  1. find_element locates the EssentialElements\Heading in the hero section
  2. update_element changes data.content.text and data.design.typography.fontSize
  3. Content/design split preserved in the update
  4. CSS cache cleared via breakdance_clear_cache action

Create a FAQ section

build_page + faq-accordion pattern

Prompt

Build an FAQ section with 5 questions about our product. Use Breakdance's AdvancedAccordion element with collapsible sections.

What happens

  1. AI uses the faq-accordion pattern with AdvancedAccordion parent
  2. Creates 5 AdvancedAccordionContent children with question/answer content
  3. Nesting validator confirms AccordionContent children are valid
  4. Each element gets a unique numeric ID; _nextNodeId updated

Responsive styling

update_element + schema

Prompt

Make the hero heading 48px on desktop, 36px on tablet, and 28px on mobile. Center-align it on all breakpoints.

What happens

  1. AI sets fontSize in data.design for desktop default
  2. Schema provides responsive breakpoint info: Desktop, Tablet, Phone
  3. Validator confirms fontSize and textAlign are known properties with valid values
  4. Design sub-object preserved separately from content on update

Validate a layout

validate + inject_builder_content

Prompt

I have a JSON structure for a testimonial grid. Validate it against Breakdance's element rules before injecting it.

What happens

  1. Validator checks all element types against the 84-element registry
  2. Nesting rules verify parent-child relationships
  3. Duplicate ID check scans entire tree
  4. Fuzzy matching suggests corrections for misspelled properties

Builder diagnostics

get_builder_info

Prompt

What page builder is this site using? Show me its capabilities, the version, and what intelligence features are available.

What happens

  1. get_builder_info detects Breakdance and reports version
  2. Reports Full Intelligence level with 84 elements and 120+ properties
  3. Shows themeless mode status, WooCommerce integration, and Element Studio support
  4. AI knows exactly what it can do before starting any edits

Technical details

What shipped

  • Element registry expanded to 84 elements across 7 categories — Basics, Blocks, Site, Advanced, Dynamic, Forms, and WooCommerce
  • Schema properties expanded to 120+ — typography, layout (flex/grid), sizing, spacing, background, border, effects, position, and responsive breakpoints
  • Layout validator with nesting rules — Columns must contain Column, AdvancedAccordion must contain AdvancedAccordionContent, AdvancedSlider must contain AdvancedSlide
  • Child-only type enforcement — Column, AdvancedAccordionContent, AdvancedSlide, and ContentToggleContent flagged when placed outside their required parent
  • Levenshtein fuzzy matching on property names — unknown properties get "did you mean?" suggestions with configurable distance threshold
  • Enum validation for tag, display, position, textAlign, flexDirection, justifyContent, alignItems, objectFit, and overflow
  • Content/design data split preserved — simplify_structure() separates data.content, data.design, and _raw keys; complexify_structure() rebuilds them
  • _nextNodeId tracking — after content injection, maximum numeric element ID is scanned and counter updated to prevent ID collisions
  • 8 full-structure layout patterns — hero-section, three-column-features, call-to-action, testimonial-grid, faq-accordion, pricing-table, image-text-split, post-loop
  • WooCommerce elements conditionally registered — 13 WooCommerce-specific elements included only when WooCommerce is active
  • Duplicate ID detection — validator flags repeated element IDs across the entire tree before injection
  • get_available_modules() delegates to registry when intelligence is loaded — from 44 hardcoded elements to 84 cataloged
  • get_builder_schema() delegates to schema class — full property types, responsive breakpoints, quick reference, and structure notes
  • get_documentation() enriched with patterns and element catalog when intelligence is active

Breaking changes

None in this release

  • No breaking changes. Breakdance intelligence activates automatically when Breakdance is detected.
  • Content/design split is backward-compatible — old flat attributes still work in complexify_structure().
  • All existing Respira settings, snapshots, and configurations are preserved.

Migration guide

What to do next

  • Update the plugin to 6.3.0 from your WordPress dashboard.
  • Update MCP server: npm i -g @respira/wordpress-mcp-server@6.3.0
  • Breakdance intelligence activates automatically when Breakdance is detected — no configuration needed.
  • Works with Breakdance 1.x and 2.6+ (tree_json_string format handled transparently).
  • All existing Respira settings, snapshots, and configurations are preserved.

How to upgrade

Coordinated release — update both plugin and MCP server.

Plugin

WordPress Admin -> Plugins -> Update Respira for WordPress to 6.3.0

MCP Server

# Update to 6.3.0 for Breakdance Deep Intelligence
npm i -g @respira/wordpress-mcp-server@6.3.0
# Or use npx (always runs latest):
npx -y @respira/wordpress-mcp-server

Verify Breakdance Deep Intelligence

  1. Update to 6.3.0 from your WordPress dashboard.
  2. Ask your AI assistant to run get_builder_info and confirm Breakdance shows “Full Intelligence” with 84 elements.
  3. Test nesting validation: ask AI to create a Column outside of Columns and check for the nesting warning.
  4. Test fuzzy matching: intentionally misspell a property and check for “did you mean?” suggestions.

Previous release

Before 6.3 went deep on Breakdance, 6.2 brought intelligence to Oxygen Builder.

Oxygen Deep Intelligence: 49 components, 140+ schema properties, fuzzy matching settings validator, data repair pipeline, Oxygen 6 detection, and 10 layout patterns.

Read the 6.2 Oxygen Deep Intelligence story

Join the Community

Connect with other Respira users. Get help, share prompts, and see what others are building.

Respira for WordPress GitHub Community

Discussions, Wiki, Issues. Searchable. Permanent. Best for troubleshooting, prompt recipes, and feature requests.

Open Community Hub →

Respira Discord

Real-time chat. Quick questions. Voice debugging. Hang out with other builders.

Join Discord →