Skip to main content
UI Guides

Search rules

Search all UI Guides rules by name, category, or source

interactionsTailwind

Class Precedence

SHOULD

SHOULD: Use tailwind-merge (via cn()) to handle class conflicts in dynamic composition

Understand Tailwind's class order and override patterns

Bad

Good

Why it matters

When combining classes dynamically, the last class in CSS source order wins (not the last class you write). Use tailwind-merge to intelligently merge Tailwind classes and resolve conflicts.

References

Built by Gleb Stroganov, design engineer at Evil Martians.

The rules come from other people's skills and guidelines — Vercel, Rauno Freiberg, @Ibelick, impeccable, Emil Kowalski, Tailwind, RAMS — each one credited on the Sources page. The work here is extraction and wiring: every rule is pulled into one corpus, given a good and a bad example you can operate, a MUST/SHOULD/NEVER rule an agent can paste, and a link back to where it came from.