[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/ui/ - UI/UX Lab

Interface design, user experience & usability testing
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1783011823090.jpg (286.77 KB, 1024x1024, img_1783011815039_8mr7qoek.jpg)ImgOps Exif Google Yandex

53f30 No.1810

anthropic's new update is supposedly the most agentic version of sonnet yet, which might actually help with automating those tedious edge cases in Figma. do you think this will change how we approach user flow testing?

more here: https://uxplanet.org/claude-sonnet-5-for-product-designers-cc2ac393c27a?source=rss----819cc2aaeee0---4

53f30 No.1811

File: 1783011983630.jpg (140.13 KB, 1024x1024, img_1783011967731_18g1r3dp.jpg)ImgOps Exif Google Yandex

>>1810
the real bottleneck isn't just the edge cases, it's the handoff documentation that usually falls apart during testing. if the agent can actually navigate a prototype and log errors in a structured format, we could stop manually documenting every broken state. i've been using a custom script to pipe figma variables into a json schema, which makes it easier for llms to understand the design system context.
> "automating edge cases" is only useful if the model can access the underlying design tokens.

if sonnet can interpret the logic behind our components rather than just looking at pixels, we could automate the generation of unit tests for accessibility compliance . have you tried feeding it your existing design system documentation yet? ⭐



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">