expo-tailwind-setup

Automate Tailwind CSS v4 setup in Expo apps with NativeWind and PostCSS.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configuring Tailwind CSS v4 for Expo projects across iOS, Android, and Web, including integration with react-native-css and NativeWind, can be tedious and error-prone.

Core Features & Use Cases

  • Tailwind CSS v4 integration for Expo projects
  • Metro + NativeWind setup for unified styling across platforms
  • PostCSS & global CSS configuration to enable theme variables and platform-specific rules
  • Use Case: A developer wants a single styling system across web and native targets with consistent design tokens.

Quick Start

Follow the setup guide to configure Tailwind CSS v4 with Expo using 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 v4 in an Expo project?

Configuring Tailwind CSS v4 with Expo requires setting up the NativeWind Metro transformer, adding a PostCSS plugin for CSS-first configuration, and wrapping your app with a global CSS provider.

Does NativeWind work with Tailwind CSS v4 for cross-platform React Native styling?

Yes, NativeWind integrates with Tailwind CSS v4 to enable unified styling across iOS, Android, and Web by leveraging react-native-css and configuring the Metro transformer.

What is the best way to configure platform-specific CSS variables in Expo?

Using NativeWind with react-native-css provides a CSS-first configuration approach through PostCSS, enabling consistent design tokens and platform-specific CSS variables across iOS, Android, and Web.

Why do I need PostCSS when integrating Tailwind in an Expo app?

PostCSS is required to enable CSS-first configuration for Tailwind v4, allowing the NativeWind Metro transformer to properly process global CSS, theme variables, and platform-specific styling rules.

Can I use a single styling system for both web and native Expo targets?

Yes, integrating NativeWind and react-native-css with Tailwind v4 provides a single styling system across web and native Expo targets, ensuring consistent design tokens via global CSS wrappers.