Engines
In the app, and through the API and MCPThe map behind your system.
Grails works out how your pieces connect at every sync, with no manual work: which components use which, which tokens they bind, which tokens alias which. People add the relations only they know.
Closed alpha: request access at no cost during the period.
- usesButton
- Buttonuses
- Buttonbinds tokencolor/brand/primary
- color/brand/primaryaliases
- aliases
- Buttonalternative todeclared
- see alsocolor/brand/primarydeclared
Capabilities
What you can do
Derived at every sync
Component usage, token bindings and aliases are read from Figma and kept as relationships. Nobody has to maintain them.
Declared relations
People can add eight relations Figma cannot know: relates to, see also, pairs with, excludes, alternative to, replaces, refines and same as.
In the app: direct relationships
Sub-components, Used in, Used tokens, the alias chain and the Related block show each entity’s direct relationships as lists.
Through the API and MCP: impact
Ask what depends on an entity before you change it, walk related entities up to three hops with the path between them, and get the order in which to build a component, dependencies first. A token binding carries a property, the variants and the layers where it was found.
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.