What problem does it solve? Setting up gluestack-ui v5 requires coordinating Tailwind CSS v4's CSS-first configuration, a styling engine (NativeWind v5 or UniWind), Metro, PostCSS, and Babel, and mistakes like keeping a legacy tailwind.config.js or mispinning lightningcss cause build failures. ## Core Features & Use Cases - CLI-guided setup: Initialize projects with npx gluestack-ui@latest init, add individual or all components, and migrate from v4 using the @alpha tag. - Manual NativeWind v5 path: Provides exact package versions, the lightningcss 1.30.1 pin, global.css theme tokens, postcss.config.js, and metro.config.js for Expo and React Native CLI. - Manual UniWind path: A simpler Expo-only setup without PostCSS, including UniWind-specific global.css selectors, metro config, and Uniwind.setTheme() theme switching. - Use Case: A developer starting a new Expo app runs the CLI init, picks NativeWind v5, copies the provided global.css and config files, and gets a working themed component library without guessing version compatibility. ## Quick Start Ask the assistant to set up gluestack-ui v5 in your Expo project using the recommended CLI and NativeWind v5 styling engine.