---
title: Figma
slug: wip/hx2w-figma
createdAt: 2024-10-17T09:17:31.962Z
---

# Customization & Theming: Figma

:::Iframe{code="<iframe title=&#x22;Embeded content from codepen.io&#x22; class=&#x22;no-border max-full-width full-height flex-grow&#x22; src=&#x22;https://codepen.io/redbulldesign/embed/wvqyLRj/3daed4a5a31e0b8c4ec7de5d8af2869d?default-tab=result&#x26;amp;theme-id=39402&#x22; height=&#x22;438px&#x22;></iframe>"}

:::

While CSS Custom Properties make styling components straightforward in code, Figma currently lacks similar comprehensive theming capabilities. These guidelines provide **strategies** **for customizing Cosmos web components** in Figma. We recommend that designers **use Cosmos components** whenever possible and **style** **them** **through** **local instance overwrites** or **wrapped** **Cosmos components** to improve reusability.

These strategies enable designers to **receive updates** from the Cosmos Web Components library after applying customizations, **stay in parity** with code integrations, and **streamline** **hand-offs** across the organization.

## Instance Overwrites

This strategy is **ideal for smaller projects** such as landing pages, where you may use a customized component in one or a few places, but do not have to worry about re-usability.

### Customization in Design

Start by selecting a **start with a Cosmos component -&#x20;**&#x69;n this example, the [Button](https://cosmos.redbull.design/button). After adding it from th&#x65;**&#x20;Asset panel**, you can locally overwrite any [allowed properties](https://help.figma.com/hc/en-us/articles/360039150733-Apply-changes-to-instances#%E2%80%9Ch_01HXD7C9W8VK2AFP0VRKAP84EZ%E2%80%9D) to match your design language.&#x20;

:::Iframe{iframeHeight="0" code="<rbup-video-backend&#xA;     id=&#x22;player1&#x22;&#xA;     video-url=&#x22;https://res.cloudinary.com/rbmh-platforms-partnerprojects/video/upload/v1738245691/archbee-design-systems/gravity/customization-guidelines/customization_guidelines_-_simple_-_design.mp4&#x22;&#xA;>&#xA;<img slot=&#x22;poster-image&#x22; src=&#x22;https://res.cloudinary.com/rbmh-platforms-partnerprojects/image/upload/v1738318380/archbee-design-systems/gravity/customization-guidelines/Thumbnail_-_Instance_Overwrites_in_Design.png&#x22;/>&#xA;</rbup-video-backend>"}

:::

### Engineering Handover

:::Iframe{iframeHeight="0" code="<rbup-video-backend&#xA;     id=&#x22;player1&#x22;&#xA;     video-url=&#x22;https://res.cloudinary.com/rbmh-platforms-partnerprojects/video/upload/v1738245693/archbee-design-systems/gravity/customization-guidelines/customization_guidelines_-_simple_-_handover.mp4&#x22;&#xA;>&#xA;<img slot=&#x22;poster-image&#x22; src=&#x22;https://res.cloudinary.com/rbmh-platforms-partnerprojects/image/upload/v1738318380/archbee-design-systems/gravity/customization-guidelines/Thumbnail_-_Instance_Overwrites_Engineering_Handover.png&#x22;/>&#xA;</rbup-video-backend>"}

:::

Engineers can compare the changes between the customization and the Cosmos Component i&#x6E;**&#x20;Dev Mode** using the "**Compare Changes**" option in the Inspect Panel.

The Modal's left side lets yo&#x75;**&#x20;navigate through the layer structure**, highlighting "Edited" component parts. The right side displays &#x61;**&#x20;Code Diff** showing the design changes.

:::hint{type="info"}
ℹ️
Flex layout values often appear as changes in code despite not being intentional design changes. Always verify changes by comparing them with the expected visual outcome.
:::

## Local Component Wrappers

Instance overwrites become cumbersome to manage for complex and/or long-term projects where themed component maintenance and reusability matter.**&#x20;In large-scale projects**, designers may handle thousands of instances—without component-level customization, these become time-consuming to update and error-prone.

### Customization in Design

:::Iframe{iframeHeight="0" code="<rbup-video-backend&#xA;     id=&#x22;player1&#x22;&#xA;     video-url=&#x22;https://res.cloudinary.com/rbmh-platforms-partnerprojects/video/upload/v1738245694/archbee-design-systems/gravity/customization-guidelines/customization_guidelines_-_complex_-_design.mp4&#x22;&#xA;>&#xA;<img slot=&#x22;poster-image&#x22; src=&#x22;https://res.cloudinary.com/rbmh-platforms-partnerprojects/image/upload/v1738318381/archbee-design-systems/gravity/customization-guidelines/Thumbnail_-_Local_Component_Wrappers_in_Design.png&#x22;/>&#xA;</rbup-video-backend>"}

:::

First, identify the **Cosmos component** you want to customize and drag it in from the **Asset Panel**. For this example, we've selected the [Badge](docId\:kuVk98G7HkPpCiRryH0TG).

Begin by identifying the variants needed for your project. Add these variants to your canvas, then select all variants and combine them as variants of a single component using the '**create component set**' action.

Next, rename your component `cmd+r` and **create the properties** for your variant set. While property naming is flexible, it's best to align closely with Cosmos property names to help engineers understand and connect the relationship between properties across the local and wrapped component.

![](https://api.archbee.com/api/optimize/Kp4perMrWxGYfa_PWfi7H/hDzy1eDV9x4j0L2rhB5B8_align-property-naming.jpg "Property alignment")

After setting up the component structure, make your desired visual changes by overwriting properties in the wrapped Cosmos component instances.

### Engineering Handover

:::Iframe{iframeHeight="0" code="<rbup-video-backend&#xA;     id=&#x22;player1&#x22;&#xA;     video-url=&#x22;https://res.cloudinary.com/rbmh-platforms-partnerprojects/video/upload/v1738245689/archbee-design-systems/gravity/customization-guidelines/customization_guidelines_-_complex_-_handover_pt1.mp4&#x22;&#xA;>&#xA;<img slot=&#x22;poster-image&#x22; src=&#x22;https://res.cloudinary.com/rbmh-platforms-partnerprojects/image/upload/v1738318381/archbee-design-systems/gravity/customization-guidelines/Thumbnail_-_Local_Component_Wrappers_Component_Playground.png&#x22;/>&#xA;</rbup-video-backend>"}

:::

Since the local component API may differ from the Cosmos Component API, start by using the **Component Playground** to inspect the proposed properties.

:::Iframe{iframeHeight="0" code="<rbup-video-backend&#xA;     id=&#x22;player1&#x22;&#xA;     video-url=&#x22;https://res.cloudinary.com/rbmh-platforms-partnerprojects/video/upload/v1738245691/archbee-design-systems/gravity/customization-guidelines/customization_guidelines_-_complex_-_handover_pt2.mp4&#x22;&#xA;>&#xA;<img slot=&#x22;poster-image&#x22; src=&#x22;https://res.cloudinary.com/rbmh-platforms-partnerprojects/image/upload/v1738318381/archbee-design-systems/gravity/customization-guidelines/Thumbnail_-_Local_Component_Wrappers_Comparing_changes.png&#x22;/>&#xA;</rbup-video-backend>"}

:::

After component inspection, inspect the **Code Diff** for each variant by selecting "**Compare Changes**" in the Inspect Panel. Remember to perform inspection at the component level, not the instance level as described in instance overwrites.

