What it does
Every other builder tool works from a documentation file that went out of date the day the builder updated. Breakdance publishes its element registry at runtime, and Breakdance Pro reads it — so elements are validated against the install it is actually building on, with your license, your subplugins and your third-party packs. A mistyped slug is an error message naming the closest match, not a blank section nobody can explain a week later. It goes further than placing boxes. Literal colors and sizes that match variables you already defined are reported, so a new section follows your palette instead of starting a second design system. Repeated cards are recognized and planned as a loop bound to a post type. Headers, footers, popups and templates are created together with their display conditions, because a template with no conditions is invisible — and that is the single most common way a build appears to have done nothing at all. Figma frames are read from the file as structure: node tree, auto-layout, and Variables matched against yours by value. Not looked at as a picture. That path needs a Figma connection, and the skill says so plainly rather than quietly handing back screenshot-quality output and letting you find out later.
Key capabilities
Validated against YOUR install
Element slugs and property paths checked against the live registry, not a doc that went stale.
Screenshot, HTML, URL or Figma
Four ways in, one validated Breakdance page out.
Your variables, not new hex codes
Literal colors and sizes are matched against variables you already defined.
Repeated cards become a loop
Detected and planned as a loop bound to a post type, not eight copies.
Templates with their conditions
A header or template with no display conditions is invisible. It builds both.
Refine one node at a time
Change a heading without rebuilding the page around it.
How it works
Hand it the source
A screenshot, some HTML, a URL, or a Figma frame.
Read your install
The element registry, variables, selectors and presets you already have.
Validate, then write
Every slug and property path checked first; a dry run shows you the plan.
Assign it
Page, template, header, footer, popup or global block — with display conditions.
AI abilities
| Tool | Type | What it does |
|---|---|---|
| nibwp/breakdance-pro-elements | read | The element vocabulary this install actually offers. |
| nibwp/breakdance-pro-tokens | read | Variables, selectors and presets already defined on the site. |
| nibwp/breakdance-pro-validate | read | Check a tree before it is written — slugs, paths, namespaces. |
| nibwp/breakdance-pro-html-to-section | write | HTML into a validated Breakdance section. |
| nibwp/breakdance-pro-url-to-section | write | A live URL rebuilt as an editable template. |
| nibwp/breakdance-pro-image-to-section | write | A screenshot or mockup into a working page. |
| nibwp/breakdance-pro-figma-to-section | write | A Figma frame read as nodes and Variables, not as a picture. |
| nibwp/breakdance-pro-template | write | Headers, footers, popups and templates with their display conditions. |
| nibwp/breakdance-pro-loop-plan | read | Turn repeated cards into a loop bound to a post type. |
| nibwp/breakdance-pro-refine | write | Change specific nodes on a page that already exists. |
| nibwp/breakdance-pro-audit | read | Audit an existing page against the same rules. |
| nibwp/breakdance-pro-woocommerce | read | The WooCommerce element catalogue for store templates. |
| nibwp/breakdance-pro-library | read | Design-library parts, so new sections match what is approved. |
| nibwp/breakdance-pro-feedback | write | Record what worked so later builds improve. |