WordPress 6.7 and later have been hinting at deeper automation, and Automattic just pulled the timeline forward. There is now a developer preview of a Claude Cowork plugin plus a set of “Skills” that rethink AI WordPress site building. I have watched plenty of AI site generators spit out spaghetti, so my expectations were low. This one targets block themes and local development in WordPress Studio, which points at maintainable architecture rather than a shiny demo.
Anyone who has spent a night on a broken checkout or a race condition in a legacy plugin arrives at this skeptical. I did. The pitch is not replacing the developer though, it is taking the boilerplate off your hands: Claude generates a full WordPress block theme out of a conversation, then deploys it straight into WordPress Studio.
What the Claude Cowork plugin actually does
It hangs off the /create-site command, which is not a single prompt but a sequence of “Skills”: reusable instruction sets that teach the model to behave like a WordPress architect. I have been chasing ways to simplify AI WordPress plugin development for years, and this is the next step in that direction. The workflow is split into three phases instead of one giant prompt: Site Specification, Site Design, and Block Theming.
The naive version of AI WordPress site building is asking an LLM for “a blue header and three columns.” What comes back is a messy style.css and a few broken HTML blocks, and refactoring that vibe code takes longer than writing it from scratch would have. The new Claude Skills aim at a valid theme.json and block patterns instead.
/* The Naive Way: Hardcoded CSS in a prompt result */
.header { background: blue; padding: 20px; }
.column-3 { width: 33%; float: left; }
/* The Skill-Based Way: Structured theme.json configuration */
{
"version": 3,
"settings": {
"color": {
"palette": [
{ "slug": "primary", "color": "#0000ff", "name": "Primary" }
]
},
"layout": {
"contentSize": "800px",
"wideSize": "1200px"
}
}
}Integrating with WordPress Studio
The usual gotcha with AI development is the deployment gap: you get the code and no obvious place to put it. The new Claude Cowork plugin closes that by talking to WordPress Studio, so the model can write files into your local environment. That fits the pro block theme development workflow I use, where everything is iterated locally before it goes near production.
I have had clients vibe code their own themes with generic GPTs and end up with a site that breaks every time a core update drops. These Skills are written to stay inside best practice: correct hooks and filters rather than edits hacked into the template files. The “WordPress Theme Creation” skill in particular is aimed at working block themes you can extend later.
Is it ship ready yet?
No. It is a developer preview and things break. Expect expired transients and race conditions when you generate several design options at once. The direction is clear enough though. AI WordPress site building is moving off chatbots and onto agents that understand the file system and the WordPress API.
To try it, clone the repo and follow the instructions in the Claude Cowork documentation. It is messy and experimental, and it is still the most structured attempt at automated site generation I have seen that does not throw code quality away.
If AI WordPress site building is eating your dev hours, I can take it off your hands. I have been working with WordPress since the 4.x days.
What to keep in mind on your next project
- Read the generated
theme.jsonyourself and check it for accessibility and performance bottlenecks. Do not trust the magic. - Pair AI generation with WordPress Studio or another local environment so a bad run never touches a live site.
- Use the specific Skills Automattic provides instead of a generic “create a site” prompt. The output is far more consistent.
