Skip to main content
UI Guides

Search rules

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

formsTailwind

Use tailwind-merge

MUST

MUST: Use tailwind-merge for components accepting className props to ensure override classes win

Use tailwind-merge for intelligent class conflict resolution

Bad

Good

Why it matters

When combining base component styles with variant or override classes, tailwind-merge ensures the last conflicting class wins. This is essential for reusable components that accept className props.

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.