Commands for every step
pull, push, tokens, component, media, screenshot and critical. The site downloads and uploads with two commands.
The Nucleo CLI pulls your WordPress site into a folder, versions it with Git and pushes it back to the site. One command for each step.
The WordPress site lives in the database. Changes made in wp-admin do not go through repository review, and deployment becomes manual work.
Nucleo puts pages, tokens and components in files. The folder goes into Git, the CLI syncs it with the site, and the quality engine checks every push before publishing.
pull, push, tokens, component, media, screenshot and critical. The site downloads and uploads with two commands.
nucleo pull writes the site to a folder. Commits, branches and reviews are those of your repository.
tokens suggest reads the CSS of the design and proposes tokens for values used at least three times. push --use-tokens replaces the values with tokens.
component new creates a plugin with the required header. component deploy copies it to the local or development site, after the check.
nucleo mcp acts as a STDIO proxy to the site MCP server. The AI client starts the command and works with the permissions of the connected user.
screenshot saves pages at 390 and 1440 px. critical generates the critical CSS. Both use Playwright, an optional dependency.
You need Node 20 or later. Set the site, user and WordPress Application Password in nucleo.config.json, or in the NUCLEO_SITE, NUCLEO_USER and NUCLEO_APP_PASSWORD variables.
nucleo pull nucleo-site downloads pages, tokens and content into the folder. Commit with Git as you would for any project.
nucleo push nucleo-site --dry-run validates each document as the real push would. With no errors, run the push without --dry-run.
The free Nucleo plugin is on the WordPress repository. Configure the CLI with the site and an Application Password, then export the first pull.