Skip to content

Design System & assets

The Design System gate captures your visual language, colors, type, and components, so your screens (and eventually your code) are built from a consistent foundation. Unlike most gates it’s form-based, not a chat: you fill in the system directly. Fonts you upload here are pulled into your repo’s design cache by cubedot init, so your agent builds with the real typefaces.

You can connect Figma two ways, depending on the path you use. Figma is available on Trial and Pro (see Plans).

  • API path, a personal access token (PAT), added on the project’s Integrations page, lets CubeDot read frames you reference.
  • MCP path, cubedot init --enable-figma uses OAuth so your coding agent can pull design context live while it builds.

The optional, terminal gate. Attach real design screens or Figma references to lock the UI, tied to the screens defined in UX Design. Because it’s optional, you can ship a full blueprint without it and add screens later.

Images you upload can be tagged as wireframes or design screens; the library groups them so the right visuals feed the right gates.