PHP2Shell PHP2Shell alert: check if your website needs the emergency PHP patch Check it →
Hug Prat
AI for businesses
Brass craftsman robots building a website out of wooden and stone blocks in a Barcelona workshop with a panot-tiled floor
Omitsis

WordPress · Omitsis · 2023 – 2026

AI agents that build WordPress for a Barcelona agency

A team of agents that knows the agency’s methodology and builds in WordPress block by block, with a visual review of every section and one PR per fix.

PRs merged in two days
47
years developing WordPress
+15
tiles for the visual review
1440 × 900
tokens consumed by the agent team
≈1.23 B

The context

Omitsis is a Barcelona digital agency, founded in 2008, that combines web design and development. I’ve worked with them as a senior WordPress developer since 2023, and they have a carefully refined methodology of their own for building websites out of blocks.

In 2026 we asked ourselves how far a team of AI agents could go working to those very same standards: the same blocks, the same design tokens and the same high bar for quality.

WordPress all the way

  • Custom Gutenberg blocks with ACF, block.json and PHP templates, following the agency’s library.
  • Themes with design tokens: colors, typography and spacing in a single place, so every block stays consistent with the rest.
  • WP-CLI and Docker environments so the agents can create, test and deploy without touching production.
  • Performance and accessibility as a requirement, not an extra.
  • The agency’s skills: its Claude Code plugins, ported as Hermes skills, so local models also work with the house methodology.

How the visual quality is achieved

  1. Reliable screenshots. A custom capture tool waits for the network, loads lazy images, removes banners and generates overlapping 1440 × 900 tiles.
  2. Section-by-section review with a vision model against the approved design, never with the full-page screenshot.
  3. Patch, deploy and capture again, with each section’s height measured.
  4. One PR per fix. In two days the agent team opened and merged 47.

Rules that worked

  • One orchestrator and at most two children, each with its own files.
  • Password-protected staging before showing anything to the client.
  • A hook that stops the orchestrator from polling its subagents in a loop.
  • Human review before every delivery.

What I learned

The problem was almost never the model but the system: badly taken screenshots, poorly wired vision or sessions that ran too long. Fixing the system did more than switching models. And with WordPress, a good block library is what lets the agents work fast without breaking anything.