What problem does it solve? Styling components in a design system that ships to both web and React Native is error-prone: developers mix up platform mechanisms (Tailwind classes on RN files, useStyleSheet on web files), use raw values instead of design tokens, or break consumer style overrides with wrong merge order. This Skill enforces the correct styling conventions for each platform before code is written or reviewed. ## Core Features & Use Cases - Platform routing: Detects whether the touched file belongs to libs/ui-react or libs/ui-rnative and loads the matching styling reference (Tailwind + cva + cn for web, useStyleSheet + themeJS + lx for React Native). - Design token enforcement: Ensures colors, typography, spacing, and sizes come from the Lumen design system tokens rather than raw Tailwind palette classes or hardcoded literals. - Review checklist: Provides diff-verifiable checks such as dynamic classname concatenation, wrong data-attribute selectors for Base UI vs Radix primitives, and incorrect style merge order on React Native. - Use Case: When adding a new Button variant in libs/ui-react, load this Skill to declare the variant in cva with token-based classes instead of inline conditional strings. ## Quick Start Ask the assistant to style a new component in libs/ui-react or libs/ui-rnative following the Lumen component-styling conventions.