brmbh

Your agents run WordPress.

Brmbh agentic suite is designed to run WordPress end to end without abstraction. It empowers agents to create, update, deploy, grow and much more!

$ npx skills add brmbh/wordpress
Claude Code Cursor GitHub Copilot Windsurf VS Code +30 agents
Ask your agent
install the brmbh WordPress skill

What it ships

Four pieces, one contract: theme, blocks, commands, skills. Your agent never leaves the stack — it scaffolds, builds, deploys and syncs without plugin pile or staging detour. Scroll, and they land in the tray.

Why Suite?

WordPress is free, open source and runs on your server. Agentic engineering now helps to reduce the number of plugins or complex staging environments. This Suite will give you and your Agents superpowers to build, manage and grow any WordPress projects.

New workflow: Have a chat with your agent.

Coding agents and LLMs are highly capable of achieving outstanding results. WordPress delivers the infrastructure on top of it. Brmbh aims to connect both worlds. It gives you the most capable and trusted full-stack website building framework which in addition you own forever.

Add the agent skills

One command and your agent knows the full brmbh workflow: scaffold, blocks, deploy, DB sync. Works on Claude Code, Cursor, Windsurf and 30+ others.

Your agent scaffolds

Hand your agent the project name. It clones the theme, installs dependencies, builds assets, activates it in WordPress and wires its own skills into the repo.

Build, block by block

Point at a Figma frame and the agent spins up the block factory, compiles the styles and registers the block. You review and ship.

my-theme — Terminal
Explorer
wp-themes
my-theme
style.css
functions.php
front-page.php
my-acf-blocks
loader.php
hero new
block.json
fields.php
template.php
_style.scss
AGENTS
create-block.md
deploy.md
package.json
theme.json
Run once in your terminal
$ npx skills add brmbh/wordpress
✓ fetched brmbh/wordpress
✓ installed skill — wordpress
  Claude Code · Cursor · Windsurf · +30 agents
▲ your agent now speaks brmbh
You ask your agent
create a new brmbh theme called my-theme
$ npx @brmbh/cli create my-theme
✓ cloned brmbh/wordpress
✓ npm install — 42 packages
✓ activated in WordPress
▲ theme ready — start building
You ask your agent
create a hero block from this Figma frame
<?php // hero — agent-built from your Figma frame
$title    = get_field('title');
$subtitle = get_field('subtitle'); ?>

<section class="hero py-6 bg-dark text-white">
  <h1 class="display-3"><?= esc_html($title) ?></h1>
  <p class="lead"><?= esc_html($subtitle) ?></p>
</section>
⎇ mainbrmbh zsh

Own the full stack.

Server and client

Vanilla PHP and a real JS build — no Blade, no black box. So one agent writes both halves: the PHP on the server and the JavaScript in the browser. Front to back, same conversation.

wp-cli as a Content MCP

WordPress ships wp-cli — a full, scriptable backend. brmbh wraps it, so your agent can run the CMS like an MCP: create content, manage plugins, query the database, move environments around.

The core stays up to date.

One command

npx brmbh update brings the CLI, the agent skills and the core of the theme (block factory, SCF guard, wp brmbh commands) to the newest version.

Your code stays yours

Templates, blocks and styles are never overwritten. When a release needs a change in your files, it comes as a migration that is shown first. If one can't run cleanly, nothing is written.

No more environment hassle.

Environments

Staging, production or any other name: each environment is a few lines in brmbh.json instead of a shell script per server. Hosts that should stay out of git go in brmbh.local.json. Any host with SSH and WP-CLI works, from your laptop or from CI.

Files

npx brmbh deploy production ships a commit, not a working tree, with the build output and without dev files. A dry run lists every file first, and after --apply the live site has to show that commit.

Database

npx brmbh db pull production copies the live database to your machine and rewrites every URL to your local site, serialized data included. Plugins are matched to the versions the server runs. Every import is backed up first, and content only flows down unless the environment allows a push.

Uploads

npx brmbh uploads pull production brings the media library down and only adds what is missing. A push shows its changes first and keeps every replaced or deleted file in a backup on the server. Folders like videos can be skipped.

Nobody else ships this.

brmbhUnderscoresUnderstrapSage
CSS frameworkBootstrap 5noneBootstrapTailwind
Bootstrap ↔ Gutenberg bridge—partial—
Self-registering SCF blocks———
Agent skills———
Figma → SCSS tokens———
Deploy + DB sync———
Templatingvanilla PHPvanilla PHPvanilla PHPBlade
Requires SCFyes (free)nonono

Get started yourself.

Themes folder

Scaffold

Ask your agent

“Create a hero block from this Figma frame.”

Ship