Shopify's new theme architecture, built for AI agents

Shopify has previewed a new theme architecture that moves page structure back into readable Liquid code, built deliberately for the age of coding agents, and for anyone building custom Shopify work it is the most interesting shift in years. The short version, templates become legible files a person or an agent can read top to bottom again, instead of the JSON output nobody was supposed to edit by hand. It is a developer preview, not a forced upgrade, and existing themes keep working, but the direction it signals is worth understanding now. This is what changed and what to do with it.

The reason it lands here, our whole thesis has been that you can build custom Shopify sections with Claude Code and skip the app tax, and Shopify just rebuilt the theme layer to make exactly that easier. When the platform redesigns its own foundation around coding agents, the agent-built store stops being a clever hack and starts being the intended path.

What actually changed

For a decade the trade was flexibility for legibility. Early Shopify themes were a template system you could read in one file, then Sections arrived in 2016 and gave merchants real control, and the cost was that pages turned into JSON configuration you had to cross-reference across schemas, settings, and blocks to understand. The new architecture takes the legibility back without giving up the flexibility, and it does it with a handful of concrete pieces.

Each of these is small on its own. Together they turn a theme from a thing you configure through knobs into a thing you read and compose in code, which is the difference between guessing how a page is assembled and simply seeing it.

Why “readable for agents” is the whole point

The deeper idea is simple, what makes a theme good for a developer makes it good for an agent too, they want the same things. An agent reads code the way a developer does, one file at a time, and it does its best work when that file explains itself, when the block says what it accepts and the error says what went wrong instead of failing somewhere three layers down. JSON configuration gave it none of that. An agent asked to add a second button next to the first had to hope the theme already exposed a block that could hold two. In plain markup it just adds the button and wraps the pair in a div, the way anyone would.

That is why the typed {% doc %} contracts matter more than they look. When a block declares its parameters, their types, and an example, a coding agent can discover what is valid, produce correct output, and get told precisely when it invents an API that does not exist. Shopify reported that merchants have already made tens of millions of AI theme edits this year, so the demand was already there, the architecture is catching the foundation up to it.

What it means for a store owner

You do not need to touch any of this today, and nothing about your current theme breaks. What changes is the calculus on custom work. Building a bespoke section, a landing page, a replacement for a display app, gets cheaper and faster when the theme itself is legible to the agent doing the building, and the typed contracts mean the schema mistakes agents used to make get caught early instead of in production. The partials primitive is the quiet winner for speed, it lets a cart or a count update its own small region instead of re-rendering a whole section, which is thousands of lines of reactivity code a store no longer carries.

The honest caveat, this is a preview aimed at developers, so the tooling and the custom-section workflows around it will keep moving for a while. The move to make is not to rebuild anything now. It is to know that the platform has committed to the agent-built store, and to plan custom work with that direction in mind rather than against it.

What to do next

If you have been waiting to build custom instead of renting another app, the ground just got firmer under that decision. Start with the highest-return small build, the sticky cart, the spec section, the app you pay most for monthly, and have it built the agent-legible way. When Tailwind lands in Liquid the styling side gets easier too, a shared vocabulary the agent already knows. The stores that treat their theme as readable, composable code, rather than a pile of configured apps, are the ones this architecture rewards.

FAQ

What is Shopify’s new theme architecture?

A previewed theme structure that puts page layout back into readable Liquid files instead of JSON, with composable blocks, typed documentation contracts, a partials update primitive, a strict parser, and Tailwind coming. It is built to be legible to developers and coding agents alike.

Does this break my current Shopify theme?

No. It is a developer preview, not a forced migration, and existing themes keep working. Liquid stays a stable, long-lived API. The new architecture is a foundation for new builds, not a demolition of what you already run.

Why does Shopify care about AI agents?

Because merchants are already editing themes with AI at scale, and agents build best from readable code with explicit contracts. A great developer experience and a great agent experience turn out to be the same thing, so the architecture optimizes for both at once.

What are typed {% doc %} contracts?

A way for a block or snippet to declare its parameters, their types, and an example. Developers get real-time feedback and errors, and coding agents get a way to discover valid inputs and get told when they invent an API that does not exist.

Should I rebuild my store for this now?

No, it is early and preview-stage. The takeaway is directional, Shopify has committed to the agent-built store. Plan custom work with that in mind, and when you do build bespoke sections, build them the legible, composable way this rewards.

Want custom work built the agent-legible way, section or landing page? Send me the store and I will scope the highest-return build first. Free look, no obligation, usually a reply within the hour.