Each item in the current selection becomes an instance of the named component at the same position
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.
Generates a style guide using your local styles
Flips color styles containing "Light" and "Dark" https://twitter.com/jsngr/status/1481014510437736457
This automation specs out your component and uses some specs components to annotate the padding. This automation was inspired by the work done by DDG Autolayout and builds on top of it.
this automation groups your main components together automatically for you https://twitter.com/jsngr/status/1483469784461283329
Spec out the spacing (columns) of an auto-layout. See it in action: https://twitter.com/abeyang/status/1478860588713349120
This automation finds an "Original" frame, then duplicates and resizes it based on the amount of items and included properties from a source array. It then arranges the duplicates and the original into a grid based on user input values (items per row and distance apart). You'll need to set the element constraints in the source frame, and if you want to adjust the number of items / names of items dig into the {{sourceArray}} Useful for quickly visualizing how a design might look in different sizes (multiple media units or responsive layouts for example). Inputs: Source frame: the name of the "original" frame to duplicated Items per row: the number of items in each row of the grid to be created Distance apart: the distance between each item in the row (used in column calculation too) Source array: [ { "itemName": "iPhone14Pro", "itemWidth": 393, "itemHeight": 852 }, ... } Credits: This automation uses the Grid-Maker logic by Bred (https://automator.community/automation/grid-maker) for the arrangement. Thanks Bred! Image credit: https://unsplash.com/@seanwsinclair
1️⃣ Generate color swatchs from selection of colors. 2️⃣ Update existing colors. 3️⃣ Easily generate HSL, HSB & HEX values from selection. See this all in action: https://twitter.com/SatbirArora/status/1592247743438737408
Loop over selected Frames, outputting scaled components at a 1:1 size defined from user input. Great for processing large icon batches. Optional User-defined batch component description. I normally use this to drop the icon library name. *Icons in the demo image are examples created from rebellenoire's icon library https://teenyicons.com/
Export all selected color styles in the local library into created color chips with named labels and HEX codes.
Replaces selected component(s) by an instance, reparents these, then moves the components to a dedicated page (default to "Components")
Inspired from the automation from Jono Young, this automation creates a file structure with the following pages: 1. Cover with library instance 2. Discovery 3. Wireframe 4. Visual design - mobile 5. Visual design - desktop 6. Prototype - mobile 7. Prototype - desktop 8. Idea icebox 9. Rejected
It takes your parent, grand parent, and even grand^2 parent layer names and set a new layer name with them.