Build with Bricks
Create a native draft and reuse existing Bricks design styles.
Before you start
- EMCP Pro and a verified AI connection.
- Active Bricks theme in the documented supported range; Bricks 2.4.x requires EMCP 3.18.0+.
- A practice site and a draft page.
Let’s do this, step by step.
Step 01
Select and save the builder
Open Setup → Page Builders. Select Bricks under 1. Standalone builder. Choose Save changes. A Not detected card lists missing requirements.
In WordPress, open EMCP Tools, then Page Builders. Under Standalone builder, select Bricks and choose Save changes. If the card says Not detected, check its listed requirements first. Gutenberg can stay available beside this builder.
Step 02
Enable the actions and reconnect
Open Setup → Tools → Bricks. Inspect read and write switches; enable the actions needed for this practice task, then Save changes and reconnect your AI app.
Open Tools and select the Bricks tab. Turn on the read tools and editing actions this lesson needs. On a new installation these Pro tools start switched off. Choose Save changes, then reconnect your AI app so it sees the updated list.
Step 03
Inspect before building
Ask the AI to read Bricks's context, supported element controls, and existing design settings.
Ask what this installed version can actually edit. Seeing an element in the catalog does not always mean EMCP can create or change it.
Step 04
Create a native draft
Ask for a small services-page draft using sections, headings, and a contact button.
Create one draft and keep its returned ID. The AI should assemble real Bricks elements and use the latest saved version for each change.
Inspect Bricks context, element controls, and existing design styles. Create a draft services page with a hero, three services and a contact introduction. Use native elements, preserve global settings, and do not publish.
Step 05
Reuse styles at the correct scale
Read bricks-get-context root_font_size.rem_px and the design system. Reuse existing class IDs. Inspect native_abilities for Bricks’ separate AI capability status. EMCP does not create global classes or template conditions.
Before choosing spacing, ask the AI to read Bricks’ root font size and existing styles. Bricks often uses a ten-pixel base for rem units, so assuming sixteen pixels can make the layout too small. Reuse existing classes. Bricks’ own AI abilities are a separate feature, enabled by an administrator in Bricks Settings, then AI.
Step 06
Refine the phone layout
Preview the draft and request one targeted change to spacing or image crop on mobile.
Name the existing page and element so the AI edits that result. Do not start another page just to adjust the phone view.
Step 07
Check interactions and custom CSS
Use current native schemas. In 3.20, existing global classes, element display conditions and safe interactions are accepted; executable JavaScript interactions remain excluded. Verify custom CSS and checkbox behavior in Bricks.
If the design includes interactions or custom CSS, inspect those settings in Bricks after saving. Test buttons, sliders and display conditions. A successful response does not show whether the visitor sees the intended behavior.
Step 08
Read back and preview
Read the saved page again. Open the native editor, then inspect the frontend at desktop and phone widths.
Check the saved content, editing controls, images, and links. If a newer edit is detected, read it before trying again. A save response alone does not prove the page looks right.
You’re done when…
The Bricks result remains natively editable and the intended save/publication state is verified.
Keep the reference handy.
The docs cover tool details and requirements for this lesson.
You only need the guide for the app or builder you use. Ready to build? Try an Elementor draft or use Gutenberg.
A brief becomes a real page.