Set up Tuturuuu UI
Install and wire the shared package for product apps, then follow the contributor workflow when the library changes.
Public package setup
Use the package from product apps by installing the shared package, loading global CSS once, and importing components by subpath.
Install packages
Install `@tuturuuu/ui` and `@tuturuuu/icons` with the owning app package manager.
Load global styles
Import `@tuturuuu/ui/globals.css` once at the app root so tokens and base styles are available.
Use subpath imports
Import components from public subpaths such as `@tuturuuu/ui/button`.
Use theme tokens
Use existing design tokens and dynamic color utilities instead of hard-coded hue classes.
bun add @tuturuuu/ui @tuturuuu/icons
import '@tuturuuu/ui/globals.css';Package imports
Import every primitive from its public subpath. Keep workspace apps behind the same package boundary as external consumers.
import { Button } from '@tuturuuu/ui/button';
import { Dialog, DialogContent } from '@tuturuuu/ui/dialog';
import { Search } from '@tuturuuu/icons';Contributor setup
Internal maintainers should update the docs route, registry, messages, and tests together.
Add metadata
Add component docs metadata in the category split that owns the component.
Add preview coverage
Use a live preview for safe primitives and a pattern preview for complex app shells.
Verify exports
Check the package export map before documenting a new public import path.
Add tests
Update integrity tests, route render tests, and focused preview tests before final checks.
bun --cwd apps/web test 'src/app/[locale]/ui/component-docs.test.ts'
bun --cwd apps/web type-check