AI-first framework for WordPress & WooCommerce
Faster than ever.
Airy is a framework for WordPress and WooCommerce.
An agent composes pages from a library of measured patterns, a validator refuses anything that breaks the performance, layout or fidelity budget, and from then on you edit the site in WordPress – inside the same contract, which the editor cannot step outside of.
Built in the open, phase by phase. Phase 3 of 5.
Why Airy exists
WordPress won the ecosystem – plugins, hosting, editors, and the people who already know it. Page builders lost the performance. A layout that needs no JavaScript ships hundreds of kilobytes of it, every plugin adds a little more, and by the second year the site nobody has touched is slower than the day it launched.
Letting an AI write arbitrary code into that stack does not fix the problem. It industrialises it. Airy takes the opposite route. The agent does not write free-form code – it composes within a contract. Every pattern declares what it costs, and the gate refuses to build a page that goes over budget. Speed stops being a launch-day achievement and becomes a condition of building at all.
What this means if you own the site
It stays fast
Performance is not a launch-day score that decays with the next plugin. A change that breaks the budget does not compile – so the site you have in a year is the site you launched.
Changes without a developer
You edit the site in WordPress, in the editor you already know. Nothing you can do there breaks the layout, the colours or the speed – the editor is only offered what the contract allows.
It is still WordPress
Standard blocks, the standard editor, standard hosting – the result is an ordinary block theme on purpose. No page builder licence, no proprietary format, nothing to migrate away from later, and nothing that stops working if you stop using Airy.
Publish as static files
Edit in WordPress, ship plain HTML and CSS. No PHP on the public server, nothing to patch and nothing to break into – and the exported page is pixel-identical to the one you approved.
Moving an existing site
A migrated site is compared with the original pixel by pixel at five screen widths. Acceptance is a number, not an opinion – and the report shows the before and after side by side.
Measured, not promised
100
Lighthouse Performance, straight out of the pipeline – measured on the built site, not on a demo.
0 B
JavaScript on this page. Interactivity exists only as declared islands with a byte budget, and this page needs none.
81 kB
Everything this page loads, in four requests: markup, styles and two font files. Two thirds of that weight is the typeface.
0.000%
Pixel difference between the static files we publish and what WordPress renders, across five screen widths – measured three ways: through a browser, over plain HTTP, and from inside WordPress.
23
Patterns in the library the agent composes from – each with a declared cost, a responsive strategy and accessibility notes.
Measured on this page and on the benchmark runs in the repository, with the same tool on both sides.
How it works
01
Snapshot – the design enters as a URL, an HTML file, an image or a Figma file, and becomes a measurable input: geometry, tokens, animations, fonts.
02
Compose – the agent builds the pages from the pattern library, and the contract file fixes what the editor may later offer: the tokens, the blocks, the budgets.
03
Validate – one gate checks schemas, budgets, responsive behaviour, token consistency and visual fidelity. A failure stops the build.
04
Edit and publish – the compiler emits a WordPress child theme, and from there the site is yours: you edit it in the block editor, and one button freezes it into static files. Nothing reaches production without a person pressing it.
The contract is the file
This is the part of this site that lives in the repository – and it is not the text you are reading.
design:
tokens:
color: { ground: "#FFFFFF", ink: "#10141A", link: "#1569C0" }
editing:
lockTokens: true
allowedBlocks: [core/paragraph, core/heading,
core/columns, airy/logo]
colorSchemes:
dark: { ground: "#0B0E12", ink: "#F4F6F8" }
The words live in WordPress, where anyone can edit them. The file holds what they cannot break: the palette, the blocks the editor is allowed to offer, and the byte budgets that fail the build. It reviews like code and diffs like code, because it is code.
Where the project is
The spec, the theme core and the command line are done; site migration is running now; the WooCommerce layer and an AI panel inside wp-admin – so that a marketer can change the site without touching code – come next. Airy is developed in the open, one phase at a time.
If you own a site or a shop and this reads like your problem, write. Early projects shape what gets built next.