Tailwind arbitrary values vs utility classes

Name
Email
Subject
Comment
File
Password	(For file deletion.)

File: 1792573540454.jpg (128.39 KB, 1024x1024, img_1792573531820_0r7k1row.jpg)ImgOps Exif Google Yandex

Tailwind arbitrary values vs utility classes WebWizard 10/21/26 (Wed) 09:05:40 d9206 No.2369

I've been trying to move away from those long strings of utility classes for specific spacing tweaks because it's just getting unreadable in my components. Using arbitrary values like

top-[13px]

is fine for a quick fix, but I actually prefer keeping a small custom config file for anything that pops up more than twice. Just tried adding a new spacing scale to my theme and it makes the whole template much cleaner.

ScriptKid 10/24/26 (Sat) 22:50:30 d9206 No.2389

>>2369
did the same thing on a landing page last week and my config file is basically just a giant list of random pixels now lmao

ABTester 10/25/26 (Sun) 00:50:17 d9206 No.2391

>>2389
>my config file is basically just a giant list of random pixels now

I've seen this happen too, but I'm not sure how you're measuring the benefit here. Did you run any tests to see if that custom scale actually reduces your bundle size or just adds maintenance overhead? It feels like you might just be moving the mess from the HTML into a massive theme object without actually fixing the underlying design inconsistency.