The road to agent-native WordPress.

Keep shipping ready-made workflows, expand the NibWP Library, and add more “do the job” skills instead of only exposing raw AI tools.

Work with WooCommerce as a shop rather than as posts: products and variations, orders, coupons and reports.

Add more Sure-related plugins/integrations and keep improving Sure ecosystem support.

Bring paper.design workflows into NibWP — let AI work with another design source before building in WordPress.

Build Builderius components and templates from a design, a screenshot or a description, checked against your design system before anything is saved.

Work with Oxygen sites on their own terms — templates, reusable parts and global styles — rather than through generic post editing.

Handle Yoast the way a specialist would: analyse what is weak, fix it in place, and keep titles, descriptions and schema consistent.

Reuse, adapt and share Etch components across your sites instead of rebuilding the same section every time. Bring a component in, make it yours, keep it in your own library.

Build Oxygen components and templates from a design, with global classes and reusable parts instead of duplicated structures.

Work with Rank Math on its own terms — scores, schema, redirects and sitemaps — instead of editing fields blindly.

Turn a design into GenerateBlocks sections that use your global styles and stay editable, rather than one-off markup.

Build pages in core Gutenberg blocks, validated before they save, for sites that use no page builder at all.

Build Breakdance sections and templates from a design or a description, checked against your design system before they are saved.

Work with WS Form the way it is actually built — forms and their fields, conditional logic, actions and submissions — so building or fixing a form does not mean clicking through every setting by hand.

Manage a multilingual site through Weglot — languages, translated pages and the wording Weglot has chosen — so a translation can be reviewed and corrected in place instead of hunting for it.

A permission system (more than a role) so agencies can give clients scoped access to parts of the NibWP dashboard — hide AI tools, workflows, integrations, and sensitive agency workflows. Built for white-label agency setups.

Connect an AI client by signing in and approving a readable list of permissions, instead of copying an application password.

Manage Voxel post types, fields, templates and listings through typed abilities.

Build Voxel-native templates and listings from a brief, screenshot or Figma frame.

A live window onto your own site while the assistant works — see each page open, each change land, and what was done. On every plan, free included.

Reads your site's own colours, fonts and spacing and decides how a page should look before a single block is placed. Free.

One screen that checks your setup end to end and says, in plain words, what is wrong and how to fix it.

Write a way of working once and share it with every site on your licence, or offer it to the community.

Connect a site from your terminal in one command, set up your editor, and work across every site at once.

Turn a pulled Figma design into a native page with whichever builder your site runs — Etch, Bricks, Elementor, Kadence, Oxygen, or core blocks. Tokens first, always a draft.

Connect a Figma account and pull frames into a local library, cached as an image plus the real design tokens. Pull one frame, a whole file, or an entire team. Read-only against Figma.

Turn a design, screenshot or URL into real Elementor widgets and templates that use your global styles and stay fully editable.

Turn a screenshot, an HTML file or a URL into real Kadence Blocks rows and sections. Everything it writes is checked before it saves, so what lands in the editor is editable rather than a wall of markup.

Read and write Builderius templates, components and global styles, so an assistant can work in the builder your site actually uses.

Manage Directorist listings, categories and fields, so a directory site can be maintained in bulk rather than one entry at a time.

Read and write Kadence settings, global styles and blocks, so changes match the theme rather than fight it.

Work with FluentCommunity spaces, members and profiles, so community management is part of the same conversation as the rest of the site.

Every tool call your assistant makes, recorded on your own site, with what it was asked to do and how it turned out. Yours to read at any time.

The rule that stops an assistant improvising: a skill declares the exact steps for a task, and the site refuses anything that skips them.

Turn a design into Bricks templates with global classes, dynamic data and query loops — checked against your design system before it saves.

Generate a complete ACSS design system from a screenshot or a brand — palette, type scale, spacing — and apply it so everything binds to tokens.

Turn HTML, a screenshot, a URL or a Figma frame into native EtchWP components with ACSS tokens, validated before anything is written to your site.

The first stable release: connect an assistant to WordPress through one signed endpoint, with the core abilities and the admin screens around them.

Read and write Slim SEO metadata, keeping titles, descriptions and social previews consistent across the site.

Read and write Tutor LMS courses, lessons, quizzes and enrolments, so course work does not mean clicking through every screen by hand.

Work with GeneratePress and its elements, hooks and global styles directly, instead of writing raw markup into a page.

Check how mail is actually leaving your site and read the delivery log, so a broken contact form is something you can see rather than guess at.

Read and write SEOPress titles, descriptions, social metadata and redirects, so SEO work happens where the rest of the work happens.

Audit and fix the SEO on a site, migrate between SEO plugins without losing metadata, and manage redirects — whichever SEO plugin you run.

Work with SureCart products, pricing and checkout, and build storefront sections that use real SureCart blocks rather than screenshots of them.

Write a way of working once and run it whenever you need it. Share a workflow with every site on your licence, or offer it to the community.

Work with Divi the way Divi works — theme builder templates, presets, global colours, library items and role settings.

Create and manage JetEngine custom post types, fields, relations and query loops, so dynamic content is set up properly rather than faked.