Theming overview
Understand how the default whisk/ui theme, token vocabulary, and application overrides fit together.
Theme model
Whisk/UI uses a default theme for shared tokens and components. Applications can extend the theme at one explicit boundary.
Theme provider
Provide the theme once near the application root so components share color mode and theme context. Generated CSS owns token values; the provider synchronizes the active theme scope.
tsx
<ThemeProvider theme={theme} themeMode="light">
<App />
</ThemeProvider>Customization layers
- Use default Whisk/UI tokens first.
- Add semantic application tokens second.
- Use component recipes for repeated product patterns.
- Keep global CSS and host-specific CSS at the boundary.
Recommended workflow
Start with a visual token decision, give it a semantic name, use it in a component or recipe, then document the exception if it is product-specific.