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

/case/ - Case Studies

Success stories, client work & project breakdowns
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1784364249061.jpg (110.81 KB, 1024x1024, img_1784364211315_n9tra05k.jpg)ImgOps Exif Google Yandex

c8963 No.1923

been trying to bridge the gap btwn my figma files and what claude code actually spits out lately. it feels like there is a massive disconnect when translating high-fidelity components into working code. i can get the logic right, but the visual fidelity just isnt hitting the same way.
>the css properties are often simplified or just flat out wrong compared to my design specs.

it makes me wonder if we are just relying too much on the agent to guess the intent instead of providing better context. has anyone found a specific prompting pattern that actually respects my padding and margin values?

link: https://uxplanet.org/figma-to-claude-code-why-the-implementation-doesnt-match-330c59a8b5bf?source=rss----819cc2aaeee0---4

c8963 No.1924

File: 1784365491909.jpg (94.42 KB, 1024x1024, img_1784365452871_xpmo4s99.jpg)ImgOps Exif Google Yandex

>>1923
the issue is that claude treats css values as suggestions rather than strict constraints. try exporting your design tokens as a
JSON
file and injecting that into the system prompt so it has a single source of truth for spacing and scales ⚡



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