WP Jarvis

Year — 2026

Scroll

Case study

From a blank page to a full, styled WordPress page you refine by chatting.

WP Jarvis is a WordPress plugin that builds complete pages from a conversation: describe the page, watch it build, ask for changes and publish, all inside wp-admin. I built the plugin, its backend, the site and the launch film.

Role
Founder, product design, design engineering
Year
2026
Team
Solo: design, code, backend and launch
Link
Visit website (opens in a new tab)

Live preview

Use the real WP Jarvis plugin

  1. 1Ask it to “Build a page for a coffee shop”.
  2. 2Try an edit: “Make the buttons blue” or “Add a testimonials section”.
  3. 3Press Publish and open the page.

WordPress admin is a desktop tool. On a phone, open it full screen or come back on a larger screen.

Challenge

AI add-ons for WordPress write a paragraph or one block. A real page still meant hours in a page builder.

WP Jarvis had to produce a whole, structured page, let people change one thing without breaking the rest, and publish it as a real WordPress page.

What I built

A builder that lives in wp-admin, plus the backend that does the AI work.

The plugin is a React app inside WordPress. It never stores AI provider keys: people sign in with a WP Jarvis account, and every AI request goes through my backend, which also serves the list of models.

Where the agent acts

  • Generates a complete, styled page from a description and streams it as it builds.
  • Applies follow-up messages as targeted edits instead of regenerating the page.
  • Connects navbar links to real pages and keeps new pages consistent with existing ones.

Where people decide

  • Decides what to ask for and when the page is right.
  • Sees every change in a live preview (desktop, tablet, mobile) with a revision history.
  • Publishes, public or private. Nothing goes live until they press Publish.

Process & decisions

The hard part wasn’t generating pages. It was proving an edit did exactly what was asked.

  1. 01

    A successful response is not a correct edit

    Independent audits kept finding edits that “worked” technically and still changed the wrong button or left half the request undone. Every release round after that had to prove three things per edit: the right target, every requested clause covered, and nothing unrelated changed.

  2. 02

    Explicit edits skip the model

    Requests like changing one button’s colour now take a deterministic path that resolves the exact element and changes only that property, with zero model calls. If the target is ambiguous, Jarvis asks which one instead of guessing.

  3. 03

    Test on real WordPress, not mocks

    A local WordPress role matrix checks what each kind of user can and cannot do: release 2.4.79 passed 12 of 19 checks, 2.4.80 passed all 19. By 2.4.83 the backend suite had 2,069 tests and the plugin 1,039 JavaScript tests.

  4. 04

    When a rule list never converges, fail closed

    Four review rounds on the section-editing verifier each found a new way around it. The fix was to stop adding rules and make it refuse anything it couldn’t verify.

Result

Released as plugin 2.4.83 and used on a production WordPress site, with its own site and launch film.

142
commits on the repo since May 2026
Next project Matching Unicorns A human-first remote hiring platform that matches growing US companies with Mexican professionals. Three connected portals, admin, client and talent, sit on one multi-tenant system. Hiring platform · 2026