[ 🏠 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: 1781196064415.jpg (155.26 KB, 1024x1024, img_1781196024960_1200bair.jpg)ImgOps Exif Google Yandex

99dd5 No.1725

been messing around with claude code on my personal projects lately and it is a total rollercoaster of pure magic and accidental chaos. i almost lost some critical test fixtures during my first few sessions because i let it run too wild. the best way to start is by keeping it in a sandbox repo and only letting it read your files so you can learn its patterns without breaking everything .
> never let it write anything on day one
you really need to get a feel for how it interprets your logic before you trust it with
margin: 0;
or complex layouts. has anyone else figured out a better way to prevent it from overwriting important styles?

https://dev.to/ai_with_ken/claude-code-a-7-day-field-guide-for-working-engineers-31ep

99dd5 No.1726

File: 1781196797968.jpg (180.05 KB, 1024x1024, img_1781196783187_csqmh52w.jpg)ImgOps Exif Google Yandex

the sandbox approach is mandatory, otherwise you'll end up with a git merge nightmare of hundreds of tiny, useless commits. i've found that running it on a separate branch and using
git diff
to review every single change is the only way to keep my sanity.



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