Skip to content

Product

Product

How we run your design system with you, and the four jobs it needs.

Product overview

OperationsRun the system as an organisation: owners, a review queue, rituals and exceptions that end.
SeeKnow what your system really is: a health check and an audit with evidence.
ShapeTyped tokens, one contract per component, and components written and checked. Your look stays.
GovernOwners, rules, exceptions and a review queue, kept as records in your repository.
RunAgents do the routine work under rules your people set.
Loom BaseOur own design system, built and checked by our own engine.
Agents and MCPGive agents your real system, check their work and record what is missing.
SecurityLeast-privilege access, your model and keys, labelled AI output.

Roles

Roles

How each role in your organisation uses Loom, and what it gets back.

Design-system ownersOne queue, decisions on record, and a system that reports on itself.
CTOs and engineering managersGovern what your AI tools write, in your own repository and CI.
Product managersRequests with service levels, plain release notes and what you can reuse.
CEOs and stakeholdersThree measures from the first month, and one page a month.
DesignersAsk once, see your ask move, and keep Figma and code in step.
DevelopersChecks that name the fix, and migrations written for you.
Accessibility ownersThe only person who rules on accessibility, with the evidence in front of you.
Content and UX writingVoice and terminology as rules Loom checks in your copy.
Ops leadsThe rhythm of the system: queue, rituals, comms and cover.
Organisations with many brandsOne system across brands, regions and products, each layer owned.

Proof

Proof

Try Loom in your browser. Each demo says what is real.

Read your own stylesheetPaste your CSS or tokens and see the decisions nobody made.
One quarter of a design systemThirteen weeks of a sample system, with an operating model and with tools only. Sample data.
The agent's draft, checkedA scripted agent's drafts with the real findings of Loom's check.
What arrives in your repositoryThe pull request Loom's own commands write, on a sample repository.
Score usEvery check behind our own scores, and the command to reproduce each.
Before and afterThe same button before and after tokens: the look stays.
Agent replayWatch a recorded agent build with Loom's MCP server.
Health checkA self-assessment. About three minutes; your answers stay in your browser.
ArticlesArguments about design systems, governance and agents.

About

About

Who we are and how we work.

AboutWhy Loom exists, and who is behind it.
TrustHow we keep our claims honest and handle your data.
How we workHow an engagement works, from a health check to ongoing care.
DESIGN.mdA whole design system in one Markdown file, exported by Loom. Read two examples.
PartnersDesign agencies, and a prospective partner in Japan.
ContactBook a conversation through the contact form.

Book a conversation

Menu

Product

Product overview
OperationsRun the system as an organisation: owners, a review queue, rituals and exceptions that end.
SeeKnow what your system really is: a health check and an audit with evidence.
ShapeTyped tokens, one contract per component, and components written and checked. Your look stays.
GovernOwners, rules, exceptions and a review queue, kept as records in your repository.
RunAgents do the routine work under rules your people set.
Loom BaseOur own design system, built and checked by our own engine.
Agents and MCPGive agents your real system, check their work and record what is missing.
SecurityLeast-privilege access, your model and keys, labelled AI output.

Roles

Roles overview
Design-system ownersOne queue, decisions on record, and a system that reports on itself.
CTOs and engineering managersGovern what your AI tools write, in your own repository and CI.
Product managersRequests with service levels, plain release notes and what you can reuse.
CEOs and stakeholdersThree measures from the first month, and one page a month.
DesignersAsk once, see your ask move, and keep Figma and code in step.
DevelopersChecks that name the fix, and migrations written for you.
Accessibility ownersThe only person who rules on accessibility, with the evidence in front of you.
Content and UX writingVoice and terminology as rules Loom checks in your copy.
Ops leadsThe rhythm of the system: queue, rituals, comms and cover.
Organisations with many brandsOne system across brands, regions and products, each layer owned.

Proof

Proof overview
Read your own stylesheetPaste your CSS or tokens and see the decisions nobody made.
One quarter of a design systemThirteen weeks of a sample system, with an operating model and with tools only. Sample data.
The agent's draft, checkedA scripted agent's drafts with the real findings of Loom's check.
What arrives in your repositoryThe pull request Loom's own commands write, on a sample repository.
Score usEvery check behind our own scores, and the command to reproduce each.
Before and afterThe same button before and after tokens: the look stays.
Agent replayWatch a recorded agent build with Loom's MCP server.
Health checkA self-assessment. About three minutes; your answers stay in your browser.
ArticlesArguments about design systems, governance and agents.

About

About overview
AboutWhy Loom exists, and who is behind it.
TrustHow we keep our claims honest and handle your data.
How we workHow an engagement works, from a health check to ongoing care.
DESIGN.mdA whole design system in one Markdown file, exported by Loom. Read two examples.
PartnersDesign agencies, and a prospective partner in Japan.
ContactBook a conversation through the contact form.

Book a conversation Start with a free health check

A loose thread.

This page does not exist or has moved. Every section of the site is listed below, or go back to the home page.

Back to the home page See the demos

ProductHow we run your design system with you, and the four jobs it needs.
RolesHow each role in your organisation uses Loom, and what it gets back.
AcademyCertify everyone who uses your system, and keep them current.
ProofTry Loom in your browser. Each demo says what is real.
ResourcesLearn at your own pace.
AboutWho we are and how we work.

Loom

The next level of your design system.

Product

Product overview
Operations
See
Shape
Govern
Run
Loom Base
Agents and MCP
Security
Academy

Roles

Roles overview
Design-system owners
CTOs and engineering managers
Product managers
CEOs and stakeholders
Designers
Developers
Accessibility owners
Content and UX writing
Ops leads
Organisations with many brands

Proof

Proof overview
Read your own stylesheet
One quarter of a design system
The agent's draft, checked
What arrives in your repository
Score us
Before and after
Agent replay
Health check
Articles

About

About overview
About
Trust
How we work
DESIGN.md
Partners
Contact

Pages describe what runs today; plans are under Coming next, and every capability's state is on What runs today. Sample data is labelled. Loom is based in Singapore.

Data and privacy Security Accessibility What runs today Book a conversation Health check This site's DESIGN.md This site runs on LoomType: Archivo, Atkinson Hyperlegible Next and Martian Mono, SIL Open Font License.