What is LoomX?

Coding agents are extraordinarily capable at the logic of software – the data structures, the function calls, the component assembly, the state management. They have been trained on vast quantities of production code and can generate working implementations of almost anything with remarkable speed and correctness. What they were not trained to do is make aesthetic decisions that feel considered rather than competent.

A coding agent that assembles a card component will reach for whatever default makes the code work. It will choose a margin, a border radius, a type size – not because those choices carry meaning for this brand, but because something had to be chosen. The result works. It does not feel made.

LoomX exists to close this gap. It is the part of the expression infrastructure that speaks in the agent's own environment: the coding tool, the IDE, the workflow where the interface is being built. It does not interrupt. It advises. At the moment a decision is made, it ensures that decision is informed by the brand's encoded expression identity.

LoomX is not a code generator. It does not write components. It does not produce design mockups. It is not a Figma plugin, a component library, or a design system documentation tool. These are adjacent things that do adjacent work.

LoomX's territory is narrower and more specific: the moment a coding agent makes a design decision. That moment is where the expression engine intervenes – not with a constraint that prevents the agent from acting, but with guidance that shapes how the agent acts. The output is still the coding agent's. The judgment that shaped it belongs to the brand.

LoomX is the runtime layer of the expression infrastructure. It is what carries the expression identity – authored in LESS Studio and compiled into a brand's expression system – into the coding environment where interfaces actually get built.

Think of it as the delivery mechanism. LESS Studio is where brand expression is encoded. The expression system is what that encoding produces. LoomX is the agent-facing interface to that system – the part that speaks to Cursor, Claude Code, and Copilot in the language those tools understand, at the moment those tools are making decisions.

See also: what is LESS?

The most important design decision in LoomX is what it does not do. It does not surface a separate interface. It does not ask the developer to pause and consult a design system. It does not require a designer to be copied on a pull request. It is silent – present at the moment of decision without being in the way of the decision.

This is the right architecture for infrastructure. The test of any infrastructure layer is whether it does its work without requiring the people it serves to think about it. DNS is infrastructure because you do not think about IP addresses when you type a URL. LoomX is expression infrastructure because you do not think about brand guidelines when your coding agent is building a component. The judgment is already there.

LoomX takes its name from the loom – the device that weaves individual threads into a coherent whole. What the loom does for threads, LoomX does for design decisions: it ensures that individually made choices – each one seemingly small and discrete – produce a coherent, considered result.

The X is the axis where thread meets thread. Where the coding agent's logic meets the brand's taste. Where something made becomes something meant.