Claude Code is built for code, not for WordPress, but the WordPress agency that runs Claude Code well today ships work at roughly 3x the velocity of one that does not. I run Seahawk Media, an agency that has shipped 12,000+ WordPress sites since 2018. Most of our team uses Claude Code daily for the work that used to be the boring 70 percent of WordPress development: theme scaffolding, plugin debugging, schema generation, content migration, REST API custom endpoints, and the long tail of "fix this PHP issue" tickets. This is the actual workflow.
If you are weighing whether Claude Code is real for WordPress work specifically, the operator answer is yes, with a different setup than you would use for Vue or Next.js, and only if you treat the WordPress idioms as first-class context.
Why most WordPress teams are using Claude Code wrong
Most teams open Claude Code in the WordPress root, ask Claude to write a custom block, and get something that compiles but does not match the team's coding standards, does not register the block correctly, and does not handle PHP-side server rendering. The output looks plausible to someone unfamiliar with WordPress; it fails in subtle ways for someone who knows the platform.
The fix is context. Claude does not know your WordPress conventions until you tell it. A short CLAUDE.md at the project root with your block standards, your PHP code style, your test conventions, and your deploy workflow turns Claude from a generic PHP-aware tool into a project-specific WordPress collaborator. The 30 minutes of CLAUDE.md authoring is the highest-leverage time investment I have made on the WordPress side of our work.
The CLAUDE.md I run on every WordPress project
A version of the CLAUDE.md template we use across Seahawk client engagements:
Project context: client name, primary domain, hosting (Kinsta, WP Engine, Cloudways), WordPress version, PHP version, theme, key plugins.
Coding standards: WordPress Coding Standards (WPCS) for PHP, Yoda conditions or not, prefix conventions for functions and globals, naming convention for custom post types and taxonomies.
Block standards: server-rendered blocks for content blocks, ACF Pro for editorial fields, Bricks Builder if used, Gutenberg if not. Block registration patterns the team has settled on.
Test conventions: PHPUnit for PHP, Jest for JS in blocks, Cypress for E2E if applicable. Where tests live in the project tree.
Deploy workflow: how to push to staging, how to push to production, what gets bumped where.
Forbidden patterns: things never to do (eval, query_posts, direct database queries without prepared statements, etc.).
That is two pages of plain English. Claude reads it once, and every subsequent code-generation session in the project is calibrated to your standards rather than generic WordPress defaults.
Specific WordPress workflows that compress massively
Custom block scaffolding
From idea to working server-rendered block: 90 minutes manually, 10 minutes with Claude Code if the CLAUDE.md is good. Claude generates the PHP registration, the JSX for the editor, the server-rendered template, the block.json, and the editor-side controls. I review the diff and fix one or two style issues. The boring scaffolding is gone.
Plugin conflict debugging
Claude reads the error log, searches the plugin directory for the offending hook, identifies the conflict, and proposes a fix. The detective work that takes 30 to 60 minutes manually takes 5 minutes inside Claude Code. We caught a Yoast / RankMath conflict on a recent migration in the time it took to brew a coffee.
Schema markup at scale
Claude generates per-page-type schema (Article, BlogPosting, Product, FAQPage, Organization, BreadcrumbList) following the project's naming conventions. Three to five page types, full schema coverage, in roughly 30 minutes. The schema would have been a half-day job for a junior engineer.
Content migration scripts
WP-CLI plus Claude is genuinely a different category of tool from WP-CLI alone. We migrated 8,000 posts off a custom CMS to WordPress on a recent engagement. Claude wrote the WP-CLI commands, the post-import cleanup script, the redirect map generation, and the URL deduplication. Three days of work in a half-day.
REST API custom endpoints
From product spec to working endpoint with permission callbacks, schema validation, and test coverage: under an hour. The boilerplate that makes WordPress REST API work disappears into Claude's output.
What Claude Code does not handle well in WordPress
Three areas where Claude struggles enough that I treat the human as the senior engineer:
Theme architecture decisions. When choosing between block themes, classic themes with FSE, Bricks, or full headless, the trade-offs are project-specific and Claude does not have your client's editorial context. This is human work.
Plugin selection. Claude can compare plugin features but does not know which plugins your team has had bad experiences with, which ones the client's host blocks, or which ones break on PHP 8.3. Pick plugins yourself; let Claude integrate them.
Custom Gutenberg block UX. Claude generates working blocks; it does not generate editor experiences that feel polished. The micro-interactions, the toolbar placement, the InspectorControls layout, the empty-state copy, those are design decisions, not code-generation outputs.
The toolchain I actually use
Claude Code as the primary surface, with the WordPress-specific MCP additions:
Filesystem MCP, built in. Reads the WordPress codebase, theme files, plugin directory.
Postgres or MySQL MCP, for content audits and migration work. Run SQL against the wp_posts and wp_postmeta tables directly.
Puppeteer MCP, for crawling the rendered site to verify changes shipped correctly.
WP-CLI via the shell, Claude invokes wp commands directly when needed.
Plus an existing CLAUDE.md per project. That is the entire stack.
Bottom line
Claude Code for WordPress is real, the workflow is different from generic Claude Code use, and the CLAUDE.md per project is the highest-leverage 30-minute investment a WordPress agency can make this year. We ship faster, fix faster, and surface plugin conflicts faster than we did before.
At Seahawk Media we run AI-assisted WordPress development on every client engagement now. The first conversation is free; the recommendation is honest about whether AI-assisted is the right fit for your specific WordPress project.