CSS is the language browsers use to style web pages: colors, type, spacing, and layout. In UX it's where design decisions stop being a mockup and become the thing users touch, which makes it the shared ground between designers and developers.
Use cases
When designers can't read or speak CSS, the handoff turns into a guessing game. Spacing drifts, colors land slightly off, and the shipped product stops matching the file everyone signed off on.
The 4px drift: You spec 16px padding, the developer eyeballs it, and every card ships a little tight. Multiply that across a product and the whole thing feels off without anyone knowing why.
The dark-mode scramble: A team hard-coded hex values everywhere. Adding dark mode now means hunting through hundreds of files instead of swapping one token set.
The responsive surprise: A layout looks perfect in the desktop mockup and collapses on a phone because nobody planned how it reflows. Reading CSS layout catches that before QA does.
How it's used in practice
Speak it enough to spec it: You don't need to write production CSS, but knowing selectors, the box model, and units makes your handoffs precise.
Design in tokens, not hex codes: Define colors, spacing, and type as named variables so one change updates everywhere.
Plan for reflow: Think in flexible grids and breakpoints. The page has to survive every screen size.
Respect user settings: Use relative units like rem so type scales when someone bumps their browser font size to read.
Review in the browser: Check the built component against the design live, not just against the Figma file.
🪄
Pro-tip: The fastest way to earn a developer's trust is to hand off specs in their language. "Use --space-4 and let it wrap below 768px" lands better than a screenshot with arrows. You stop being the person tossing mockups over the wall.
Challenges & limitations
Browser inconsistency: The same CSS can render differently across browsers and versions, so "done" in one place isn't done everywhere.
It's a real skill: Specificity, the cascade, and layout have genuine depth. Half-knowing CSS produces confident-but-wrong specs.
Boundary blur: How much CSS a designer should own is a team question with no single right answer.
