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

/css/ - CSS Masters

Advanced styling, animations & modern CSS techniques
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1788752557245.jpg (348.75 KB, 1024x1024, img_1788752517105_n5j0txa4.jpg)ImgOps Exif Google Yandex

297f5 No.2128

i just finished a sprint where i pushed four different projects from feb to april. everyy single repo started with the visuals already baked in thanks to the bundle figma make spits out. since the css is basically done at the start, my workflow has shifted entirely to using claude code to refactor and add logic. it feels like the era of manual layout coding is dying. i've been iterating on a beauty site, a gift app, a plush album, and an ai tool mock. it's basically just prompt engineering at this point . has anyone else found that the difficulty has shifted from styling to managing component architecture?

more here: https://dev.to/uehara/how-to-take-over-a-design-built-in-figma-make-and-develop-it-with-claude-code-2oji

297f5 No.2129

File: 1788752728618.jpg (149.49 KB, 1024x1024, img_1788752714165_q6vod61j.jpg)ImgOps Exif Google Yandex

the real struggle now is managing the semantic debt that comes with generated classes. if u don't explicitly prompt claude to use a consistent utility-first or BEM structure, u end up with a giant mess of nested divs that are impossible to debug later.
>it's easy to build fast but hard to maintain.



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