Skip to content

How ExonUI fits together

The catalog, packs, the setup wizard, connect guides, Grid Notes and Grid: what each one is, how they relate and what you can use today.

DocsUpdated 2026-11-12
Browse docs

The pieces

ExonUI's parts and where they stand
PieceWhat it isStatus
Catalog36 design tools, MCP servers, libraries and asset sources, each with what it is, what it costs and how it connects.Live
Setup wizardTurns your choice of agents and tools into one combined setup per agent: commands, config files and install links.Live
Connect guidesStep-by-step setup for one tool in one agent: 183 guides, one for each pair that works.Live
Grid NotesShort, checked notes on using a library with an AI agent: 16 libraries so far.Live
Free toolsDesign utilities that run in your browser: colour, type, spacing, tokens, SVG and easing.Live
Catalog feedThe catalog as one JSON file, for tools that want to read it.Live
GridA local gateway: one MCP server in your agent that searches and calls the tools of the servers behind it.In development. Interactive tour live.

What isn't here yet

Grid isn't published and there's no command-line tool. Today the wizard writes each tool's own entry into your agent's configuration, so nothing you set up depends on Grid.

What a pack is

Behind every catalog entry is a pack: the part ExonUI can act on. A pack has a kind, which decides what you get from it.

Pack kinds
KindWhat it means
mcpA server your agent connects to over MCP. It gives the agent tools, such as reading a design file.
libraryA code library. There's no server: the pack carries an install command, docs and, for many, Grid Notes.
assetA source of assets such as icons, fonts or animations.
skillA bundle of instructions, in a SKILL.md file, that teaches an agent a way of working.
bridgeAn adapter for a tool that has no server of its own, for example one that only exports files.
linkListed for reference only. The catalog describes it but generates no setup.

Who stands behind a pack

Each pack is official when the tool's own vendor maintains it, community-vetted when we've reviewed it and pinned a version, or unverified when we list it without either. The catalog shows this on every entry.

How Grid works

Loading every tool of every server up front fills an agent's context. Grid keeps one small server in front and lets the agent look things up as it needs them, with four tools:

Grid's tools
ToolWhat it does
grid_statusShows which packs are enabled, whether they connect and how many tools they offer.
grid_searchFinds tools and packs by what you want to do, and returns short cards.
grid_describeGives the full details for one result: a tool's inputs and access level, or a pack's install command and Grid Notes.
grid_callRuns a tool from a server behind Grid.

Grid classes each tool as read, write or destructive. Read-only tools always run. For the rest, the pack's policy decides: read blocks them, ask asks you first, and write lets ordinary writes run while still asking before anything destructive.

Note

Grid is a local program in the ExonUI repository. It isn't published, so this page describes how it works rather than how to install it.