tutti-ui-system

# Tutti UI System Use this skill as the single entrypoint for `@tutti-os/ui-system` component reuse, extraction, promotion, metadata, and storyboard work. ## Non-Negotiable Standard Any UI promoted into `@tutti-os/ui-system` must fully follow the UI-system design standard before it can be reported as complete. Treat these as hard requirements, not cleanup suggestions: - use UI-system semantic tokens and existing shared CSS variables; do not leave raw `hex`, `rgb(...)`, `rgba(...)`, ad hoc gradients, or app-local palette values in promoted components or their storyboard examples unless the source of truth already exposes them as approved tokens - compose existing UI-system `base` primitives such as `Card`, `Button`, `Tooltip`, `Dialog`, and related vocabulary before creating custom panel, button, field, or overlay treatments - use icon components from `@tutti-os/ui-system/icons` for promoted components and storyboard examples. Do not inline SVG/data URI assets, import app-local icon files, or pull third-party icon packages directly from promoted UI. If the source UI depends on an icon that is not in the UI system, promote the source-derived icon into `packages/ui/system/src/icons` with metadata first, then consume the UI-system icon export. - make storyboard examples render the real component surface and states; do not rely on surrounding docs chrome to hide component-level visual drift or to fake the final panel/surface language - when a consumer ...