Novamira Pro - Memory and expertise for your AI v1.10.0 Nulled

View hidden content is available for registered users!

Novamira Pro - Memory and expertise for your AI v1.10.0 Nulled (Pro + Core)
= v1.10.0 - 2026/09/14

• New: Dynamic Content for Elementor specialization gives AI agents dedicated guidance for working with the plugin and lets them manage its PDF templates. A companion skill covers its features and workflows.
• New: JetElements specialization gives AI agents dedicated guidance for working with the plugin in Elementor. A companion skill covers its features and workflows.
• New: Ultimate Addons for Elementor specialization gives AI agents dedicated guidance for working with the plugin in Elementor. A companion skill covers its features and workflows.
• New: Happy Addons specialization gives AI agents dedicated guidance for working with the plugin in Elementor. A companion skill covers its features and workflows.
• New: Unlimited Elements for Elementor specialization gives AI agents dedicated guidance for working with the plugin in Elementor. A companion skill covers its features and workflows.
• New: Qi Addons for Elementor specialization gives AI agents dedicated guidance for working with the plugin in Elementor. A companion skill covers its features and workflows.
• New: Element Pack specialization gives AI agents dedicated guidance for working with the plugin in Elementor. A companion skill covers its features and workflows.
• New: HT Mega specialization gives AI agents dedicated guidance for working with the plugin in Elementor. A companion skill covers its features and workflows.
• New: PowerPack for Elementor specialization gives AI agents dedicated guidance for working with the plugin in Elementor. A companion skill covers its features and workflows.
• New: Piotnet Addons for Elementor specialization gives AI agents dedicated guidance for working with the plugin in Elementor. A companion skill covers its features and workflows.
• New: Xpro Elementor Addons specialization gives AI agents dedicated guidance for working with the plugin in Elementor. A companion skill covers its features and workflows.
• New: Bricks changes made by AI agents can be undone. Every content change is saved into a WordPress revision before it is written, so you can roll it back from the post's revision history, and a change is held back while someone else has that post open in the builder unless you ask for it to go through anyway.
• New: Bricks pages are checked on the site before an AI agent reports them as done. It loads the page the way a visitor would, so one that errors, comes out blank or loses its styles is caught and reported as a problem rather than handed over as finished.
• New: AI agents can manage Mosaic sub classes, Variants and variant sub classes, not just top-level Classes, and pick a Variant only from the ones an element supports. Class names are saved exactly as Mosaic would save them from its editor, including its automatic renaming when a name is already taken, and deleting a Class also removes it from the elements that used it, as in the editor.
• Tweak: The Elementor page building tools now offer the new atomic element types only on sites where Elementor has them enabled, so an agent no longer builds a page out of elements the site cannot render. Reading a page that already contains such elements now reports which ones are not registered, instead of returning a tree that looks complete while the page renders empty.
• Tweak: The Elementor page building tools now describe the shape of an element inside their own input schema — which keys a node takes, which of them accept a second spelling, and which are refused — instead of leaving it to the surrounding prose. An agent reading the tools no longer has to guess the shape of the content it is about to write.
• Tweak: An AI agent that pastes a whole section's markup into a single Bricks text element is now stopped and told to build the section out of separate elements, so what it hands over stays editable in the builder rather than arriving as one block of text. Empty sections and containers are reported the same way.
• Tweak: Bricks styles lead on Bricks sites. With an active Novamira design the agent works from your Bricks classes, variables and theme styles first and uses the design to fill gaps or when you ask for it; without one, Bricks is the single source of truth and no design document is created unless you ask for it.
• Tweak: A Divi layout the builder itself would not accept is now saved with a warning naming what that container does take, instead of being refused, and changing a setting that alters what a container may contain now rechecks its contents and reports anything that no longer fits. Divi error messages also name the container's actual variant and only ever suggest something Divi accepts there.
• Tweak: On a Mosaic install that still uses its older class storage, the class and variant tools explain that Mosaic needs updating, while themes, templates, page elements, components, collections and variables keep working.
• Tweak: Memory can now be turned on or off from the Novamira Features page, and its admin menu follows that setting.
• Fix: An Elementor page built with the new atomic elements on a site where Elementor does not have them enabled now comes back as an error naming the feature to turn on, instead of a success reply that leaves the page empty. Elementor silently drops element types it cannot build and saves nothing in their place, so everything an agent sent that way was lost while the write still reported success.
• Fix: Elementor writes are now checked against what was actually stored down to the nested elements, so content dropped below the top level comes back as an error instead of passing as saved.
• Fix: Listing Elementor widgets filtered by the atomic source now returns those widgets, where it previously came back empty on every site, including sites that have the new elements enabled.
• Fix: Narrowing an Elementor widget's controls to a single tab or section now returns those controls, where both filters previously came back empty for every widget on every site. On sites where the tools cannot confirm a widget's controls were handed over in full, narrowing by tab is now refused with an explanation instead of returning a partial list that looked complete.
• Fix: Inserting a ready-made Elementor subtree now accepts either spelling of an element's type, the same as writing a whole page. Inserting used to accept only one spelling, so a subtree an agent had just written could come back refused when it tried to insert that same content again.
• Fix: An Elementor element written without a type is now refused wherever it appears in a subtree, not only when it is the outermost one. Such an element still rendered on the page, but Elementor itself stopped counting it as an element: exporting the page, saving it as a template, and Elementor's own content clean-up all walked straight past it and logged PHP warnings on the way.
• Fix: Reading an Elementor page no longer hands back content the writing tools would then refuse. Any misspelled element keys found on the page are now listed separately instead, so nothing is lost, and rewriting the page clears them for good.
• Fix: An Elementor element that names a widget but no element type is now understood instead of refused, wherever it appears in a subtree — the widget name already says what the element is. This also makes pages that were saved earlier with that gap editable again through either writing tool.
• Fix: The short one-line form for an element's styles now works when writing a page or inserting a subtree, as it already did when adding or editing a single element. The same styles were valid in one tool and rejected by another.
• Fix: The Elementor page building skill now spells out the whole widget discovery call, so building a page no longer stops at that first step. Two of its instructions left out something the discovery tool requires, and an agent that followed either one was turned back with an input error before it could look up a single widget.
• Fix: Elementor content is no longer written to posts that cannot hold an Elementor page, such as another plugin's own template store. A write aimed at such a post now comes back as an error naming the post and its post type, instead of reporting success and leaving behind content nothing ever reads.
• Fix: Elementor's dynamic tags now keep working on the new element types when an AI agent applies one, storing the choice the way Elementor records it so the element shows what it should and the page still saves in the editor. A tag aimed at something no longer on the site, or a value Elementor would reject, is now refused with an explanation before anything is written.
• Fix: An Elementor element that has no link keeps it that way when an AI agent edits anything else on it. Editing only the text used to fill the empty link setting in with a default target and tag, which changed the element on every edit and made an empty link impossible to set back.
• Fix: Elementor settings that hold a structure rather than a single value, such as a link, a form field's options, an element's extra attributes, and display conditions, are accepted in the exact form Elementor stores them in again. A malformed or generically typed value that Elementor would reject anyway is now refused up front, instead of being saved in a shape the editor rejects.
• Fix: Adding or editing a single Elementor atomic element now runs Elementor's own validation over its settings before saving, the same check writing a whole page already had. A setting that used to save and report success, only for Elementor to refuse the element on its next save, now comes back as an error naming the setting, and nothing is saved.
• Fix: An Elementor image setting is no longer offered to AI agents as a place to attach a dynamic tag. The tag belongs on the image source inside the setting, not on the setting itself, so attaching it there was stored in a form Elementor does not read and the image stayed empty; the agent is now told so and pointed at the settings that do take a tag.
• Fix: Elementor elements an AI agent has just added to a page now arrive with their own styling, because the page's stylesheet is rebuilt from the content that was saved. A new icon now keeps the size it was given and a new grid stays a grid, where either could previously come out at default size or collapsed into a single column.
• Fix: The tool that refreshes a page's cached output no longer suggests it also rebuilds the stylesheet: it clears the cached markup only, as it always has.
• Fix: Bricks pages built by AI agents arrive styled on sites that serve CSS from files. The page's stylesheet is now written as part of the change, where it previously stayed empty or out of date until someone opened the page in the builder and saved it again.
• Fix: Bricks typography set up by AI agents loads and applies on the front end, so headings and body text use the family you asked for, and turning a single font option off no longer switches Google Fonts off across the site.
• Fix: Bricks sections built by AI agents stay editable in the builder. Element identifiers are generated by the site and a repeated one is refused before anything is saved, so a section no longer contains elements that cannot be selected, edited or deleted.
• Fix: New Bricks element identifiers must contain exactly six characters before they reach a page or template, while identifiers already stored remain editable through the same tools. Component bodies replace non-six-character identifiers automatically and report each replacement.
• Fix: Top-level Bricks elements written as a whole page, inserted subtree, or new template — plus component instances placed beside a top-level sibling — now store the root parent marker in the integer form its Duplicate command requires.
• Fix: Bricks content changes are read back before an agent reports them as saved, and reported together with the number of elements the page now holds, so work that did not land comes back as a problem instead of a success.
• Fix: Bricks layout settings applied by AI agents take effect on every element type. Spacing and direction are offered per element in the form Bricks accepts there, so values set on headings, buttons, images and the rest apply instead of being dropped.
• Fix: Bricks warnings raised while an agent builds now match your site. Working layout settings on a site with theme styles, and the data Bricks records on the elements themselves — element metadata, global elements and the protected parts of its nested elements — are no longer reported as problems, so a warning is worth acting on.
• Fix: Bricks component properties can be added and changed on an existing component, without rebuilding it and re-pointing the pages that use it. Instances placed before a new property existed keep rendering with that property's default.
• Fix: Bricks component styling reaches every page that uses the component. Editing a component refreshes the stored stylesheet of each page it appears on, and the reply names any page that could not be updated together with the call that finishes it.
• Fix: Bricks components are safe from an AI agent's clean-up. A component you have placed on a page is no longer reported to the agent as an empty band to remove, and a component nothing uses is no longer protected from deletion by pages that exist only as revisions.
• Fix: Bricks global settings can all be changed by AI agents, including the ones your site adds, where anything outside a short built-in list used to be refused as unknown.
• Fix: Bricks variables deleted by an AI agent go to the Bricks trash on sites that keep one, so you can restore them from the Variable Manager the way you would after deleting one yourself.
• Fix: Bricks global classes and theme styles edited with a shorter list drop the entries you removed, so a gradient renders with the stops you kept and a theme style stops applying where you removed its condition.
• Fix: Bricks settings written by AI agents are checked against what your version of Bricks accepts. An interaction trigger or action your build cannot run is refused instead of stored and reported as done, and a setting that holds a list, such as a form's actions, is caught before a single value written there can stop the page rendering.
• Fix: Many Bricks refusals now say what is actually wrong instead of looking like the site had broken. Sending a value Bricks does not accept, naming a setting or post type it does not know, asking for something the site is not set up for, or writing to a page someone else has open in the builder each come back as the specific problem, where before they all read as “the server broke, try again” and an agent could repeat the same impossible call. Refusals whose cause is still ambiguous — chiefly those that report something as not found — are deliberately left as they were rather than labelled with a guess.
• Fix: Applying a Bricks global class to a post that does not exist now says the post was not found, where it previously reported that the post had no content and invited the agent to add some to a page that was not there. Patching an area whose stored content is not a Bricks element tree is likewise reported as damaged content, rather than as an empty area to fill — which would have written over whatever is still stored there.
• Fix: A Bricks page whose stored elements were already broken before an agent touched it is now reported as exactly that, naming what is wrong with the stored page, instead of the failure being attributed to the change the agent was making. Nothing is saved either way, but the agent is now pointed at repairing the page rather than at rewriting a request that was never the problem.
• Fix: Dynamic images and button links bound by AI agents in Divi now show their real values without replacing other image or button details, and custom fields inside loops resolve correctly.
• Fix: Divi Theme Builder templates created by AI agents are now registered through Divi's own storage, so they appear reliably in the builder and apply to their assigned pages. Assignment-only edits preserve unrelated layout bindings, and an invalid assignment is refused instead of applied.
• Fix: Divi interactions created by AI agents now use the trigger names Divi's front end recognizes, so their configured effects run. They are also saved with Divi's enabled field and shown as enabled in the builder.
• Fix: A Divi page with a row nested inside a column can be changed again. Divi's builder lets you nest a row that way, but the tools refused to write such a page back, so a page an agent could read came back as an invalid layout on save; nesting a row inside a column now works from the tools too.
• Fix: Divi fullwidth sections, along with groups, inner columns, and other container modules, can now be built and changed by AI agents, where a page holding one of these previously could not be edited at all. Specialty sections stay partly out of reach: their side-by-side columns cannot be created or replaced, so those writes are refused and the page has to be finished in the Divi builder.
• Fix: Creating an ACF field group now refuses a payload it does not recognize instead of storing it. A malformed or misspelled payload used to silently produce an empty field group with no title, no fields, and no location rules while still reporting success; it now comes back as an error naming the keys at fault.
• Fix: Creating or editing an ACF field group can no longer overwrite an unrelated post. A payload carrying a post id, the shape an agent gets from reading an existing group, used to make ACF rewrite that post instead of writing the field group; post ids in a field group payload are now ignored, and reading a field group's schema no longer includes one.
• Fix: A saved ACF field group is now read back and checked against what was asked for before the write is reported as done, so a group that did not fully persist comes back as an error instead of a false success.
• Fix: Creating an ACF field group that fails this new check is now rolled back, including any fields already written, without touching any other plugin's field groups.
• Fix: Editing an ACF field group that fails this new check is now reported rather than undone: the reply says what did not match and which fields the group holds afterwards, so you can decide what to do.
• Fix: Editing an ACF field group now requires the field group's key and refuses a post id. A number is not meaningless to ACF — it looks the post up by id — so a request that passed one could edit a field group it was never pointed at and then overwrite that group's key with the number, leaving the group unreachable by the key all of its fields still pointed at.
• Fix: The Mosaic tools work again on sites running the latest Mosaic. Mosaic changed where it keeps its classes, and on an updated site every Novamira Mosaic tool used to disappear without a word, including the setup check.
• Fix: Classes an AI agent applies to Mosaic elements now render with their styles, where they previously went into the element's plain CSS class list and lost their styling. A Mosaic class name sent to that plain list is now refused, and the design-system check flags any page that still carries one there.
• Fix: Renaming or deleting a Mosaic variable goes through Mosaic itself, so the variable's CSS name stays unique and a later save in the Mosaic editor no longer fails on a name left behind by an earlier change. Variable listings now also report the CSS variable name each one actually emits.
• Fix: The GenerateBlocks and GeneratePress build skills now send GenerateBlocks content, including GeneratePress Block Element bodies, through the Block Editor Queue and let GenerateBlocks produce each block's CSS itself. They previously told agents to hand-write block markup and CSS and to rebuild the page stylesheet by hand, which could leave blocks invalid in the editor or pages unstyled.
• Fix: Adding, editing or deleting a Fluent Forms field, or replacing a form's fields, no longer throws away the rest of what the form has stored. On a multi-step form the step configuration was silently deleted while the call still reported success, and the form kept rendering and submitting, so nothing pointed at the loss. Everything these tools do not change is now saved back exactly as it was.
• Fix: Tools whose inputs are all optional now accept omitted input through the WordPress abilities route and direct calls.
• Fix: When an AI agent gets a request wrong against the WordPress content tools or the Elementor page tools — an id that does not exist, a value the site will not accept, a page already in the trash, a featured image that is not an image — the reply now says the request was the problem, instead of reporting a server failure. Told the server had failed, an agent would keep retrying the same call unchanged rather than correcting it. Failures that really are the site's own are still reported as such.
• Minor fixes

View hidden content is available for registered users!

Novamira Pro - Memory and expertise for your AI v1.9.0 Nulled (Pro + Core)

• New: Blocksy specialization (requires the Blocksy theme 2.1.47 or newer, with Blocksy Companion and Companion Pro also supported): AI agents can set up the theme's global design, per-page layout, header and footer, and Companion features. A companion skill walks agents through the workflows.
• Tweak: Divi modules are now written through the dedicated Divi tools, so what an agent builds saves and renders as expected.
• Tweak: Kadence pages on a site where the block editor cannot run now come back with that as the reason, so the agent reports it instead of working around it.
• Tweak: Novamira Pro specializations can now be turned on or off with their related abilities and skills from the Novamira Features page (requires Novamira 1.12.0 or newer).
• Tweak: Uninstalling Novamira Pro now deactivates its license and cleans up after itself, handing any Context instructions over to the base Novamira plugin and removing its own settings, caches, scheduled checks, and admin notices.
• Fix: Elementor pages now open in the editor showing the content an agent has just written, instead of an older editor autosave. Writes aimed at a revision or autosave id are refused with a message naming the parent post to target.
• Fix: An Elementor write that does not persist now comes back as an error instead of a success reply, so the agent can act on it rather than carry on with a page that never changed.
• Fix: Elementor content and styles that arrive in the wrong shape are now refused with a validation error that names the offending element and the shape expected there, instead of being saved as a style that does nothing.
• Fix: Divi 5 pages composed one section at a time now open complete in the Divi builder, which previously showed only the first section even though the front end rendered them all. Pages built before this release are put back together on the next write.
• Fix: The Divi 5 tools now appear on sites that run Divi through a child theme whose parent theme folder was renamed.
• Fix: Meta Box post types can now be kept off the public site while staying editable in wp-admin, through the standard WordPress visibility settings.
• Fix: The Code Snippets tools work again on Code Snippets 3.10 (free and Pro), and the supported older versions keep working unchanged. AI agents are also told when a snippet is locked, when an edit was not applied, and which snippets a deleted Pro condition was gating.
• Minor fixes

Decryption key:

To view the content, you need to Sign In or Register.

Novamira Pro - Memory and expertise for your AI v1.8.3 Nulled (Pro + Core)

• New: Spectra Blocks specialization (requires the Spectra Blocks plugin 0.0.8 or newer; the Spectra Blocks Pro add-on is detected when present). AI agents can check the install state and version pair, browse the block catalogue with its activation state, read the plugin settings including reCAPTCHA configuration and Global Block Styles, and inspect Popup Builder popups down to their block markup. A companion skill covers the workflows and keeps the legacy Spectra (UAGB) plugin clearly separate.
• Tweak: The Kadence, GenerateBlocks, and GeneratePress build skills now teach agents about editor-assigned block settings (per-block style IDs and layout markers). With the upcoming Novamira release the Block Editor Queue fills them in automatically at finalization; on Novamira 1.11.3 and earlier the skills instruct agents to supply them by hand, so composed blocks no longer save unstyled or with a row's columns collapsed while the queue reports success.
• Fix: The Spectra build and integration skills now walk agents through the real Block Editor Queue pipeline for composing uagb/* content, where they previously pointed at per-block editing tools that do not exist, stopping every Spectra page build at the first step. They also cover Spectra's editor-assigned block_id, so composed blocks no longer save unstyled on Novamira 1.11.3 and earlier.
• Minor fixes

Decryption key:

To view the content, you need to Sign In or Register.

Novamira Pro - Memory and expertise for your AI v1.8.2 Nulled (Pro + Core)
No changelogs found!

Decryption key:

To view the content, you need to Sign In or Register.

Novamira Pro - Memory and expertise for your AI v1.8.1 Nulled (Pro + Core)
v1.8.1
2026/08/01

• New: Oxygen 6 specialization (requires Oxygen 6.0 or newer): AI agents can build pages and templates, style them through the global design system, bind live content and loops, and manage form submissions. A companion skill walks agents through the workflow.
• Tweak: Feedback reports on Novamira now have a place to go: the agent points you to https://novamira.ai/feedback, where you send the report yourself after reviewing it. The agent also offers to prepare one when the same problem keeps coming back after it has genuinely tried to fix it, instead of waiting for you to ask.
• Minor fixes

Decryption key:

To view the content, you need to Sign In or Register.

Novamira Pro - Memory and expertise for your AI v1.8.0 Nulled (Pro + Core)
v1.8.0 - 2026/07/29
* New: Weglot specialization (requires Weglot 5.0 or newer). AI agents can set up the connection, configure the original and translated languages, style the language switcher, and control which pages are translated and under which web addresses. A companion skill covers the boundaries.
* Fix: AI agents can now call the tools that take no required input, whatever MCP client they run in. Those tools previously came back with an input error unless the client sent an empty object explicitly.
* Fix: The Elementor editor keeps working inside the Novamira Visual workspace on Elementor 4.1 and newer. Novamira Visual now turns off Elementor's editor isolation policy so the workspace can drive the editor, and site owners who prefer Elementor's isolation can restore it with the novamira/visual/use_elementor_document_isolation filter.
* Fix: Bricks operations that fail now come back to AI agents as real errors instead of replies that look like success, so an agent no longer carries on after a failed color palette, global class, variable, theme style, or dynamic data operation.
* Fix: Bricks template display conditions written by AI agents are always stored in the array form Bricks reads, on every supported Bricks version: recoverable scalar values are normalized to arrays with a warning, while malformed condition containers or entries are rejected with a clear error before anything is saved (Bricks 2.4 skips malformed scalar values entirely).
* Fix: Bricks code elements written by AI agents now honor the BRICKS_LOCK_CODE_SIGNATURES constant on sites that lock code-signature generation, on every supported Bricks version: a write that needs new code signatures comes back with a clear error naming the affected code elements and how to unlock. On Bricks 2.4 this also keeps unsigned code, which would render empty, off the page.
* Fix: Breakdance pages built by AI agents now come out styled without reopening the builder, because Breakdance's CSS cache is rebuilt after every write to the page.
* Fix: Breakdance element design controls are now fully visible to AI agents, including the grouped ones (the Posts Loop list, the Div layout and background) that previously came back as a single "Error" placeholder, so those elements can be styled instead of left at their defaults.
* Fix: Breakdance elements that cannot render until they are configured, such as a form element with no form picked or a checkout element outside checkout, no longer block later edits to the same page. The element is still added and the agent is told the page will not display it until it is set up.
* Fix: Breakdance raw code elements, and raw page content written straight into WordPress on a Breakdance site, now need your explicit confirmation before an AI agent writes them.
* Fix: Beaver Builder pages written by AI agents no longer fail just because the page contains a column group nested inside a column, a normal Beaver Builder structure that reads always accepted. Column group nodes now allow a row or a column as parent.
* Fix: Mosaic Builder design-system variables can now have their value set by AI agents (color, length, font, etc.), not just their name, so recoloring or restyling no longer requires deleting and recreating variables or falling back to inline styles.
* Fix: Mosaic Builder utility classes can now be styled by AI agents per state (hover, focus, etc.) and breakpoint directly, instead of falling back to raw PHP or database edits that could put the site in a critical error.
* Fix: Mosaic Builder HTML attributes (data-*, aria-*, role, etc.) written by AI agents now carry the identifier Mosaic's own validation expects, so they survive a theme export and import instead of silently disappearing.
* Fix: Mosaic Builder component instances can now have their per-instance override edited or cleared directly by AI agents, instead of falling back to raw database writes that could corrupt the design system.

Decryption key:

To view the content, you need to Sign In or Register.

Novamira Pro - Memory and expertise for your AI v1.7.1 Nulled (Pro + Core)
v1.7.1 - 2026/07/22
* Tweak: Fluent Forms listing and form building are cleaner for AI agents: listing notifications returns compact rows by default (expandable on request), listing submissions hides trashed entries and searches the IP and browser, and building a form now warns when a setting is passed at the wrong level or a form is left with no fields.
* Fix: If the license server was unreachable, admin pages could slow to a crawl. This no longer happens.
* Fix: Fluent Forms forms and fields built by AI agents now render reliably on the page and in the editor. Newly created forms, all field types (including Address, Name, and choice fields), field settings like placeholder, max length and number min/max/step, and the published or unpublished status now take effect instead of silently producing empty output.
* Fix: A range of Fluent Forms robustness fixes: notifications added by AI agents now send on submission without overwriting hand-made ones, per-form permission checks are enforced, confirmation redirects and email headers reject unsafe values, list filters written as text work, concurrent settings edits no longer overwrite each other, and listing or exporting large submission sets no longer risks exhausting memory.
* Minor fixes

Decryption key:

To view the content, you need to Sign In or Register.

Novamira Pro - Memory and expertise for your AI v1.7.0 Nulled (Pro + Core)

• * New: Astra specialization (requires Astra 4.13.5+, free theme plus optional Astra Pro Addon). AI agents can edit the theme settings, color palettes, Header/Footer Builder, and per-page overrides, with more areas unlocked by Astra Pro; a companion skill covers the two tiers.
• * New: Avada theme specialization (requires Avada 7.15+). AI agents can edit a curated set of Fusion Theme Options and manage the Global Colors and Global Typography presets; a companion skill covers the boundaries.
• * New: Avada Fusion Slider support (requires Fusion Core 5.15.5 or newer, bundled with Avada). AI agents can list the site's sliders and edit their display settings and slides.
• * New: OceanWP specialization (requires OceanWP 4.1+, plus the optional Ocean Extra companion). AI agents can edit a curated set of Customizer settings and per-page layout, and with Ocean Extra mount Library templates and turn the Ocean Extra modules on or off; a companion skill covers the boundaries.
• * New: Spectra specialization (requires Spectra 2.19+, free plus Spectra Pro). AI agents can browse the block library, manage Popup Builder popups end to end, and turn individual blocks on or off; a companion skill covers the workflow.
• * New: Spectra One specialization (requires Spectra One 1.2.2+). AI agents can edit the Global Styles, navigation, and template parts, apply a style variation, and export the whole design as a reusable snapshot.
• * Tweak: WooCommerce abilities now register only when WooCommerce is active and at the minimum version, so sites without a store no longer list the WooCommerce category or its setup check.
• * Tweak: The Bricks page-building skill now covers query filters and pagination, and the setup check reports whether Bricks' query filters are enabled.
• * Tweak: Divi 5 content written by AI agents can no longer carry inline style attributes, since those cannot be edited from the Visual Builder controls. The agent gets a clear error pointing to the module's native settings, and inline styles go through only with an explicit opt-in.
• * Tweak: Bricks native dark mode can now be set up by AI agents (requires Bricks 2.2 or newer): palette colors accept a dark variant, and reading the palette reports whether the site is ready for Bricks' toggle-mode element.
• * Tweak: Meta Box value writes by AI agents can now be scoped to a field group, so a field that does not belong to the group is declined up front instead of being saved as a stray custom field.
• * Fix: Elementor pages that AI agents build now import cleanly on any Elementor site, so a page saved as a template moves between sites without errors.
• * Fix: GeneratePress Elements now let AI agents read and set their display, exclude, and user conditions, completing the path to building an Element end to end.
• * Fix: The Bricks page-building skill now teaches the correct query-loop grid pattern (the loop goes on the card, not the grid container), where Bricks previously rendered one grid per post.
• * Fix: Bricks trees written by AI agents now keep parent and children references consistent in every case, and a write repairs any inconsistent link already stored on the page and says so in a warning.
• * Fix: Meta Box field groups saved by AI agents no longer fail on Meta Box 2.6.0 and newer when a field carries datalist suggestions.
• * Fix: Meta Box field-group reads by AI agents now return the values for every field in the group, where they previously came back empty.
• * Fix: Meta Box post types and taxonomies created or edited by AI agents now get working permalinks right away, with no need to re-save the WordPress Permalinks screen.
• * Fix: Breakdance Pro licenses are now recognized by AI agents, so a Pro site works with the Pro feature set instead of the free one.
• * Fix: Breakdance elements now expose their Settings tab options to AI agents (custom CSS classes, display conditions, draft state), so those can be read and edited like any other element option.
• * Fix: Breakdance template abilities now accept the post id in the same form the element abilities use, so AI agents no longer hit input errors when moving between templates and elements.
• * Minor fixes

Novamira Pro - Memory and expertise for your AI v1.6.2 Nulled (Pro + Core)
v1.6.2 - 2026/07/07
* New: Bricksforge specialization (requires Bricksforge 3.1.8 or newer). AI agents can set up and manage the Bricksforge add-on for Bricks. They turn Bricksforge tools and custom elements on or off (Pro Forms, Popups, Maintenance Mode, Mega Menu, and more), and build Pro Forms through the Bricks page tools, with the field, choice, multi-step, condition, and layout details handled for them. They create and manage Bricksforge popups (opened on page load, click, or scroll, with a Bricks template as the content), and manage the Email Designer templates that restyle WordPress and WooCommerce emails: which emails each template replaces, its subject, whether it is active, and its theme. A companion skill teaches the form recipe and the Bricksforge specifics, and points agents to a live browser workspace for the visual parts (email layout, animations).
* Fix: Responsive style overrides (tablet and phone) that AI agents set on Divi 5 modules now take effect on the page. When an agent provides a breakpoint override, it is stored in the nested shape Divi 5 reads, whether the agent writes it as a nested object or as a single dotted path, so mobile and tablet spacing, sizing, and typography land as intended. This applies when editing a module, adding a module, and setting a page's content, and the agent is told the native nested shape so its next write matches what the builder stores.
* Minor fixes

Decryption key:

To view the content, you need to Sign In or Register.

Novamira Pro - Memory and expertise for your AI v1.6.1 Nulled (Pro + Core)
v1.6.1 - 2026/07/06
* New: Dynamic Shortcodes specialization (requires Dynamic Shortcodes 1.9.0 or newer). AI agents can build and troubleshoot Dynamic Shortcodes on your site: they can validate and compose shortcode strings, evaluate them against the live site to preview the real value, discover the fields available for each type, and create, edit, list, and delete reusable Power Shortcodes. A companion skill set teaches the syntax with real examples and shows how to place a Dynamic Shortcode inside each supported page builder (Elementor, Bricks, Breakdance, Oxygen, WPBakery, and the block and classic editors).
* New: AI agents can add interactions (motion) to Divi 5 modules. A trigger on a module (a click, hover, scroll, page load, mouse move, entering the viewport, form submit, or a responsive breakpoint change) runs an effect on it: toggle its visibility, scroll to it, or mirror the mouse for a parallax feel. Agents discover the available triggers and effects and set them per module, and the module stays editable in the Divi Visual Builder.
* Tweak: Divi 5 pages that AI agents build and style stay editable in the Visual Builder. Agents style through Divi's native module settings, global presets, colors, and variables in a clear order, so a page opens and edits normally in Divi rather than relying on custom CSS. When an agent writes page content, the page is kept marked as a Divi builder page, so its layout is preserved the first time the Visual Builder is opened.
* Tweak: When an AI agent edits an Elementor page, only that page's compiled CSS is refreshed. Other pages keep their cached styles and any open editor canvas stays intact, and the site skips a full site-wide CSS recompile on every edit.
* Tweak: AI agents building pages with GenerateBlocks now confirm the finished page renders with its styles before treating the work as done, since GenerateBlocks generates the page CSS from the blocks.
* Fix: Elementor v4 Global Classes that AI agents create or edit now show their base styles as explicitly defined on the desktop class controls in the editor, the same way classes made by hand do. Agents write the base style variant with the "desktop" breakpoint the Elementor editor expects, so the values read as set on the class and stay easy to maintain in the Elementor UI.
* Fix: Breakdance color variables, global classes, and global settings that AI agents create or edit are now saved in Breakdance's native format, so they load correctly in the builder and stay editable in Breakdance's own design-system UI. Tokens saved by an earlier version are still read correctly and rewritten cleanly on the next change.
* Minor fixes