Tailwind CSS for designers
Why utility classes feel like Figma properties.

Zander Whitehurst
10 min read
The first time most designers see Tailwind, they recoil. A single element with fifteen classes crammed onto it looks messy, unreadable and frankly a bit rude. I had exactly that reaction. Then I spent a week with it and realised it was the most designer friendly way of writing CSS I had ever used.
The reason is simple. Tailwind classes map almost directly to the properties panel in Figma. Once you see that connection, reading and writing them feels natural, and directing an AI agent to build your designs gets much easier.
What Tailwind actually is
Tailwind is a CSS framework made of small, single purpose classes. Instead of writing a separate stylesheet with a custom class for every component, you apply styles directly in your markup:
<button class="bg-blue-600 text-white px-4 py-2 rounded-lg">
Save changes
</button>
Each class does one thing. bg-blue-600 sets the background. px-4 sets horizontal padding. rounded-lg sets the corner radius. That is the whole idea.
It reads like the properties panel
Select a frame in Figma and look at the right hand panel. Fill, padding, corner radius, gap, stroke. Now look at a Tailwind class string. It is the same list, just written as words.
- Fill becomes
bg-white - Padding becomes
p-6 - Corner radius becomes
rounded-xl - Stroke becomes
border border-gray-200 - Drop shadow becomes
shadow-sm
I find this genuinely calming. When I read a Tailwind component, I can picture it in my head the same way I can picture a Figma frame from its properties.
Auto layout is flexbox
If you are comfortable with auto layout in Figma, you already understand most of flexbox. Tailwind makes the connection obvious:
<div class="flex flex-col gap-4 items-start">
That reads as vertical auto layout, 16px gap, aligned to the start. Swap flex-col for flex-row and you have horizontal auto layout. justify-between is the "space between" setting. Once this clicks, most layouts stop being mysterious.
Spacing is a scale, not a guess
Tailwind uses a spacing scale where each step is 4px. So p-1 is 4px, p-4 is 16px and p-6 is 24px.
This is wonderful for designers because it nudges everyone towards consistent spacing. If your Figma files already use an 8px grid, it maps cleanly. You will notice quickly when someone uses an odd value like p-[13px], and you will feel righteous about it, which is one of the small joys of design engineering.
Colours become tokens
Tailwind ships with a default colour palette, but most teams configure their own to match their design system. That means your classes can say bg-primary or text-muted instead of raw values.
This is where designers can have real impact. If your Figma variables and your Tailwind theme use the same names, design and code speak the same language. Ask Claude to set this up for you and check that the names match exactly.
Responsive design without the headache
Tailwind handles breakpoints with prefixes. A class without a prefix applies everywhere, and prefixes like md: and lg: apply from that size upwards:
<div class="grid grid-cols-1 md:grid-cols-2 lg:grid-cols-3 gap-6">
One column on phones, two on tablets, three on desktops. This mobile first approach takes a little getting used to, but it makes responsive behaviour visible right there in the markup.
States are prefixes too
Hover, focus and disabled styles work the same way:
<button class="bg-blue-600 hover:bg-blue-700 focus-visible:ring-2 disabled:opacity-50">
Seeing every state in one place makes it much easier to spot when one is missing. I have caught more forgotten focus states by scanning Tailwind classes than I ever did in Figma handoffs.
Why it works so well with AI
AI coding tools are very fluent in Tailwind. Because styles live directly on the element, Claude can see and change exactly what it needs without hunting through stylesheets.
It also makes your feedback precise. Instead of "add more space", you can say "change gap-4 to gap-6". The agent knows exactly what you mean, and you can check that it did it.
A few things to watch for
Tailwind is not perfect. Long class strings can get hard to read, and it is easy to repeat the same styles in lots of places. The answer is usually to turn repeated patterns into components rather than writing the same fifteen classes over and over.
My first Tailwind project had the same card styles copied into nine files. Changing the border radius was an afternoon I would rather forget.
Start with one component
Pick a simple component from your product, like a card or a button. Open it in Figma and write down every property in the panel. Then try writing the Tailwind classes yourself before asking Claude. Compare your version with Claude's. Do this a few times and you will be reading Tailwind as fluently as a properties panel. Our Frontend UI for Designers workshop is a good next step if you want to practise this with guidance.
Memorisely