Convert a screenshot, live URL or Figma frame into a validated Bricks template — real core elements, brand-scoped global classes and your ACSS tokens, with query loops backed by CPT + ACF.
Hand Bricks Pro a design and it returns an editable Bricks template that uses only whitelisted core elements, brand-scoped BEM global classes, and your ACSS tokens — never flattened HTML you can't touch in the builder.
Only real Bricks elements are emitted — no junk markup.
Styles become brand-scoped global classes, not inline mess.
Colors, type and spacing map to your ACSS tokens.
Repeating content becomes loops backed by CPT + ACF.
Forms route through the native element — never raw <form>.
Nothing is persisted until you review and approve.
A screenshot, live URL, or a Figma frame.
Nodes become whitelisted core elements with BEM global classes.
Element whitelist, tokens and query loops are checked.
Review, then write the template — only on your OK.
| Tool | Type | What it does |
|---|---|---|
| nibwp/bricks-create-template | write | Generate a validated Bricks template from a design, URL or Figma. |
| nibwp/bricks-detect | read | Detect the Bricks version and global class setup. |
| nibwp/bricks-list-elements | read | List the whitelisted core elements available. |
| nibwp/bricks-validate | read | Validate a template against the element & token rules. |
| nibwp/bricks-apply | destructive | Persist the approved template into your site. |
A screenshot became an editable Bricks template with real global classes. Hours saved per page.
The query loops it wired to our CPT just worked. No hand-fixing.
Finally AI output that opens cleanly in Bricks.
ACSS is recommended for token mapping; Bricks Pro produces safe fallbacks when it is absent.
Never without approval — it generates, validates, and waits for you to confirm.
Yes — repeating content is wired to CPT + ACF query loops, not static copies.
Yes — Bricks Pro and the other three Pro Skills are included in the Bundle.
Get it on its own, or unlock all Pro Skills in the Bundle.