expo-tailwind-setup

Configures Tailwind CSS v4 in Expo projects with NativeWind and react-native-css across iOS, Android, Web.

Updated Jan 2, 2026
One-click install
npx skills add https://github.com/IlyaKukarkin/bee_bloom --skill expo-tailwind-setup-ilyakukarkin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: expo-tailwind-setup
Source: https://github.com/IlyaKukarkin/bee_bloom/tree/main/.agents/skills/expo-tailwind-setup
Command: npx skills add https://github.com/IlyaKukarkin/bee_bloom --skill expo-tailwind-setup-ilyakukarkin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Expo apps often lack a unified styling approach across iOS, Android, and Web; Tailwind CSS provides a utility-first model, but React Native requires adapters such as NativeWind and react-native-css to apply styles reliably.

Core Features & Use Cases

  • Tailwind v4 integration across Expo, NativeWind, and react-native-css: unify styling across platforms.
  • Metro + PostCSS configuration: enables CSS-first styling without Babel, simplifying builds.
  • Cross-platform UI patterns: guidelines and examples for consistent components on iOS, Android, and Web.

Quick Start

Initialize your Expo project and run the setup to configure Tailwind CSS v4 with NativeWind and react-native-css.

Frequently Asked Questions about expo-tailwind-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up Tailwind CSS in an Expo project?

To set up Tailwind CSS in an Expo project, configure Tailwind v4 with NativeWind v5 and react-native-css. This involves installing dependencies, creating a global CSS file, and updating Metro configuration to enable consistent styling across iOS, Android, and Web.

Does NativeWind v4 work with Tailwind CSS v4 in Expo?

NativeWind v5 is required to work with Tailwind CSS v4 in Expo. This setup uses react-native-css to apply styles reliably across platforms without needing a Babel configuration, simplifying the build pipeline.

How do I configure Metro for NativeWind without Babel?

Configuring Metro for NativeWind without Babel requires updating the Metro configuration to integrate a PostCSS pipeline. This CSS-first styling approach uses react-native-css to process the global CSS file and apply styles universally.

Why do I need react-native-css for Expo Tailwind styling?

You need react-native-css for Expo Tailwind styling because React Native requires adapters to apply web-style CSS utility classes reliably. It bridges Tailwind CSS v4 with NativeWind v5 to ensure consistent UI rendering across iOS, Android, and Web.

Can I use className-driven styling across iOS, Android, and Web in Expo?

Yes, you can achieve className-driven styling across iOS, Android, and Web in Expo. By unifying Tailwind CSS v4 with NativeWind and react-native-css, this configuration enables a utility-first styling model across all platforms without requiring Babel.