I am using a robust design system and token library with components that have variants for different states like active, hover, error etc. Our token library has theming for light and dark mode. I would describe our design system as robust and well made using best practices for a mid sized to large design system.
I have exported the library for make and the library appears as an option when designing with Make. My issues is that the designs it creates do not resemble our design system. The text input components we use are similar to default Material 3 text fields. The designs created sometimes use a Material UI style but it uses outlined inputs or inputs with detached labels. The colors are sometimes close but it seems truly coincidental and not related to our actual token library.
In fact after testing and prodding I see no difference in using our design system library and using no reference. My suspicion is that it simply does not understand our library and is moving forward with default values. I do not see any of the relevant tokens that are a part of our library and the actual components show in the code do not match the components of our design system.
What I’m trying to solve for is how do I successfully add our library with reusable consisten components and tokens that match our design styles? I’m hoping it is something as simple as tweaking the format of our component naming, or token naming.
For reference I will include some views from our DS library to show the structure and naming. Hopefully someone can point out a flaw in my design here or point me in the direction of a library that actually works with Figma Make. I don’t mind if I need to dramatically simplify the design.
Token A (color example)
Token B (theme example)
Right Panel Component Selected (I use true false for toggling variant states)
Left Panel Component Selected (naming structure)
