Hello Delta

Most tools are built for the model that exists when the work starts. We built Delta for the model that will exist in a year.

That sounds like a small distinction, but it is not. It actually decided almost everything about how we shaped the Delta theme.

The bet

Models are getting better at design work, and on a very fast pace. Within a year we expect them to hold more context, remember more of a project, stay consistent across longer sessions, and keep a firmer grip on what you are orchestrating.

If we built around today’s limitations, every workaround for short context and weak memory would become something to unwind later. So we built for the capable model instead, and accepted that some of it would feel early.

We are making that bet deliberately, and building as though it is already true.

Four decisions

No editor interface. We do not ship a canvas, a widget panel or a drag surface. You describe what you want and the agent builds it. You can bring a site into existence in conversation. The admin screens we do provide are for looking at what the agent has done, not for doing it yourself.

Plain materials. The agent writes HTML, CSS and JavaScript. Nothing sits between that markup and the browser at render time, which is good for page speed, and it means the agent needs no new vocabulary. Every page builder invents an object model that a model has to learn before it can be useful. HTML and CSS are already known. We turned the whole theme into one surface the agent can operate.

A stable floor under the design. We ship a seed set of primitive tokens and semantic colours. They are not a house style. They are a floor you can scaffold any design system on, so that themes and demos keep a baseline of structural integrity while you customise freely on top. When the agent composes a layout it works from those tokens and adds new ones where your design needs them. There is more in Primitive tokens.

Integrations rather than reinvention. We do not ship our own contact forms, custom post types, custom fields or SEO. Those spaces already have plugins that do the job well. We expose tools for them instead, and you ask the agent to wire one in. We would rather do one thing than a shallow version of six.

What this release is

An initial version, published so we can get input from people building real client sites.

Delta is alpha. It builds and runs this website, including the documentation you are reading, which is the most honest test we can give it. That does not make it finished.

Some specifics, so you know what you are getting:

• The admin interface is there for a visual overview of your theme setup and for debugging. We did not tailor it for humans, and it is not trying to be something it is not.
• The AI chat editor, which works directly on a Delta page, is experimental and needs your own API access.
• Most of our current effort is going into internal agent routing and a context architecture that is modular and extensible, because that is what decides whether the agent does the right thing without being told twice.

What comes next

Two directions matter more to us than any feature we could list, and neither exists yet.

The first is client workflow. We want the agent to become the point of contact for your clients, so they ask it to log feedback or send you a message instead of emailing screenshots. We are working towards scoped connectors, where you share a connector with a client and their agent operates the site within narrow limits. No layout edits, but uploads, input and feedback.

The second is static output. WordPress remains a good content management system. It is less obviously the right thing to serve to visitors. Our output is already plain files, so the distance to a static site is shorter from here than it would be from a builder’s internal format.

Who we are

John and Krishna (us) have worked together since 2017. Under Analog WP we built Style Kits for Elementor and several other plugins. A few months ago, we built Schema, a WordPress MCP plugin that exposes the Automatic.CSS design system to AI clients.

John has spent fifteen years in WordPress, the last ten of them on design system scalability and design operations: standardisation, consistency, and the systems that stop both from drifting as a site grows.

Krishna has been building WordPress plugins for a decade, and has moved his engineering work fully onto agent-driven workflows.

That is why we made the tokens a fixed floor rather than a suggestion.

The problem has not changed, only who does the building.

Agent-first design needs the baseline a design team always needed, expressed as a semantic layer the builder can work inside.

Where to start

What Delta is covers the model in more detail, and Connect an agent covers setup with Claude, ChatGPT, Cursor, Claude Code and other MCP clients.

If you build client sites and you try it, the most useful thing you can send us is where it got in your way.

Meet Delta