Making AI-Assisted WordPress Development Safe: Single User and Multiple User Paths
Workbox uses a stack of Figma, Claude, GitHub and WP Engine to produce high quality WordPress themes and blocks. This stack can save folks a lot of time and money. However, in addition to understanding what very good WordPress code looks like, you need to consider the risk of security issues from your AI assistant.
If you’re a one-person builder or part of a very small group, you can follow a simple security path. For projects that have multiple users (or the client requires audit or review processes), your security path is only a little more complicated.
The 3 Rules
Workbox treats Claude like a fast, capable development contractor: it reads designs and writes code, but it never holds the keys to a live site. To keep things secure we apply these three rules to all projects:
1. Claude proposes, a person approves. Nothing hits a live site without a human’s approval.
2. Least privilege. Claude, and the accounts it works through, only have permission levels required for the task at hand. It never gets production credentials.
3. Secrets stay out of reach. Passwords, SSH keys and API tokens are never pasted into chats, stored in project files, or readable by Claude.
The two security paths below (simple, slightly less simple) differ only in tooling, not in the rules. Path 1 fits a solo developer or a team of two or three working directly with WP Engine. Path 2 adds GitHub for teams that need change history (or audits), parallel work and automated deployments.
Path 1: Figma + Claude + WP Engine (for individuals and very small teams)
Work happens on a local copy of the site and moves to WP Engine through Staging. Only the account owner can put anything on Production.
| Step | What happens | Security control |
|---|---|---|
| 1. Design | The designer works in Figma; Claude reads the design through the Figma connector | The connector has view-only access to the project files, no edit rights |
| 2. Build | Claude builds the theme and blocks on a local copy of the site (for example, Local by WP Engine) | Claude’s settings block reading .env, wp-config.php and SSH keys; every terminal command needs the developer’s approval |
| 3. Push to Staging | The developer pushes the local site to the WP Engine staging environment | The developer’s WP Engine account is limited to dev and staging; MFA is on; a backup point is created before each push |
| 4. Review | The lead, and the client if needed, check the staging site | Nothing is live yet; possible issues stay on staging |
| 5. Go live | The account owner copies staging to production in the WP Engine portal | Only the owner or lead has production access; a backup is created first |
Trade-off: no line-by-line change history. Rollback means restoring a WP Engine backup, which also rolls back content. That is acceptable for small sites with infrequent changes and one or two people working on it.
Path 2: Figma + Claude + GitHub + WP Engine (larger teams)
GitHub becomes the single route to every WP Engine environment. Deploy keys live only in GitHub, so neither Claude nor individual developers need them. This is the path Workbox follows.
| Step | What happens | Security control |
|---|---|---|
| 1. Design | The designer works in Figma; Claude reads the design through the Figma connector | View-only connector access, as in Path 1 |
| 2. Build | Claude writes code on a separate Git branch | Same Claude settings as Path 1: secret files blocked, commands approved; Claude never sees deploy keys |
| 3. Commit | Code is pushed to the GitHub repository | Secret scanning with push protection rejects commits that contain keys or passwords; MFA on every GitHub account |
| 4. Dev and Staging | Changes on the develop and staging branches deploy automatically to WP Engine dev and staging through GitHub Actions | The deploy key is stored as a GitHub secret and injected only at deploy time |
| 5. Approval gate | A change reaches main ; the production deploy pauses until the lead approves it in GitHub | Branch protection on main ; a GitHub “production” environment with a required reviewer; the production key is available only to main |
| 6. Production | The approved deploy ships to WP Engine production | A full audit trail of who changed what and who approved it; rollback = revert the commit and redeploy, without touching content |
For bigger teams, you should add pull requests with code review and require the lead’s review for changes to deployment files ( .github/workflows ). Teams that work on urgent fixes can skip pull requests and rely on the approval gate.
Controls that apply to both paths
One shared Claude configuration. The team uses the same settings file: secret files and SSH folders are blocked, terminal commands need approval, and “skip all permissions” modes are turned off.
Connectors with minimum scope. Figma, GitHub and other connectors get only the access a project needs. Access is reviewed regularly and revoked when a project ends.
Prompt injection is expected, not ignored. Claude reads client files and web pages that could hide malicious instructions. Because Claude holds no keys and has no production access, an injection has nowhere to go, and any risky actions still need a human click.
Browser automation in a separate profile. When Claude works in a browser, it acts with that browser’s logged-in sessions. We use a dedicated profile that never has admin sessions (like hosting or a CMS) with client sites.
Personal accounts with MFA everywhere. Figma, GitHub, WP Engine and Claude: no shared logins, MFA on, access removed when someone leaves.
Business plan for Claude. On Anthropic’s commercial plans, conversations are not used to train models by default. (Confirm the current terms before publishing.)
Which path is right for you?
| Path 1: no Git | Path 2: GitHub | |
|---|---|---|
| Team size | 1 to 3 people | 3+ people, or several working on one site |
| Change history | WP Engine backups only | Every change recorded, with author and approver |
| Rollback | Restore a backup (code and content together) | Revert one change, content untouched |
| Best for | Small brochure sites, infrequent updates | Regulated clients, frequent releases, audits |
In plain words: Claude works like a skilled contractor who works on your home, but never gets the keys. It can see designs and write code. Only a real person on a team can open the door to the live site, and every opening is logged. Even if someone tries to trick Claude, all the keys stay out of reach.