Now that you’ve seen how other teams are using this setup, let’s walk through how to actually implement it and what features inside Supernova can streamline your work.
One of Supernova’s features enabling this unified approach is the Brands feature. It helps you structure and scale your system within a single design system by separating tokens, components, and documentation by brand, product, or platform.
The Brand feature in Supernova acts like a folder structure inside your design system data. It allows you to differentiate design decisions and manage complexity—without having to create separate design systems.
Each Brand can have its own Figma Data Source, its own documentation logic, and its own export pipelines—all neatly organized under one roof.
When the Brand feature is enabled in a design system:
→ You can assign tokens, assets, and components to specific brands.
→ Each brand can have its own Figma Data Source, keeping design files separated.
→ Documentation can be structured to show brand-specific content, while still living within a single documentation site.
→ Code automation pipelines can be customized per brand, ensuring that tokens and assets are delivered correctly to each respective platform.
This feature also improves flexibility around code automation. By assigning tokens and assets to a specific brand, you can configure brand-specific pipelines with ease.
1️⃣ Enabling the Brand Feature
To enable the Brand feature in Supernova:
2️⃣ Assigning Tokens, Assets & Components to Brands
3️⃣ Structuring Documentation for Multiple Brands
When working with multiple brands or themes, Supernova’s Figma Variables Sync plugin makes it easy to bring structured design data into your system. This plugin allows you to sync collections and modes from Figma directly into Supernova, where they become fully manageable design tokens. It’s an essential part of making your multi-brand setup functional and future-proof.
If you’ve enabled multiple Brands in your Supernova design system, you’ll be able to select which Brand each collection of variables and/ or modes belongs to when pushing them from the plugin. This ensures clean separation between tokens used by different brands or platforms, all within a single design system structure.
You can choose which Figma mode maps to which Supernova theme, preserving names and context when managing multiple visual styles like Light and Dark modes.
You have one Figma library with these Collections:
Collection 1 (Brand 1): Light Mode & Dark Mode
Collection 2 (Brand 2): Light Mode & Dark Mode
You can sync each collection to its corresponding Brand in Supernova, and Supernova will handle the rest—preserving your naming, structure, and themes across the board. Later, in your documentation, you can use Token Swatches inside a Token Block to visually represent these themes per brand.
Once your token architecture is mapped and organized by brand, it’s time to bring automation into the picture. Supernova allows you to build dedicated export pipelines for each brand, so you can deliver tokens and assets directly into your codebases—fully automated and completely customized per platform, brand, or product area.
Whether your team is using Figma variables to build design system components or product-specific features, these pipelines help eliminate manual handoff and reduce delivery time. You can configure naming conventions, color formats (HEX, RGBA, etc.), and output formats per brand.
Each Brand in your system can have its own:
This setup makes it easy to scale code delivery alongside your design system, especially as different teams work at different speeds, use different frameworks, or follow different release cadences.
💡 We’ll dive deeper into how to configure pipelines and exporters in Chapter 5—but it’s good to know that the Brands feature you’re setting up now is what unlocks this level of automation later on.
Now that you’ve learned how to leverage the Brand feature and structure your design data in Supernova, it’s time to explore how your team can collaborate effectively within this setup.