On this page
Figma Setup
Design with Nebula in Figma.
Nebula Enterprise is Nebula as a Figma library, describing the same components as the React library.
Access
You need a Figma seat to design with the library. Request one from inside Figma, which sends it to an admin to approve.
The library itself is added to every Kaluza Figma file by default, so its components, styles and variables are in your assets panel already. If it isn't there, open the Assets tab, add more libraries, and search for Nebula Enterprise.
Using components
Drag the component you want from the assets panel onto the canvas.
Use the component rather than drawing your own. A redrawn component will look right in the file and then behave differently once it's built, because the thing that ships is the React component and not your drawing of it.
Change an instance through the properties panel rather than by showing and hiding layers in the layer tree. The panel lists what the component is built to vary.
Avoid detaching an instance. Where the properties don't cover what you need, that's worth raising rather than working around: a detached instance will stop receiving library updates, and nothing will flag it later.
For anything beyond placing one, go to the library file. Each component has its own page in it, named after the component, holding its variants and states as labelled sections. The quickest route is the Figma button next to the title on any component page here.
Colour, spacing and type
Use the library's variables rather than raw values. See Colours, Spacing and Typography for what each one is for. A hard-coded hex is the same problem as a redrawn component: it won't follow a theme change, and nobody downstream can tell whether you chose it deliberately.
Where Figma and the code differ
We aim for the Figma library and the code to match one to one, and we don't guarantee it. Two kinds of difference are deliberate.
Some interactions can't be reproduced usefully in Figma, and modelling them costs more than it's worth. Where a behaviour only exists in code, you'll find it on the component's own page rather than in the library.
Some are grouped differently on purpose, to keep the Figma library easier to work in. CTAButton and CTALink are a single 'Button' component in Figma, so both link to the same Figma page.
Anything else is drift. If you find a variant, a property name or a token that disagrees between the two, flag it rather than designing around it, because the next person will hit the same thing and won't know which side is right.
Claude and the Figma canvas
Claude can read a Figma file and make changes to it through the Figma MCP server, which makes it useful for the mechanical parts of a design: laying out a screen from components that already exist, or applying variables across a file.
Point it at your own file, not at the Nebula Enterprise library. Changes to the library are a design system decision and they reach everyone, so they go through the design system team rather than Claude acting on a prompt.
For what else Claude can do with Nebula, and how to set it up, see Using Nebula with AI.
Support
For anything about Nebula in Figma, including a mismatch between the library and the code, contact the design system team on Slack at #ug-design-system. For Figma itself, #ug-figma.