Breakdance Pro is the skill that designs. The Breakdance integration gives your assistant the data layer — pages, elements, templates, settings. Breakdance Pro turns a screenshot, an HTML page, a live URL or a Figma frame into a real Breakdance page, template, header, footer, popup or global block.
Why it exists
Any builder tool that works from a written element reference is out of date the day the builder updates. Breakdance publishes its element registry at runtime, so Breakdance Pro reads it and validates against the schema of the install it is actually building on — your license, your subplugins, your third-party packs. A mistyped element slug becomes an error naming the closest match, rather than a blank section someone has to diagnose a week later.
The four ways in
- HTML — paste markup, get a validated section.
- URL — a live page rebuilt as an editable Breakdance template.
- Screenshot — an image or mockup becomes a working page.
- Figma — the frame is read from the file as a node tree, with auto-layout and Variables. Needs a Figma connection; without one the skill says so rather than quietly reading the frame as a picture.
What it builds
- Pages and sections
- Headers, footers, popups and templates — together with their display conditions
- Global blocks
- Loops bound to a post type, where repeated cards were detected
- WooCommerce store templates, from the WooCommerce element catalogue
What makes the output usable
- Elements validated against your registry. Not a static list. Unknown slugs are refused with “did you mean” suggestions from your own install.
- Property paths checked against each element’s real control schema.
- The namespace backslash caught. In JSON it silently breaks every slug, and the page renders empty with no error anywhere.
- Your variables, not new hex codes. Literal colors and sizes that match variables you already defined are reported, so a section follows your palette instead of starting a second design system.
- Templates with their conditions. A template with none is invisible — the most common reason a build looks like it did nothing.
Working on pages that already exist
Refinement happens one node at a time. Changing a heading does not rebuild the page around it, so work someone did by hand survives. Every edit keeps a restorable backup, and an audit runs the same rules against a page that is already live — which is usually how you find out why it renders blank.
Oxygen 6
Works unchanged. Oxygen 6 is the same codebase under a different brand, and every post type and meta key is resolved through Breakdance’s own constants rather than hardcoded, so nothing needs configuring differently.
Abilities
nibwp/breakdance-pro-elements— the element vocabulary this install offersnibwp/breakdance-pro-tokens— variables, selectors and presets already definednibwp/breakdance-pro-validate— check a tree before it is writtennibwp/breakdance-pro-html-to-section— HTML into a sectionnibwp/breakdance-pro-url-to-section— a live URL into a templatenibwp/breakdance-pro-image-to-section— a screenshot into a pagenibwp/breakdance-pro-figma-to-section— a Figma frame as nodes and Variablesnibwp/breakdance-pro-template— headers, footers, popups, templates and their conditionsnibwp/breakdance-pro-loop-plan— repeated cards into a loopnibwp/breakdance-pro-refine— change specific nodesnibwp/breakdance-pro-audit— audit an existing pagenibwp/breakdance-pro-woocommerce— the WooCommerce element cataloguenibwp/breakdance-pro-library— design-library partsnibwp/breakdance-pro-feedback— record what worked
Requirements
- Breakdance 2+ or Oxygen 6, active
- NibWP Pro, Agency or Lifetime
- A Figma connection, only for the Figma path
Pricing
€29 a year for one site, or €59 lifetime. Five, 25 and 100-site tiers are available, and it is included in the Bundle. Get Breakdance Pro.