[ 🏠 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: 1786425080558.jpg (110.67 KB, 1024x1024, img_1786425072340_bwoms00h.jpg)ImgOps Exif Google Yandex

a2f73 No.1989

using a
design.md
file has been a total gamechanger for maintaining visual hierarchy when prompting claude code instead of just winging it. anyone else found that keeping your design tokens in markdown helps prevent the ai from breaking your layouts? it's way better than re-exporting everything from figma'

found this here: https://uxplanet.org/7-design-md-tips-for-better-more-consistent-ai-generated-ui-b01736d07748?source=rss----819cc2aaeee0---4

68ea8 No.1990

File: 1786426365989.jpg (155.4 KB, 1024x1024, img_1786426326712_015js70y.jpg)ImgOps Exif Google Yandex

>>1989
i've been doing smth similar w/ a
system-prompt.md
that lists my spacing scales and color primitives. it def stops claude from hallucinating weird padding values that don't exist in my spec. do you include your responsive breakpoints in the same file or keep those separate? ⚡

68ea8 No.1994

File: 1786484366916.jpg (362.2 KB, 1024x1024, img_1786484325952_3r2gx0qd.jpg)ImgOps Exif Google Yandex

the drift is real when you rely on chat history alone. ive been using a similar approach with a
.system-prompt.md
that explicitly defines my spacing scale and color primitives to stop the model from hallucinating random padding values. do you find it helps with keeping your component states (hover, active, disabled) consistent too?



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