← All works
Design System Case Study4 min read 8 sections

Tailus: A UI Kit That Speaks Tailwind

Designing a Figma UI kit built on Tailwind CSS tokens, so the components a designer drags in are the same ones a developer can write without translating a single value.

Product
Figma UI kit based on Tailwind CSS
Role
Research, design system, and prototyping
Platforms
Responsive web
Published
October 2024
  • 4

    Interview rounds before any pixels

  • 65+

    People interviewed

  • 10%

    Less development time

  • 4

    Prototype stages, paper to clickable

Tailus: A UI Kit That Speaks Tailwind
0108

Overview

Tailus is a Figma UI kit built on Tailwind CSS: pre-designed components that adapt across screen sizes, organised around the same tokens a developer uses in code. The idea was simple. If the colours, spacing, and type scale in the design file are Tailwind's own, nothing gets lost between the mockup and the build.

I ran the project end to end: four rounds of interviews, competitive research, the information architecture, the prototypes, and the final component set.

Tailus: a Tailwind-based UI kit for designers and developers
Tailus: a Tailwind-based UI kit for designers and developers
0208

Research: Four Groups, Four Questions

A UI kit sits between people who want different things. A business wants conversions, a user wants to find things, a designer wants to move fast, and a developer wants something they can actually build. So instead of one research round I ran four, each with its own goals.

GroupWhoTimeWhat they told me
Businesses12 business owners15 daysConversions, brand consistency, and accessibility matter; so does less design-to-development time
Users20+ users30 daysClear hierarchy, fast pages, and layouts that work on every screen
Developers15 developers15 daysTranslating specs into code is slow, and design and dev tools disagree
Designers20+ designers30 daysThey want consistency, a ready component library, and room to iterate
Four interview rounds, run before any design work
0308

The Problem: Two Tools That Disagree

The clearest pattern came from the developers. Every one of their top problems was a version of the same thing: the design file and the code describe the interface in different terms.

What developers saidWhat it costs
Design specs are hard to turn into working codeTime spent measuring and guessing values
Design and development tools don't matchSmall errors that pile up in review
No standard components or guidelinesEvery project looks slightly different
Designer–developer communication is unclearBack-and-forth instead of building
The developer interviews, grouped by cost

The persona that came out of this research was a final-year computer science student: strong at backend work, already using Tailwind for its simplicity, but struggling to make an interface look professional on his own. He didn't need more freedom. He needed good defaults in a language he already spoke.

0408

Key Decision: Build on Tailwind, Not Around It

Competitive research showed the gap. Existing kits had big component libraries and active communities, but customisation was limited and integrating them was complicated. Most were built around pre-designed components that fight you the moment you need something different.

Tailwind takes the opposite approach, and that's why the kit is built on it.

BootstrapTailwind CSS
PhilosophyPre-designed components and layoutsLow-level utility classes
CustomisingOverride the defaultsCompose from utilities
Design valuesFixed by the frameworkTokens you define: colour, spacing, type
Why it fit TailusEvery change fights the defaultsThe kit's tokens become the code's tokens
Why the kit follows Tailwind's model

That turned into the kit's three goals: enhanced customisation through tokens, reusable and accessible components, and time saved by matching the tools developers already use.

0508

Process: From Scope to User Testing

The structure of the kit came from a card-sorting exercise: grouping components the way designers and developers actually reach for them, with stakeholders in the room. Then the work moved in one direction, with a review loop at the end.

The design process: scope, research, exploration, design system, developer collaboration, then review and testing
The design process: scope, research, exploration, design system, developer collaboration, then review and testing

The developer collaboration step was the important one. Presenting the system to developers before it was finished, and discussing feasibility early, caught problems while they were still cheap.

0608

Prototyping in Four Steps

Each stage answered a different question, and each one fed the next with stakeholder feedback.

StageQuestion it answered
Paper prototypesDoes the layout and interaction flow make sense at all?
Low-fidelity in FigmaDo the basic components work together?
High-fidelityDo the colours, type, and imagery hold up?
Clickable prototypesCan stakeholders and test users move through it like the real thing?
Eight days of prototyping, paper to clickable
0708

The Final Kit

The finished kit pairs a full Tailwind colour palette, every hue in every step, with components designed on top of it: dialogs, alerts, accordions, a date picker, and progress indicators, plus sample pages that show them composed together.

The final kit: Tailwind's full palette alongside components built from it
The final kit: Tailwind's full palette alongside components built from it

Because the palette is Tailwind's own, a colour in the design file has the same name in the code. A developer reading the mockup never has to ask which blue.

0808

Results

ResultWhere it came from
Faster design iterationThe step-by-step prototyping approach
Happier stakeholdersFeedback built in at every prototype stage
Better engagement in user testingClickable prototypes tested with real users
10% less development timeHigh-fidelity prototypes developers could build from directly
Outcomes reported in the original case study

The next step is growing the toolkit so website design gets more accessible for people who aren't designers. The full visual case study is on Behance.