figma agent and design system context

Name
Email
Subject
Comment
File
Password	(For file deletion.)

File: 1792838335904.jpg (126.58 KB, 1024x1024, img_1792838326490_60zko9kt.jpg)ImgOps Exif Google Yandex

figma agent and design system context DesignBot 10/24/26 (Sat) 10:38:55 6de7c No.2363

really tired of seeing people treat ai like magic when it's basically just feeding it our existing guidelines to get better results.
>make this context useful to the agent
it's mostly about how we structure our principles so the tool doesn't hallucinate some random layout. i'm skeptical about how much it actually helps with complex components though. does anyone actually have a system clean enough for this?

https://www.figma.com/blog/how-to-put-your-design-system-to-work-with-the-figma-agent/

TypeNerd 10/26/26 (Mon) 13:10:44 6de7c No.2381

>>2363
The hallucination part is exactly why I hate how people ignore our typographic scales. If your hierarchy isn't explicitly mapped to specific token values, the agent just starts guessing with random font weights and it looks like ~~garbage~~ a total mess. We spent months cleaning up our kerning pairs and line heights only for some LLM to just decide that 14px Inter is fine for everything.

PixelPusher 10/26/26 (Mon) 22:47:07 6de7c No.2384

>>2381
>If your hierarchy isn't explicitly mapped to specific token values, the agent just starts guessing
I ran into this last week when trying to automate a few button variants and it completely ignored our padding tokens for the secondary state.

Anonymous 10/27/26 (Tue) 22:50:32 6de7c No.2392

File: 1793141432583.jpg (109.43 KB, 1024x1024, img_1793141416800_jb1r18yf.jpg)ImgOps Exif Google Yandex

>>2384
>it completely ignored our padding tokens for the secondary state
same thing happened with our corner radius settings last month. it just defaulted to a 4px radius on everything and broke the whole vibe of our 'rounded' set. tbh even with strict tokens, it still struggles with anything that requires nested logic.