What problem does it solve? Setting up Tailwind CSS v4 in an Expo React Native project involves many breaking changes from NativeWind v4, including new Metro and PostCSS configs, CSS-first theming, and the removal of Babel presets. This Skill provides the exact configuration steps and component wrappers needed to get universal styling working across iOS, Android, and Web. ## Core Features & Use Cases - Complete configuration guide: Covers Metro config with withNativewind, PostCSS with @tailwindcss/postcss, and global.css with Tailwind v4 imports. - CSS component wrappers: Provides ready-to-use View, Text, ScrollView, Pressable, Image, and Animated components wrapped with useCssElement for className support. - Platform-specific theming: Shows how to use @media ios/android queries, platformColor(), light-dark(), and @theme variables for Apple system colors and custom fonts. - Use Case: You are starting a new Expo app in a monorepo and want Tailwind utility classes like className="flex-1 bg-white p-4" to work on native and web without maintaining separate style objects. ## Quick Start Set up Tailwind CSS v4 with NativeWind v5 in my Expo app, including the Metro config, global.css, and CSS-wrapped components.