Build, review and maintain WordPress block themes with Mistral Vibe.
From an HTML design to a reviewed FSE block theme, a safe update round and SEO content that ships after a second opinion.
Quick start · Workflow · Skills · Agents · Install
Out of the box, Mistral Vibe doesn't know what a block theme is. It writes classic PHP templates, hardcodes colours instead of theme.json presets, invents blocks and calls it done when the page looks nothing like the design. This toolbox fixes that:
- It knows the WordPress way.
theme.jsonv3 first, patterns and parts second, CSS last. - It checks its own work. Pattern validation in a real browser, PHPCS with the WordPress standard, and source-vs-site screenshots at desktop and mobile width.
- It asks before it ships. Update rounds need your approval; content goes to an independent reviewer first.
Made by a block-theme developer who uses it daily.
| Step | Agent / skill | You get |
|---|---|---|
| Design | wp-frontend-builder |
A locked design system and an HTML/CSS prototype, one section per future pattern |
| Build | /html-to-block-theme |
A production FSE block theme: theme.json v3, patterns and parts |
| Review | wp-reviewer, /code-review |
WordPress-standards review with a file:line and failure scenario per finding |
| Maintain | wp-maintainer, /wp-update-round |
Before/after screenshots, pixel diff, approval, deploy |
| Publish | seo-content-writer → seo-publish-reviewer |
Drafted content, reviewed before it goes live |
Works best with the Aviendha starter theme and the Aludra block library. See the full workflow and the architect-demo case study.
Point Vibe at the skills in ~/.vibe/config.toml:
skill_paths = ["~/code/windfinder/skills"]Sync the agents (re-run after git pull):
mkdir -p ~/.vibe/agents
rsync -a ~/code/windfinder/agents/ ~/.vibe/agents/Then, in any WordPress project:
vibe # /html-to-block-theme, /wp-update-round, /code-review, …
vibe --agent wp-frontend-builder # design to block theme
vibe --agent wp-reviewer -p "review the diff against main"Using Le Chat instead? Paste FRONTEND-DEV.md into Agents → New Agent → System Prompt. Per-project installs, approval allowlists and model tips: docs/install.md.
| Kind | Count | |
|---|---|---|
| Vibe skills | 66 | Slash commands that read your files, run git and linters, and report |
| Vibe agents | 9 | Role profiles for vibe --agent NAME, each with a spawnable subagent copy |
| Le Chat prompts | 2 | System prompts for agents without shell access, with recorded runs |
Skills by area: WordPress development (11) · Design & frontend (17) · Development workflow & quality (11) · DevOps & release (11) · SEO & content marketing (15).
Why they behave the way they do: design principles.
Workflow · Skills · Agents · Le Chat prompts · Install · Principles · Contributing · Sources · Credits · Changelog
MIT © Imagewize. Most skills are adapted from open-source collections and keep their own licenses (MIT, one Apache-2.0): see credits and NOTICE.md.
