AI-first framework · in development

AI composes the site. A contract keeps it fast.

Airy is a framework for WordPress and WooCommerce. An agent composes pages from a library of measured patterns, a validator refuses to build anything that breaks the performance, layout or fidelity budget, and you approve the result before it ships.

Built in the open, phase by phase. Phase 3 of 5.

How it works

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 describe the change in plain language and the agent composes it inside the contract. Nothing it can produce breaks your layout, your colours or your speed.
It is still WordPress: Standard blocks, the standard editor, standard hosting. No page builder licence, no proprietary format, nothing to migrate away from later.
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.5%: Pixel difference between a migrated clone and its original, across five screen widths.
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 describes the whole site in one declarative file, choosing from the pattern library instead of writing markup.
03: Validate — one gate checks schemas, budgets, responsive behaviour, token consistency and visual fidelity. A failure stops the build.
04: Build and approve — the compiler emits a WordPress child theme; you look at the preview and decide. Nothing reaches production without that.

The page is the file

This is the source of the section you just read, from this site’s own spec.

- pattern: definition-list
  props:
    anchor: how
    heading: How it works
    style: data
    items:
      - term: "01"
        description: Snapshot — the design enters as a URL, an
          HTML file, an image or a Figma file…

The whole site is one declarative file. It reviews like code, diffs like code, and cannot reference a colour that is not in the design tokens.

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.