Skip to content
Grails
ENES
Sign up

Engines

Through the API and MCP

Find what you can’t name.

Describe what you are looking for in your own words, like “the destructive action button”. Grails matches them against the documentation your team wrote, the names of things and the relationships between them, and answers with the components, tokens and styles that fit.

Sign up for freeUse it from an agent

Closed alpha: request access at no cost during the period.

Capabilities

What you can do

  • Five engines, one ranking

    Meaning, the words your documentation uses, names (with a fuzzy floor for typos), graph neighbors and declared relations are combined into one ranking.

  • It reads what you document

    It indexes components, tokens, styles, collections and documentation pages, from what your team wrote about them, with the Figma description added where there is one. The more a team documents, the better it finds.

  • Results with their neighborhood

    Each hit says which engines matched it, shows an excerpt, and counts what the entity uses and what uses it, with up to three of its consumers.

  • Knows when it is unsure

    For each group of results it says whether the top match stands out or the query was ambiguous, so an agent can ask a narrower question instead of taking the first row.

  • Honest about its coverage

    When the index is empty it falls back to names and the graph, and says so. Every response reports its own coverage.

  • Start from an entity you have

    Ask for the neighbors of a component, token or style instead of a phrase, and widen the walk hop by hop.

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.

Sign up for freeGet the Figma plugin

While in Alpha, we are working 1:1 with teams to improve the product. Access during this period is per-request only.