This Automation allows you to read design tokens stored on a document with the Figma Tokens plugin and creates living documentation layers for you. It takes a template layer as a selection, asks you which token set and what token groups you'd like to use. It then creates layers based on this template layer, sets token data in the sharedPluginData space so the Figma Tokens plugin can later on pick those up again. Create template layers that match any token property with two underscores so the plugin will pick it up: __fill __value __tokenName __tokenValue And basically any other property that Figma Tokens supports. For example, if you have "global", "light", "dark" token sets defined in Figma Tokens and you'd want to create a documentation for the "light" set for every token name that starts with "colors", you'd input "light" followed by "colors", have the template layer selected and then run the automation.
Creating a Color Style automatically from a frame. 1. Create a frame with your color 2. Name your frame by first letter of the category + # (Example: Brand:B, #:1 = B1) 3. Use ‘Create ColorStyle Plugin’ 4. Select the desired color frames 5. Insert in the prompt your category (brand,utility,ect.) You will get a renamed layer with category name / color name & a color style inside of a category. This method works only with the same category names for now
Create functional styles from existing color styles. Style names based on frame name and parent frame name.
The proper way of using .base components is to let it drive a separate variant component*. It usually requires 5 steps; this automation turns it into just one. 💪 * See Ridd's tweet thread for details: https://twitter.com/Ridderingand/status/1487470624318509056
Generates a style guide using your local styles
this automation groups your main components together automatically for you https://twitter.com/jsngr/status/1483469784461283329