My AI WordPress workflow helps me finish the parts of a custom WordPress build I already know how to check. It does not replace the check.
I use Cursor inside a Sage (Roots) theme repository, ChatGPT and Claude for context/copy passes, n8n for form handling, GitHub Actions to build the theme zip, and Vite for asset compilation. Scaffolding, boilerplate, and first-pass Blade loops come back significantly quicker than they used to. Architecture, testing, and the final yes still sit with me.
Note on context: This post is a tool-by-tool breakdown of strengths, costs, and human steps—not a repeat of my previous workflow essay ("AI for WordPress Development: My Cursor, ChatGPT, n8n & MCP Workflow"). That post covers the loop; this one maps where each tool shines and where it costs.
What “Fast” Actually Means in Custom Dev
"Fast" is easy to sell. In practice, it means something much narrower: less time spent on work that does not require a human rewrite.
I won't claim a 10x multiplier or a shorter calendar on every project, nor that a model "wrote the site." The core benefit is clear: repeatable technical work shrinks, while accountability remains firmly human.
1. Repeatable Work Lessens
Renaming an ACF page field, wiring a new Vite entry point, drafting a standard Blade loop, or filling out a GitHub Actions workflow—these are predictable patterns. AI models excel here because I can immediately verify the output against a pattern I already know.
That accounts for most of the actual speed gain. It is real, but it is also easy to overstate.
2. Judgment Remains with the Developer
Deciding which plugin stays, whether a client editor can safely modify a layout field, catching contrast accessibility failures, or evaluating if a webhook belongs in the stack—that is judgment. Models guess based on statistical likelihood. I still own the call.
If I cannot explain every line at handoff, it does not ship. It's the same quality bar as a traditional build, just with less friction on the boilerplate.
The AI WordPress Tool Matrix
This isn't a tier list or a ranking. Each tool occupies a specific role in the build, incurs a specific trade-off, and demands a non-negotiable human review step.
| Tool | Role / Best For | Weak At / Trade-Off | Non-Negotiable Human Step |
|---|---|---|---|
| Cursor | In-repo scaffolding, Blade templates, PHP helpers, refactoring. | Hallucinating WP core APIs or outdated package syntaxes. | Reading diffs line-by-line; testing logic in a real WP environment. |
| ChatGPT / Claude | Second-pass copy editing, off-repo structural brainstorming, regex. | Lacks direct codebase context; over-uses generic "agency voice." | Validating accuracy, editing tone, stripping unnecessary fluff. |
| n8n | External form handoff automation and webhook integration. | Silent failures if third-party endpoints rate-limit or change schemas. | Setting up fallback mail handlers (wp_mail) and monitoring logs. |
| Vite | Asset bundling, hot module replacement (HMR), asset compilation. | Requires strict entry point declarations in custom theme setups. | Auditing bundle sizes and verifying compiled output in browser. |
| GitHub Actions | Automated CI/CD, running Composer, building production zip releases. | Hidden pipeline costs or broken builds due to strict PHP/node mismatches. | Maintaining deployment secrets and controlling production triggers. |
| MCP (Model Context Protocol) | Giving agents scoped doors to external tools (database, terminal, APIs). | Risk of exposing elevated write access or leaking sensitive credentials. | Keeping scopes hyper-narrow; manually approving write operations. |
How I Choose Tools per Task
I start from the job, not the model:
- In-repo file edits (Sage/Roots theme): I open Cursor.
- Drafting content or working outside the codebase: I use ChatGPT or Claude.
- Handling form submissions and external payload routes: That is n8n.
- Asset compilation & production releases: That belongs to Vite and GitHub Actions.
- Connecting agents to real-time tools: MCP opens only when an agent needs a narrow doorway to an external utility.
A development shop doesn't need all of these active at once. You pick the right tool for the current step, followed immediately by human review.
How a Change Moves from Brief to Release
From a client brief to project handoff, the pipeline is short and predictable. AI models sit exclusively in the middle step—never at the boundaries.
[ Brief ] ──► [ Cursor / AI Draft ] ──► [ Human Review & Diffs ] ──► [ Vite & CI/CD ] ──► [ Production Handoff ]
- Brief: A shop note, agency ticket, or custom brief. I write the technical constraints. A model did not take the job.
- Cursor: Local scaffolding inside the Sage repository—Blade components, PHP helpers, Tailwind/CSS. ChatGPT/Claude assist with off-repo structural ideas. MCP is enabled only when an agent requires a specific, scoped tool.
- Review: I inspect the Git diff. I execute the code on a real local page. Hallucinated APIs, unnecessary plugins, and fluff copy get eliminated here.
-
Vite & CI: Running
npm run buildlocally, followed by GitHub Actions on push tomain. The pipeline runs Composer, compiles assets, packages the production release zip, and tagstheme-latest. PHP 8.3 serves as the runtime; WP-CLI remains the administrative interface. -
Handoff: Configuring
wp-adminfields for client editing, providing clean technical notes, and transferring the Git repository. If I cannot explain a piece of code, it does not get handed off.
Where n8n Sits:
n8nis isolated from the theme's core code path. When a user submits a contact form, WordPressPOSTs JSON to ann8nwebhook. If that webhook fails, a nativewp_mailfallback triggers. Automation handles the payload after submission—it does not author the theme.
What I Still Do by Hand
The list of manual tasks remains longer than the automated pipeline by design:
- Architecture & Strategy: Deciding overall system structure—and what not to build.
- Security & Access: Managing permissions, nonces, and governing what MCP servers can access.
- Diff Auditing: Reviewing every single line in a pull request rather than trusting the commit summary.
- Field & Cross-Device Testing: Validating themes on live page builds across desktop and mobile viewports.
- Copy Tone: Ensuring the copy speaks clearly to clients and agencies without sounding like LLM jargon.
- Accessibility (a11y): Verifying color contrast pairs, ARIA labels, semantic HTML hierarchy, and keyboard focus states.
- Production Deployment Approval: Giving the final green light for production releases.
Standard VS Code is still part of my setup for times when I want to edit files without AI assistance. Keeping the review muscle sharp is critical.
FAQ
Does AI write the PHP I ship?
It drafts it; I review and ship it. Tools like Cursor, Claude, and ChatGPT help produce boilerplate PHP and initial template logic. However, I read, test, and take ownership of every line that hits production—including Vite pipelines, PHP 8.3 code, and GitHub Actions scripts.
Why is there no "overall winner" in this comparison?
Because they perform completely different functions. Cursor acts as the local code editor, ChatGPT/Claude handle off-repo reasoning, n8n routes form payloads, and GitHub Actions automates deployment zips. Ranking them against each other would be comparing apples to build servers.
Will an AI workflow like this replace a developer?
No. The cost of generating repeatable code dropped, but the cost of technical judgment did not change. Hiring an experienced developer means paying for code architecture, security verification, thorough testing, and long-term maintainability—not the speed of the prompt log.
What about data privacy and vendor lock-in?
Chat interfaces and MCP tools process whatever you pass to them. I mitigate risk by keeping write scopes minimal and removing secrets/keys from prompts. While Cursor, n8n, and GitHub represent distinct third-party dependencies, all code and review processes live inside standard Git repositories that can be migrated at any time.
How does this differ from a full workflow guide?
A workflow guide demonstrates how the ecosystem fits together during an active WordPress build. This post provides an explicit tool-by-tool comparison detailing strengths, trade-offs, and where human intervention remains mandatory.
Originally published on matthummel.com.
Top comments (0)