What is LoomX?
The support and answer sub-agent of the Designless Agent.
LoomX is the support and answer sub-agent of the Designless Agent. It answers questions about Designless and helps people get set up. Prism paints the canvas. Arbiter governs the brand. LoomX answers.
The problem it solves
Expression infrastructure is a new category. People arriving at it bring real questions: what the Designless Agent does, how it connects to the coding agents they already use, what a Brand Capsule is, which plan fits their team. Every unanswered question is a reason to stop.
Documentation helps, but it assumes you already know what to look for. Someone new to a category rarely does.
LoomX exists to close that gap. It answers questions about Designless in plain language and helps people get set up, so the path from a first question to a first build stays short.
What LoomX is not
LoomX is not the engine. The engine is the Designless Language Model, the design judgment the Designless Agent reasons with. LoomX does not build your surfaces, write components, or govern your brand. The Designless Agent orchestrates that work, with Prism painting the canvas and Arbiter governing the brand.
LoomX is not a design assistant, and it is not a sales pitch. Its territory is narrower and more specific: the questions people have about Designless, and the help they need to get started.
How it relates to the wider expression infrastructure
The Designless Language Model is the engine of the expression infrastructure: the design judgment behind every decision. The Designless Agent is the agent at the center of Designless. It works inside the AI tools you already use and carries a brand's expression identity, authored in LESS Studio, to where interfaces get built.
The Designless Agent orchestrates named sub-agents, each carrying one part of the work. Prism paints the canvas. Arbiter governs the brand. LoomX supports and answers: it is the part of the system that speaks to people, not to code.
See also: what is LESS?
Help that stays out of the way
The best support is the kind you notice only when you need it. LoomX does not interrupt your work or push you toward a product. It is there when you have a question, and quiet when you do not.
This is the test we apply to all infrastructure: it does its work without making the people it serves think about it. DNS is infrastructure because you do not think about IP addresses when you type a URL. LoomX is support built the same way. You ask, you get an answer, you get back to building.
Why the name
LoomX takes its name from the loom, the device that weaves individual threads into a coherent whole. Designless is woven from many threads: your brand, the agents you use, the canvas, your team. LoomX knows how those threads fit together, so an answer comes back whole.
The X is the axis where thread meets thread. Where a question meets its answer. Where someone curious becomes someone building.