Extended collections

 

When you sync extended collections, Supernova preserves the hierarchy and merges variables into a unified token structure. Each variable appears once in your token list, with values that can be overridden at different collection levels. The modes from your Figma collections become themes in Supernova, which control how token values resolve in exporters and documentation.

Syncing extended collections

• When you select any collection in a hierarchy, the sync configuration applies to the entire hierarchy — the root and all children share the same setting for base token value and themes import.
• When you push an extended collection, all parent collections up to the root are automatically included.
• You cannot sync an extended collection without its parents. If parent collections exist in a remote Figma library (in another file), they will be imported as well.
• In the plugin, the Remote badge indicates root or parent collections from external files.

How collections and themes map to Supernova

Collection hierarchy

Your Figma collection hierarchy maps 1:1 to Supernova. For example, if you have Semantic Colors → Brand A in Figma, you’ll see the same structure in Supernova.

Modes → themes

Figma modes become Supernova themes. All collections in a hierarchy share the same modes, so if your root collection has Light and Dark modes, all child collections have Light and Dark as well.

Theme merging

Modes with the same name across the hierarchy will merge into a single theme in the Tokens view. For example, if Semantic Colors has Light and Brand A has Light, you’ll see one “Light” column in the tokens table — not two. This merged view shows root-level values by default.

Collection-specific themes

When you need to resolve a token at a specific collection level (in exporters or documentation blocks), you select a collection-specific theme like “Light • Brand A”. This tells Supernova to resolve values using that collection’s overrides.

Theme value resolution

Token values are resolved by traversing up the collection hierarchy until a value is found for the selected theme.

Example:

• Semantic Colors (root): foreground.primary = blue
• Brand A (child): foreground.primary = green

If Brand A did not override foreground.primary, selecting “Light • Brand A” would still resolve to blue — the value inherits from the parent.

Viewing overrides in Supernova

• All tokens view: Tokens appear once with root values shown. A counter badge next to the value indicates how many levels override that token. Open themes tab in the token detail to see the full hierarchy of values.
• Collections view: The collection hierarchy appears on the left, just like in Figma. Select a collection to see its resolved values in the table. The same tokens appear regardless of which collection you select — what changes is the resolved value per theme for that collection level.

Multi-file sync

When a collection extends a collection from a remote Figma file (library), the plugin marks it with a “Remote” badge. Remote collections are automatically selected and pushed together with local collections.

Sync conflicts

If a remote collection doesn't match the last synced version, the plugin warns you: “Remote collection may be outdated. Pull the latest library updates in Figma before syncing to avoid overwriting newer changes.”

If you proceed, the new sync will overwrite the previous one. To avoid unintended overwrites, make sure you pull the latest library updates for your Figma file before syncing.