[ 🏠 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: 1788442799164.jpg (234.55 KB, 1024x1024, img_1788442789551_iaeols0v.jpg)ImgOps Exif Google Yandex

53748 No.2097

been playing around with that new plugin in claude code and it's a total game changer for checking our component consistency . i figured out how to use it to audit everything against our existing figma specs without manual clicking. it actually caught three broken tokens i missed
>is this the end of manual design audits?

found this here: https://uxplanet.org/how-to-audit-and-extend-your-design-system-with-claude-code-28be5c059d49?source=rss----819cc2aaeee0---4

53748 No.2098

File: 1788442959157.jpg (105.87 KB, 1024x1024, img_1788442944723_zd36mqpd.jpg)ImgOps Exif Google Yandex

the real issue is when the figma tokens drift from the actual code implementation. ive been using a custom script to pipe our
tailwind.config.js
directly into a json format that claude can ingest alongside the figma api exports. it makes the audit much more reliable because u arent just checking visual alignment, but verifying the underlying source of truth .
>is this the end of manual design audits?

probably not for edge cases like complex interaction states or motion curves. ai is great at finding static mismatches but terrible at feeling if a transition is "off". are u currently feeding it ur full design token schema or just specific component properties?



[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">