Your system
In the appDocumentation that lives with the component.
Write about a component where it lives: beside its spec, linked to its tokens, with the component’s version history one click away.
Closed alpha: request access at no cost during the period.
The Docs tab of a component page, drawn as a schematic: written text that mentions a token as a chip, a guideline, the component's props and the Related block.
Swipe sideways to see the whole screen.
Capabilities
What you can do
Blocks that know what they are
Title, Text, Table, Props, Specs, Guidelines, Use cases, Checklist, Image, File and Related. Each is a typed block, not a blob of text, so people and agents read the same structure.
Guidelines with reasons
Guidelines are written as Must, Should, Should not or Must not, each with an optional reason beside it.
Mentions that open things
@mention a component or a token and the chip opens it.
Related, both ways
The Related block lists the relations a page declares, and the ones other pages declare toward it.
Pages, folders and categories
Pages live in folders. Each block carries a category (usage, accessibility, developer specs, content guidelines, brand or general), and a long page can be filtered by it.
Markdown in, Markdown out
Bring a .md file or pasted text in as blocks, and export a page as Markdown.
Agents can read it, and write it
Through the API and MCP an agent can read your documentation and, with a write scope, add to it.
Everything is related
Connected to
Nothing in a design system stands alone. These are the features this one works with.
See your own design system in Grails.
Request access, connect the Figma plugin and scan a file. Nothing is synced until you start it.
While in Alpha, we are working 1:1 with teams to improve the product. Access during this period is per-request only.