Resources

Start with a free health check

A self-assessment in your browser: 16 core questions across eight areas, with an optional deeper section. You see a score per area straight away, with unknowns shown separately as blind spots. It takes about three minutes and needs no account. Working

Your answers stay in your browser. Only if you ask for the full report do we receive your contact details, your profile and your area scores. Working

The result suggests one of three next steps: a discovery, a conversion or the platform.

Read our arguments about design systems

Arguments about design systems, governance and agents, with their sources.

• Your design system needs an operator, not more documentation. Why systems drift faster now that agents read them, and a checklist for what "AI-ready" means. (Manifesto, 7 minutes)
• How agents use a design system. What an agent needs to build on-system, and what it should never decide alone. (Agents)
• Governance for small teams. Propose, review, accept, release, with one or two people. (Governance)

The rubric is public

The rubric. The public eight-area standard that the health check, the audit and the control area all use, with what "good" looks like in each area. Working

Product documentation for setting up the MCP server, running the audit and writing governance records is shared with pilot teams today. Public documentation is planned. Concept

A whole system in one DESIGN.md file

DESIGN.md is an open file format, still in alpha, that describes a design system for AI design and coding tools in one Markdown file: colours, type, spacing, components, and rules on what to do and what to avoid.

Loom writes a DESIGN.md for any system it has read, from the system's records. Tokens keep your own names. Components, patterns, rules, brand and voice come from the same records the MCP server uses, and the file ends with a section on how agents should use the system. Where a record holds nothing, the file says "not defined". It never fills a gap with a guess. A check can run in CI and fail when the file is out of date. Working

What does not work yet: the file holds only the default mode's token values, it has not been checked with the official DESIGN.md command-line tool, and Loom does not yet deliver it to a client's repository as a pull request.

Here is one entry from Loom Base's file, read when this page is built:

# The Loom Base design system (@loom/base), exported by Loom from its records: 2312 tokens, 69 components, 11 patterns.

### Button
`import { Button } from "@loom/base/native";` · lifecycle beta · tier component
- **Use when:** To start an action that changes data or opens something on this page; To submit a form (set it as the form's last control); As a toggle (pressed) for an on/off f…
- **Do not use when:** Going to another page or URL → Link; Choosing one of several options → RadioGroup or Select; Turning a setting on or off that takes effect immediately → S…
- **Variants:** `tone`: primary | secondary | quiet | danger. primary: the one main action in a view; secondary: other actions; quiet: toolbars and dense areas; danger: removes …
- **Keyboard:** `Enter` PRESS; `Space` PRESS; `Tab` A disabled button is skipped; a busy one is not

Two files you can read today:

• Loom Base. Our own design system, exported by Loom: 69 components.
• This site. The rules this site is built with.

A note on where DESIGN.md fits. A single file is useful for art direction, prototyping and theming. For production code, a June 2026 test by Atlassian found that agents got much more of a system's context from on-demand tools such as an MCP server, and that a single file led agents to rebuild components instead of importing them. Atlassian calls its results not conclusive. That is why every system Loom produces ships an MCP server first, and a DESIGN.md as a second way in.

Data and privacy are explained in plain words

How we handle data on this site, in the health check and in an engagement: what we store, where, for how long and who else is involved.