A storefront theme rewrite at Shopify is turning AI adoption into a code-architecture constraint.

The Register's account describes a new, still-unnamed base theme that moves the commerce platform away from Horizon's JSON-heavy structure and back toward mostly HTML mixed with Liquid templates.

The operating problem is that storefront customization now has two readers: merchants and AI agents.

The Register account states that Shopify Sidekick is used by 20% of merchants to edit themes, and that those users have made 25 million edits this year.

Cleaner Theme Files Replace Dense Configuration

The new base theme is being shown in developer forums as a likely successor to Horizon, the current theme for customized store pages.

Its templates directory is designed to expose plain-text files that can be understood by reading the page structure, rather than chasing long serialized configuration blocks.

Ben Sehl, product director for storefronts, framed HTML as a better surface for models because leading systems already understand it and because it is expressive, local and token-efficient.

That design choice turns page structure back into something a developer, merchant or agent can inspect directly.

JSON gave merchants more controls inside the Online Store Editor.

The cost was a developer surface that became harder to reason about from one file, especially when an assistant needed to understand what a page contained before changing it.

Agent Editing Changes The Design Target

The redesign treats readability as infrastructure for agent-assisted commerce rather than as a cosmetic code preference.

The architecture is being organized around easy-to-read source, explicit contracts and feedback that an automated editor can act on without breaking a theme.

Liquid gains a new syntax and parser, while composable typed blocks sit beside ordinary HTML.

Expanded documentation tags carry examples and contract instructions, and a composable block tag passes values, configurations and overrides into nested page components.

Standard actions cover site events such as cart updates.

Sehl wrote that this primitive can remove thousands of lines of reactivity code from Horizon, shifting more behavior into a smaller set of declared operations.

Readable Code Becomes A Deployment Guardrail

Policy controls sit alongside the cleaner files.

The generated-theme rules cover contracts, structure, validation, complexity, nesting and file-size limits, turning machine-written storefront changes into something that can be checked against declared boundaries.

The broader lesson is that models often handle semantically rich, human-readable formats better than dense symbolic configuration for non-coding tasks.

A cited developer example found SQL easier for models than domain-specific tool languages, while Anthropic's prompting guidance favors XML for semantically rich structure.

For merchants, the result could be a storefront system that is easier to inspect before and after an AI assistant changes it.

The material evidence gap is commercial timing and validation: the available record stops short of a release date for the new theme or independent performance data for Sidekick-generated edits.