Kadence Pro

Kadence Pro converts a design into real Kadence Blocks. Not a screenshot pasted into an HTML block, and not markup that renders correctly and cannot be touched: rows, columns, headings and buttons that open in the block editor and can be changed by whoever owns the site.

That last part is the whole point. It is easy to produce markup that looks right on the front end and is dead in the editor, because the blocks are missing the attributes the editor needs to understand them. Kadence Pro treats editability as the requirement and pixel fidelity as the thing that yields when the two conflict.

Design in attributes, not in CSS

Every Kadence block renders from its own attributes at request time, and that single fact shapes how this skill works:

• Attributes, never stylesheets — Set the attribute and Kadence writes the CSS. The client can still edit it afterwards, which a stylesheet would prevent.
• Native blocks only — Rows, columns, advanced headings, buttons, icon lists and info boxes, not a wall of raw HTML.
• Validated before it writes — Nesting, unique IDs, column layout and attribute shapes are all checked first.
• Rendered before it writes — The page is rendered and inspected, so markup that saves cleanly but draws nothing is refused.
• Theme aware — Colors come from the Kadence Global Palette where one matches, so output follows your brand.
• Editable forever — Every element remains a real block with real controls in the editor.

What it exposes

The skill adds these tools once it is unlocked and enabled:

From hours to one prompt

The routine is always the same: preflight, read the playbook, build, dry run, persist.

Rebuild this hero screenshot as a Kadence section

nibwp/skill-preflight (run)
nibwp/load-skill-playbook (run)
nibwp/kadence-pro-list-blocks (run)
nibwp/kadence-pro-image-to-blocks (dry_run)
✓ validated · renders correctly · score 92/A
nibwp/kadence-pro-image-to-blocks (persist)
✓ 7 blocks · editable in Gutenberg

The dry run is not a formality. It validates the tree and renders it, and a conversion that would look broken is refused with the attribute to fix rather than written and discovered later.

What you can build

A few of the things teams build with Kadence Pro:

How it stays safe

• Dry run first — Validation and rendering both run before anything is written.
• Force draft — Large jobs can land as drafts so you review before publishing.
• Scoped tokens — Building pages needs a write scope, which you grant deliberately.
• Every change logged — Each call is recorded with the account, the tool and the result.

Getting started

• Install Kadence Blocks — The skill builds Kadence Blocks, so the plugin has to be active. The theme is optional.
• Unlock the skill — Kadence Pro is a Pro Skill. Activate your license and enable it in NIBWP.
• Run the preflight — nibwp/skill-preflight asks what you are building and where it should go.
• Start with a dry run — Read the validation and the score before you let it persist anything.

FAQ