When components are in your repo, theming stops being a configuration file in a dependency and becomes something you own end to end. Liminal UI is styled with Tailwind and maps colors to semantic tokens (background, foreground, primary, and so on) so you can reshape the whole UI from one place.
Start from tokens
Most surfaces use CSS variables defined on :root (and .dark if you use class-based dark mode). Tailwind maps those variables in tailwind.config or your theme extension. That means:
- Change a token once and every component that references it updates.
- Add modes (high contrast, brand variants) by swapping variable sets, not by patching node_modules.
Why this fits copy-paste components
Because you edit the component files directly, you can introduce new utility classes, extend the theme, or fork a single component without waiting for a library release. The CLI gives you a starting point; your design system is the source of truth.
Practical workflow
- Define or adjust semantic colors in your global CSS.
- Mirror them in Tailwind theme extensions if you use custom keys.
- Use
classNameoverrides on specific instances when you need one-off tweaks.
For installation and CLI usage, see the introduction. For accessibility foundations, read building accessible components.