MJC Designs AI Design Assistant for Bricks Builder

Description

MJC Designs AI Design Assistant for Bricks Builder helps you create, refine, and remove page elements through a review-first workflow. It uses the WordPress AI Client to let users choose from compatible provider models connected by the site administrator. Review proposals in a temporary frontend preview and apply only the changes you approve. This is an independent third-party integration and is not affiliated with or endorsed by Bricks Builder or its developers. This alpha release is intended for evaluation. Features may be incomplete; review every proposal and keep a backup before applying changes.

Requirements

  • WordPress 7.0 or later with the WordPress AI Client.
  • A compatible AI provider integration installed and configured under Settings > Connectors.
  • Bricks 2.4 or later, with get-page-elements, set-page-elements, and get-element-schema abilities enabled under Bricks > AI > Abilities.
  • PHP 7.4 or later.

Features

  • List editable WordPress pages and Bricks templates, including pages without existing Bricks elements. Blog posts are not available for editing.
  • Select among compatible AI provider models configured through WordPress Connectors; the user’s model preference is saved to their account.
  • Use compatible vision models with optional JPG, PNG, or WebP reference images up to 5 MB.
  • Read the selected page’s element tree and propose focused edits. Validate setting names and choices against the live Bricks control schema before preview or apply.
  • Change only registered native Bricks controls. AI proposals cannot write code controls or Custom CSS.
  • Add registered Bricks elements, including supported nested elements; move and remove elements while preserving IDs and child data.
  • Review proposals in a temporary frontend preview before applying. Switch preview widths using the site’s configured Bricks breakpoints, including custom labels and widths. Expand the interactive preview in a focus modal or keep using Open preview to open it in a new tab.
  • Open the selected page in Bricks Builder and undo the most recent assistant change.
  • Provide About, Settings, Capabilities, FAQ, Version History, terms, and privacy guidance in WordPress admin.

Provider access, model availability, prices, free tiers, quotas, and data handling depend on the selected service and model. The site administrator should review each provider’s current terms before enabling it. Bricks validates final element data and user permissions. A narrow fallback for some responsive-only settings may not create a native Bricks revision; use the assistant’s Undo action to reverse it.

Source Code

The plugin includes its browser-side source files directly in the distribution. assets/app.js contains the assistant interface JavaScript, assets/admin.css contains its styles, and assets/admin-notices.js contains the admin notice behavior. These are human-readable source files loaded directly by the plugin; they are not minified or generated, and no build tools or separate compilation steps are required.

Privacy

When generating a suggestion, the plugin sends the prompt, selected Bricks document content, and optional reference image to the AI provider and model selected for that request through the WordPress AI Client. WordPress routes the request to the service endpoint provided by the site administrator’s selected Connector; the connector and provider determine any account requirements. Reference images are not added to the WordPress Media Library by this plugin. Provider terms govern how submitted data is processed; site owners should review applicable provider privacy information, terms, usage policies, costs, and free-tier limits.

The plugin does not store prompts or reference images as chat history and does not send telemetry to the plugin author. The site administrator configures provider access under Settings > Connectors. Temporary preview drafts are deleted when the user leaves the workspace, after one hour as a fallback, or when replaced. Database backups and server logs remain subject to the site’s own policies. Review the suggested privacy text in Settings > Privacy before publishing it.

Screenshots

Installation

  1. In WordPress, go to Plugins > Add New Plugin > Upload Plugin.
  2. Upload and activate the MJC Designs AI Design Assistant for Bricks Builder ZIP file.
  3. Install and configure a compatible AI provider under WordPress Settings > Connectors. Provider setup and credentials are managed by the site administrator.
  4. In Bricks > AI > Abilities, enable get-page-elements, set-page-elements, and get-element-schema.
  5. Open MJC Designs AI, choose a configured provider model, select a page or Bricks template, enter a design request, review the preview and proposed edits, then apply them when ready.

When upgrading, the plugin removes credentials left by earlier releases. If you previously added MJC_DESIGNS_AI_DESIGN_ASSISTANT_BRICKS_API_KEY to wp-config.php, remove that unused constant manually.

FAQ

Does the assistant edit blog posts?

No. The assistant edits WordPress pages and Bricks templates. It can configure supported Query Loops to display existing posts, but it does not edit blog post content or create WordPress post records.

How do I connect an AI provider?

A site administrator installs a compatible provider integration and configures it under WordPress Settings > Connectors. Users then choose from compatible configured models in the assistant. Provider credentials are managed by WordPress and the provider integration, not stored by this plugin.

Does using a provider cost money?

It depends on the provider and model selected. Some providers offer free models or free usage tiers; others charge for use. Review the provider’s current terms, pricing, quotas, and data-handling policies before use.

What information is sent to the provider?

The selected provider receives the prompt, selected Bricks document content, and any reference image attached to that request. The plugin does not store prompts or images as chat history and does not send telemetry to the plugin author. Provider handling varies; avoid sending sensitive or personal information unless you have checked the applicable terms and have a lawful basis.

Are previews permanent?

No. The assistant creates private temporary draft previews. It deletes them when the user leaves the workspace, replaces a preview for the same document, or when the one-hour expiration fallback runs. Site backups and server logs follow the site’s own retention policies.

What can the assistant change?

It can change page-content settings and elements exposed by installed Bricks controls and abilities. It does not manage global classes, variables, theme styles, components, media libraries, template conditions, page settings, or WooCommerce setup. AI proposals can edit registered native controls; they cannot write Custom CSS or code controls.

Does MJC Designs AI include the full Bricks Skills package?

No. The plugin uses the WordPress Abilities API directly for page read and write operations. It does not connect through the WordPress MCP Adapter or load the external Bricks Skills package. This release does not expose broader workflows such as global design-system management, media actions, revision browsing, or template and component management.

Reviews

There are no reviews for this plugin.

Contributors & Developers

“MJC Designs AI Design Assistant for Bricks Builder” is open source software. The following people have contributed to this plugin.

Contributors

Changelog

1.1.3

  • Alpha improvement · 2026-10-15 03:49:05 PHT
    • Drag and drop JPG, PNG, or WebP images onto the prompt area to attach a reference image, with clear drop feedback and the existing file checks.
    • Pretty-print object settings with their original keys, quoted string values, and indentation in the Page Elements inspector preview without changing the underlying design data.
    • Replace the three bouncing dots in the main loading modal with the animated MJC Designs AI logo for page loading, applying, undoing, and other busy actions.
    • Load the logo GIF when the modal opens and remove the unused three-dot modal animation styles.
    • Add a Custom viewport control to the expanded frontend preview with editable pixel width and height, without changing the regular preview viewport.
    • Continue the public alpha evaluation phase; suggestions may be incomplete, and bugs or unexpected results are still possible.

1.1.2

  • Review fixes · Alpha · 2026-10-12 21:39:09 PHT
    • Migrate text generation to the WordPress AI Client and add a per-user provider/model selector backed by configured Connectors, with image-capability checks for reference uploads.
    • Restrict AI proposals to registered native Bricks controls; exclude code controls and reject _cssCustom instead of writing arbitrary CSS.
    • Use attached reference images only for their own request and remove remote placeholder-image instructions.
    • Rename the plugin branding to MJC Designs AI Design Assistant for Bricks Builder while retaining the brick-and-spark icon and updating its wordmark.
    • Update privacy and usage disclosures for provider-managed credentials, provider-specific costs, and data handling.
    • Add translator context for the AI provider error message placeholder reported by Plugin Check.
    • Simplify the AI model selector into a compact row and correct its width so it no longer crowds the prompt composer.
    • Move the assistant into a full-height left column, with the app header and workspace tools stacked in the right column.
    • Prefix admin pages, REST routes, asset handles, localized JavaScript data, PHP functions and constants, UI selectors, and new stored data with distinctive MJC Designs identifiers; keep old names only for cleanup of data from earlier alpha builds.
    • Restore tooltip text lookup after prefixing and render the tooltip layer at document level so it can extend beyond workspace clipping while staying within the viewport.
    • Normalize all packaged text files to LF line endings to prevent Plugin Check mixed-line-ending warnings.
    • Build preview viewport buttons from Bricks’ configured breakpoint labels and builder widths, including custom and paused breakpoints; refresh the list when the workspace loads or is refreshed.
    • Add a backdrop modal for the existing interactive frontend preview, with close, Escape, outside-click dismissal, focus handling, and the same breakpoint controls; preserve the separate Open preview action.
    • Pass Bricks controls’ registered required_when dependencies to the AI and validate changed control prerequisites against the final element settings, rejecting flex-direction values when the matching display is not flex or inline-flex.
    • Increase breakpoint and toolbar text sizes inside the expanded preview modal while retaining compact controls in the regular workspace preview.
    • Add a one-step Redo action paired with Undo; preserve stale-document checks and clear the redo snapshot when a new assistant change is applied.
    • Hide the redundant Expand preview action while the preview is already open in its modal.
    • Use the all-caps FRONTEND PREVIEW title in the expanded modal, center regular preview controls, and style Open preview to match the controls.
    • Show an accessible purple circular loading indicator over frontend preview iframes until the page loads, including the cache-busting retry.
    • Guide generation to use only available media references and never invent remote file URLs; remove the last Custom CSS fallback instruction.
    • Identify the plugin as an independent integration in its public description and align minimum-version messages with WordPress 7.0.
    • Clarify in the privacy documentation that provider requests go to the service configured in the selected WordPress Connector.
    • Display the full plugin name and a clear non-affiliation and non-endorsement statement throughout the plugin admin screens, including the main workspace and subpages; align the plugin header description with that wording.
    • Document the included human-readable JavaScript and CSS source files in the readme and clarify that the plugin uses them directly without a build step.
  • Fix · Alpha · 2026-10-11 21:35:23 PHT
    • Normalize generated regular URL links to Bricks’ registered external link type so proposals and previews pass schema validation.
    • Give schema repair attempts direct instructions to remove rejected settings such as unsupported button presets and use only the element’s registered native controls for styling.
    • Clear WordPress post and metadata caches after creating a temporary Bricks preview so the frontend iframe sees newly written elements, including on initially empty pages.
    • Initialize and verify Bricks data on temporary previews for empty pages, then retry a blank frontend iframe once with a cache-busting URL.
    • Translate the common _flexDirection alias only when the target Bricks element registers an equivalent direction control, preventing invalid settings while preserving intended flex layouts.
    • Provide core registered element schemas for blank documents and tell the assistant to build from that schema context instead of refusing image-led or generic design requests.
    • Expose CSS properties and explicit-unit requirements in each live number-control schema, and clarify that dimensions such as full-width _width values must be returned as CSS strings such as “100%” even though the Bricks control type is number.
    • Require explicit units for nonzero CSS dimensions and spacing, validate them against the registered number-control units, and guide repair attempts to correct unitless size values.
    • Mark registered rendered-text controls in the AI schema, require concise placeholder copy for newly added headings, text blocks, and buttons, and retry proposals that leave those elements without rendered text.
    • Preview the current page from a fresh temporary Bricks snapshot on workspace load, after applying changes, and after undoing them, avoiding stale public-page caches in the frontend iframe.
    • Set the Bricks editor-mode metadata when AI writes elements to a blank or WordPress-mode page so frontend templates render the new Bricks content immediately.
    • Use the published page URL for the Current page tab instead of a temporary draft preview, avoiding not-found responses on published pages.
    • Treat each newly attached reference image as authoritative for its request, replace conflicting prior page visuals for replication requests, and prevent stale asynchronous image reads from overwriting a newer upload.
    • Make every parent with children in the Page Elements tree independently collapsible, with accessible expand/collapse controls that preserve the current tree state during redraws.
    • Show the elapsed AI proposal-generation time beneath each successful assistant response, excluding frontend preview preparation.
    • Normalize class-api.php line endings to remove the Plugin Check mixed-line-ending warning.
    • Number each update item in Version History so users can reference a version and a specific update line.
    • Add clear spacing between Version History update numbers and their text.
    • Run WordPress save hooks after Bricks applies or undoes metadata changes, updating the document modified time so page-cache integrations can invalidate cached frontend output.
    • Continue the public alpha evaluation phase; suggestions may be incomplete, and bugs or unexpected results are still possible.

1.1.1

  • Alpha improvement · Alpha · 2026-10-11 03:12:37 PHT
    • Strengthen the AI’s default responsive design requirements across desktop, tablet, and narrow mobile, including checks for clipping, overflow, overlap, and readability.
    • Enforce a server-side guard that rejects max-width settings and Custom CSS declarations on Bricks Container elements before preview or apply.
    • Remove the redundant scrollbar around the frontend preview while retaining scrolling inside the website preview.
    • Use solid primary-purple chat-bubble tooltips and place one info icon beside the Page Elements panel title instead of adding hints to individual rows.
    • Add a click-to-open accuracy note beside Frontend Preview and preserve the permanent milestone row styling exclusively for version 1.0.0 (alpha).
    • Use a deep-purple background for transparent and empty areas of the frontend preview.
    • Truncate long Page Elements labels and selected-document context with ellipses for a more compact workspace.
    • Show image thumbnails beneath image-source settings in the element inspector without changing proposal data.
    • Use Unicode arrows for the panel collapse controls and show the current plugin version at the right end of the alpha banner.
    • Allow pointer and keyboard resizing of the Design assistant panel up to 40% of the workspace while preserving its current minimum width and collapse control.
    • Present Current limitations as a numbered set of short, individually separated statements for easier scanning.
    • Improve information scanning across About, Settings, and FAQ with shorter statements and clearly separated points.
    • Add expandable Read more controls to release entries with more than three update bullets.
    • Paginate Version History at twelve release entries per page with custom purple navigation controls.
    • Continue the public alpha evaluation phase; suggestions may be incomplete, and bugs or unexpected results are still possible.

1.1.0

  • Alpha improvement · Alpha · 2026-10-11 00:57:10 PHT
    • Add a dedicated wrap operation that places an existing Bricks element inside a new registered parent while preserving its ID, settings, nested content, and sibling position.
    • Update proposal previews and AI guidance to support wrapping requests such as placing an image inside a responsive div.
    • Continue the public alpha evaluation phase; suggestions may be incomplete, and bugs or unexpected results are still possible.

1.0.0

  • Alpha release · Alpha · 2026-10-10 02:30:17 PHT
    • Core design and review workflows are available for evaluation. The plugin remains in active development; features may be incomplete, and bugs or unexpected results are to be expected. Review proposals carefully and keep a backup before applying changes.
    • Align the directory package and translation domain with the official plugin name; add privacy export, erasure, user-deletion, and uninstall cleanup.
    • Add translation context for dynamic Bricks messages and tighten Plugin Check compatibility.
    • Add a custom brick-and-sparkle mark and full MJC Designs AI lockup to the workspace header.
    • Add an in-dashboard FAQ page with answers aligned to the readme.
    • Validate nested values against registered Bricks control schemas, including typography, spacing, background, border, and transform properties; normalize typography keys to Bricks format.
    • Support native text-shadow edits in typography controls while preserving other typography settings.
    • Show centered confirmations after applying, undoing, or rejecting proposed changes; rejected proposals restore the saved tree and current-page preview.
    • Use a centered three-dot loading indicator while asynchronous operations are running.
    • Keep brief success confirmations free of backdrop blur while retaining the Apply Changes confirmation styling.
    • Clarify dynamic Bricks validation placeholders for translation and Plugin Check.

0.9.32

  • Improvement · Release · 2026-10-09 23:37:33 PHT
    • Add a compact creator note with an email contact button to plugin subpages.

0.9.31

  • Improvement · Release · 2026-10-09 23:32:15 PHT
    • Add release date and time to the version table.
    • Place added elements at their proposed sibling position in the review tree.

0.9.30

  • Fix · Release · 2026-10-09 22:41:49 PHT
    • Show the current live document in Current page mode and load proposed changes through a WordPress-authorized preview URL.
    • Label each preview mode clearly while switching between them.

0.9.29

  • Interface · Release · 2026-10-09 21:57:28 PHT
    • Make Page Elements and Change Review scroll areas fill their cards instead of using viewport-based height limits.
    • Apply the shared violet and charcoal scrollbar palette throughout the plugin interface.

0.9.28

  • Fix · Release · 2026-10-09 21:20:55 PHT
    • Point Open Preview to the selected page after changes are applied, and use the temporary proposal link while changes await approval.

0.9.27

  • Improvement · Release · 2026-10-09 21:01:00 PHT
    • Use the shared branded confirmation modal when opening a frontend preview.

0.9.26

  • Fix · Release · 2026-10-09 20:46:42 PHT
    • Move an unsupported image grid-span setting onto a validated container wrapper when the live schema allows it.
    • Give Gemini more precise element-specific guidance when correcting rejected settings.

0.9.25

  • Fix · Release · 2026-10-09 20:25:57 PHT
    • Replace the dashboard menu tile with a simple hollow sparkle outline for clearer visibility.

0.9.24

  • Improvement · Release · 2026-10-09 20:21:21 PHT
    • Update the WordPress dashboard menu icon to match the assistant’s sparkle logo.

0.9.23

  • Improvement · Release · 2026-10-09 20:06:42 PHT
    • Match Version History header typography and spacing to the Capabilities table.
    • Use consistent muted separators throughout the release table.

0.9.22

  • Improvement · Release · 2026-10-09 19:59:55 PHT
    • Restyle the Version History table to match the Capabilities page while retaining fix and improvement indicators.

0.9.21

  • Fix · Release · 2026-10-09 19:53:53 PHT
    • Prevent preview and change review panels from overlapping when Page Elements collapses.
    • Give the frontend preview more height while Page Elements is collapsed.

0.9.20

  • Interface · Release · 2026-10-09 19:38:37 PHT
    • Add smooth, responsive controls to collapse the assistant and Page Elements panels.
    • Refresh Settings and other subpages with aligned full-width layouts, consistent spacing, and smaller banner icons.

0.9.19

  • Fix · Release · 2026-10-09 19:09:21 PHT
    • Remove temporary preview drafts when leaving the assistant.
    • Remove blog posts from the editable document list.

0.9.18

  • Privacy · Release · 2026-10-09 18:57:19 PHT
    • Use a general creator attribution on the About page.

0.9.17

  • Interface · Release · 2026-10-09 18:42:12 PHT
    • Refresh Settings and subpage styling; add terms and privacy guidance.

Early 0.x milestones

  • Foundation · Release
    • Add per-user API key settings, privacy guidance, capabilities, About, and terms pages.
    • Add Bricks ability integration and safeguards for reviewing and applying page changes.