WordPress 6.7 and beyond have been hinting at deeper automation, but Automattic just accelerated the timeline. They’ve released a developer preview of a Claude Cowork plugin and a set of “Skills” that rethink AI WordPress site building from the ground up. I’ve seen plenty of AI “site generators” that just vomit out spaghetti code. However, this implementation targets block themes and local development in WordPress Studio, which suggests a shift toward actual, maintainable architecture rather than just a shiny demo.
If you’re a developer who has spent nights debugging a broken checkout or a race condition in a legacy plugin, you’re naturally skeptical. I was too. But the approach here isn’t about replacing the dev; it’s about automating the boilerplate. Specifically, it uses Claude to generate a full WordPress block theme based on a conversation, then deploys it directly to WordPress Studio.
Why the Claude Cowork Plugin Changes the Game
The core of this update is the /create-site command. This isn’t just a simple prompt; it’s a sequence of “Skills”—reusable instruction sets that teach the AI how to behave like a WordPress architect. For years, we’ve tried to simplify AI WordPress plugin development, and this feels like the next logical step. Instead of one giant prompt, the system breaks the workflow into three distinct phases: Site Specification, Site Design, and Block Theming.
The “naive” approach to AI WordPress site building usually involves asking an LLM for “a blue header and three columns.” You’ll likely get a messy style.css file and some broken HTML blocks. Consequently, you spend more time refactoring the “vibe code” than it would have taken to write it from scratch. The new Claude Skills, however, focus on generating a valid theme.json and block patterns.
/* 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
One of the “gotchas” with AI development is the deployment gap. You get the code, but where do you put it? The new Claude Cowork plugin bridges this by connecting to WordPress Studio. It allows the AI to actually write files to your local environment. Furthermore, this workflow aligns with a pro block theme development workflow, where you iterate locally before pushing to production.
I’ve had clients try to “vibe code” their own themes using generic GPTs, only to end up with a site that breaks every time a core update drops. These new Skills are designed to stick to best practices, meaning they use the correct hooks and filters rather than hacking the template files. Specifically, the “WordPress Theme Creation” skill focuses on generating working block themes that are extensible.
The Senior Dev’s Verdict: Is it Ship-Ready?
Currently, this is a developer preview. Things will break. You’ll hit transients that expire or race conditions when generating multiple design options simultaneously. However, the trajectory is clear. AI WordPress site building is moving away from “chatbots” and toward “agents” that understand the file system and the WordPress API.
If you want to experiment, you’ll need to clone the repo and follow the instructions in the Claude Cowork documentation. It’s messy, it’s experimental, but it’s the most structured approach I’ve seen yet for automating site generation without sacrificing code quality.
Look, if this AI WordPress site building stuff is eating up your dev hours, let me handle it. I’ve been wrestling with WordPress since the 4.x days.
Key Takeaways for Your Next Project
- Don’t trust the magic: Always review the generated
theme.jsonfor accessibility and performance bottlenecks. - Use local environments: Always pair AI generation with WordPress Studio to avoid breaking live sites.
- Modular prompts: Use the specific Skills provided by Automattic rather than generic “create a site” prompts for better consistency.
