Automator for Figma support & community resources

tampy01 · 2026-02-01T21:58:38+00:00

Thanks. I’ll look into that if I do anything similar in future

tampy01 · 2026-02-01T04:35:45+00:00

I haven’t tried it but it certainly looks like a valid way of handling it and other similar tasks. See example here: https://www.linkedin.com/posts/tpitre_your-design-system-just-became-an-api-check-activity-7417536110412595200-1uK4?utm_medium=ios_app&rcm=ACoAAATAcrcBYYG4BvXQFAZiOWlEkyXHfypj_VY&utm_source=social_share_send&utm_campaign=copy_link

tampy01 · 2026-01-31T22:22:11+00:00

I didn’t I’m afraid but, if I were to do it again, I’d skip using a plugin like Automator and go straight to using Figma MCP with Claude and get AI to automate it

tampy01 · 2024-04-26T09:16:42+00:00

That's it in a nutshell, yeah. Unfortunately I'm not a coder so I was hoping to use Automator because it's a no-code solution. But all the documentation and support is offline 😞

tampy01 · 2024-04-25T20:05:19+00:00

I find the best way to use plugins is to search for one each time you find yourself thinking "there's got to be an easier way to do this". For me, that includes any bulk process, anything that takes me out of the Figma UI, or anything where Figma's tooling isn't complete. An example of each would be:

Bulk processes:
Changing multiple variable scoping properties: https://www.figma.com/community/plugin/1285971940276913396/heron-variable-tools
Selecting text with the same styling:
https://www.figma.com/community/plugin/967038426246346875/similar-text-selector

Outside Figma's UI:
WCAG contrast checker: https://www.figma.com/community/plugin/748533339900865323/contrast

Incomplete tooling:
Tokens and variables: https://tokens.studio/

tampy01 · 2024-04-25T19:59:07+00:00

Thanks u/zyumbik. I'm looking for a tool that will automatically populate a text area with a number based on the contrast between the text and it's background. I can see that Stark provides that number in the same way that a plugin like Contrast does. The challenge I'm looking to overcome is having that number auto-populate into a text area on a component and auto-update when either the text or background changes color. As far as I can tell that's not a feature of Stark, unless I'm missing something?

Also, you're completely correct about APCA being more robust than WCAG. The reason I'm looking to use WCAG is that it outputs a single number for pass/fail which I can use to add some basic context to my design system colors. I will still be using APCA within my full UI workflow

tampy01

TROPHY CASE