Back to Expo & Mobile

expo-tailwind-setup

ExpoTailwind CSS v4React NativeNativeWindCSS-in-JSUniversal StylingFrontendMobile Development
2.1k📄 MIT🕒 2026-06-16Source ↗

Install this skill

npx skills add expo/skills

Works across Claude Code, Cursor, Codex, Copilot & Antigravity

This skill implements the architecture for Tailwind CSS v4 within an Expo project using NativeWind v5 and react-native-css. Unlike earlier iterations that relied heavily on Babel plugins, this method shifts configuration to PostCSS and the Metro bundler. It requires the manual creation of styled-component wrappers to bridge standard React Native primitives with CSS class names. By defining global CSS variables and specific media queries for Android and iOS font rendering, developers gain control over visual styles across platforms. The setup eliminates the need for legacy Babel presets, focusing on a leaner integration with modern Expo standards. You must wrap standard primitives like View, Text, and Pressable with the useCssElement hook to enable className-based styling in your application codebase.

When to Use This Skill

  • Modernizing an existing Expo project to use Tailwind v4
  • Building cross-platform mobile apps with a single shared CSS theme
  • Managing platform-specific font family tokens via global CSS
  • Migrating away from legacy NativeWind Babel-based configurations

How to Invoke This Skill

Example prompts that trigger this skill in Claude Code, Cursor, or Antigravity:

  • How do I set up Tailwind v4 in Expo?
  • Configure NativeWind v5 for a new Expo app
  • How to use react-native-css with Tailwind
  • Replace Babel config for Tailwind in Expo
  • Create CSS wrapper components for NativeWind

Pro Tips

  • 💡Leverage `tailwind-merge` and `clsx` for dynamic class concatenation, preventing style conflicts and improving readability in components with conditional styling.
  • 💡Explore NativeWind's theming capabilities to define consistent design tokens (colors, spacing, fonts) that seamlessly integrate with Tailwind's utility classes and custom variants.
  • 💡Familiarize yourself with `react-native-css`'s runtime features and debugging tools for advanced styling scenarios or when incorporating custom CSS properties not directly covered by Tailwind utilities.

What this skill does

  • Integrates Tailwind CSS v4 via the @tailwindcss/postcss plugin
  • Configures Metro with the withNativewind transformer
  • Maps standard React Native components to CSS-enabled wrappers
  • Provides platform-aware CSS variable support for fonts
  • Eliminates Babel configuration dependencies for styling

When not to use it

  • Projects requiring simple StyleSheet objects without CSS class overhead
  • Applications targeting very old Expo SDK versions that conflict with lightningcss
  • Teams avoiding extra wrapper components for standard primitives

Example workflow

  1. Install the necessary dependencies including tailwindcss v4 and react-native-css
  2. Update metro.config.js to wrap the config with withNativewind
  3. Create the postcss.config.mjs file to load the Tailwind plugin
  4. Define platform-specific font variables in a global CSS file
  5. Implement the wrapper components in a central directory like src/tw/
  6. Import your custom wrapped components to apply className props

Prerequisites

  • Expo SDK environment
  • Basic familiarity with PostCSS configuration
  • Node.js environment

Pitfalls & limitations

  • !Failing to wrap standard components in custom CSS-enabled files results in className being ignored
  • !Conflicting legacy Babel presets will break the build process
  • !Incorrectly configuring the Metro transformer will cause runtime stylesheet failures

FAQ

Do I still need a babel.config.js file?
No. Tailwind v4 and NativeWind v5 remove the requirement for Babel-based styling configurations.
Why must I wrap components like View and Text?
The react-native-css integration requires an explicit hook call to map classNames to native styles, which necessitates these wrappers.
Is autoprefixer required for this setup?
No, it is excluded because modern Expo environments utilize lightningcss for automatic vendor prefixing.
How does this handle web support?
The setup works across platforms, though specific CSS variable access might differ between web and mobile environments via the useCSSVariable hook.

How it compares

This approach replaces brittle Babel-based transforms with a native PostCSS pipeline, offering better compatibility with the latest Expo Metro bundler standards.

Source & trust

2.1k stars📄 MIT🕒 Updated 2026-06-16
📄 Full skill instructions — original source: expo/skills
# Tailwind CSS Setup for Expo with react-native-css

This guide covers setting up Tailwind CSS v4 in Expo using react-native-css and NativeWind v5 for universal styling across iOS, Android, and Web.

## Overview

This setup uses:

- **Tailwind CSS v4** - Modern CSS-first configuration
- **react-native-css** - CSS runtime for React Native
- **NativeWind v5** - Metro transformer for Tailwind in React Native
- **@tailwindcss/postcss** - PostCSS plugin for Tailwind v4

## Installation

# Install dependencies
npx expo install tailwindcss@^4 [email protected] [email protected] @tailwindcss/postcss tailwind-merge clsx


Add resolutions for lightningcss compatibility:

// package.json
{
"resolutions": {
"lightningcss": "1.30.1"
}
}


- autoprefixer is not needed in Expo because of lightningcss
- postcss is included in expo by default

## Configuration Files

### Metro Config

Create or update metro.config.js:

// metro.config.js
const { getDefaultConfig } = require("expo/metro-config");
const { withNativewind } = require("nativewind/metro");

/** @type {import('expo/metro-config').MetroConfig} */
const config = getDefaultConfig(__dirname);

module.exports = withNativewind(config, {
// inline variables break PlatformColor in CSS variables
inlineVariables: false,
// We add className support manually
globalClassNamePolyfill: false,
});


### PostCSS Config

Create postcss.config.mjs:

// postcss.config.mjs
export default {
plugins: {
"@tailwindcss/postcss": {},
},
};


### Global CSS

Create src/global.css:

@import "tailwindcss/theme.css" layer(theme);
@import "tailwindcss/preflight.css" layer(base);
@import "tailwindcss/utilities.css";

/* Platform-specific font families */
@media android {
:root {
--font-mono: monospace;
--font-rounded: normal;
--font-serif: serif;
--font-sans: normal;
}
}

@media ios {
:root {
--font-mono: ui-monospace;
--font-serif: ui-serif;
--font-sans: system-ui;
--font-rounded: ui-rounded;
}
}


## IMPORTANT: No Babel Config Needed

With Tailwind v4 and NativeWind v5, you do NOT need a babel.config.js for Tailwind. Remove any NativeWind babel presets if present:

// DELETE babel.config.js if it only contains NativeWind config
// The following is NO LONGER needed:
// module.exports = function (api) {
// api.cache(true);
// return {
// presets: [
// ["babel-preset-expo", { jsxImportSource: "nativewind" }],
// "nativewind/babel",
// ],
// };
// };


## CSS Component Wrappers

Since react-native-css requires explicit CSS element wrapping, create reusable components:

### Main Components (src/tw/index.tsx)

import {
useCssElement,
useNativeVariable as useFunctionalVariable,
} from "react-native-css";

import { Link as RouterLink } from "expo-router";
import Animated from "react-native-reanimated";
import React from "react";
import {
View as RNView,
Text as RNText,
Pressable as RNPressable,
ScrollView as RNScrollView,
TouchableHighlight as RNTouchableHighlight,
TextInput as RNTextInput,
StyleSheet,
} from "react-native";

// CSS-enabled Link
export const Link = (
props: React.ComponentProps<typeof RouterLink> & { className?: string }
) => {
return useCssElement(RouterLink, props, { className: "style" });
};

Link.Trigger = RouterLink.Trigger;
Link.Menu = RouterLink.Menu;
Link.MenuAction = RouterLink.MenuAction;
Link.Preview = RouterLink.Preview;

// CSS Variable hook
export const useCSSVariable =
process.env.EXPO_OS !== "web"
? useFunctionalVariable
: (variable: string) => var(${variable});

// View
export type ViewProps = React.ComponentProps<typeof RNView> & {
className?: string;
};

export const View = (props: ViewProps) => {
return useCssElement(RNView, props, { className: "style" });
};
View.displayName = "CSS(View)";

// Text
export const Text = (
props: React.ComponentProps<typeof RNText> & { className?: string }
) => {
return useCssElement(RNText, props, { className: "style" });
};
Text.displayName = "CSS(Text)";

// ScrollView
export const ScrollView = (
props: React.ComponentProps<typeof RNScrollView> & {
className?: string;
contentContainerClassName?: string;
}
) => {
return useCssElement(RNScrollView, props, {
className: "style",
contentContainerClassName: "contentContainerStyle",
});
};
ScrollView.displayName = "CSS(ScrollView)";

// Pressable
export const Pressable = (
props: React.ComponentProps<typeof RNPressable> & { className?: string }
) => {
return useCssElement(RNPressable, props, { className: "style" });
};
Pressable.displayName = "CSS(Pressable)";

// TextInput
export const TextInput = (
props: React.ComponentProps<typeof RNTextInput> & { className?: string }
) => {
return useCssElement(RNTextInput, props, { className: "style" });
};
TextInput.displayName = "CSS(TextInput)";

// AnimatedScrollView
export const AnimatedScrollView = (
props: React.ComponentProps<typeof Animated.ScrollView> & {
className?: string;
contentClassName?: string;
contentContainerClassName?: string;
}
) => {
return useCssElement(Animated.ScrollView, props, {
className: "style",
contentClassName: "contentContainerStyle",
contentContainerClassName: "contentContainerStyle",
});
};

// TouchableHighlight with underlayColor extraction
function XXTouchableHighlight(
props: React.ComponentProps<typeof RNTouchableHighlight>
) {
const { underlayColor, ...style } = StyleSheet.flatten(props.style) || {};
return (
<RNTouchableHighlight
underlayColor={underlayColor}
{...props}
style={style}
/>
);
}

export const TouchableHighlight = (
props: React.ComponentProps<typeof RNTouchableHighlight>
) => {
return useCssElement(XXTouchableHighlight, props, { className: "style" });
};
TouchableHighlight.displayName = "CSS(TouchableHighlight)";


### Image Component (src/tw/image.tsx)

import { useCssElement } from "react-native-css";
import React from "react";
import { StyleSheet } from "react-native";
import Animated from "react-native-reanimated";
import { Image as RNImage } from "expo-image";

const AnimatedExpoImage = Animated.createAnimatedComponent(RNImage);

export type ImageProps = React.ComponentProps<typeof Image>;

function CSSImage(props: React.ComponentProps<typeof AnimatedExpoImage>) {
// @ts-expect-error: Remap objectFit style to contentFit property
const { objectFit, objectPosition, ...style } =
StyleSheet.flatten(props.style) || {};

return (
<AnimatedExpoImage
contentFit={objectFit}
contentPosition={objectPosition}
{...props}
source={
typeof props.source === "string" ? { uri: props.source } : props.source
}
// @ts-expect-error: Style is remapped above
style={style}
/>
);
}

export const Image = (
props: React.ComponentProps<typeof CSSImage> & { className?: string }
) => {
return useCssElement(CSSImage, props, { className: "style" });
};

Image.displayName = "CSS(Image)";


### Animated Components (src/tw/animated.tsx)

import * as TW from "./index";
import RNAnimated from "react-native-reanimated";

export const Animated = {
...RNAnimated,
View: RNAnimated.createAnimatedComponent(TW.View),
};


## Usage

Import CSS-wrapped components from your tw directory:

import { View, Text, ScrollView, Image } from "@/tw";

export default function MyScreen() {
return (
<ScrollView className="flex-1 bg-white">
<View className="p-4 gap-4">
<Text className="text-xl font-bold text-gray-900">Hello Tailwind!</Text>
<Image
className="w-full h-48 rounded-lg object-cover"
source={{ uri: "https://example.com/image.jpg" }}
/>
</View>
</ScrollView>
);
}


## Custom Theme Variables

Add custom theme variables in your global.css using @theme:

@layer theme {
@theme {
/* Custom fonts */
--font-rounded: "SF Pro Rounded", sans-serif;

/* Custom line heights */
--text-xs--line-height: calc(1em / 0.75);
--text-sm--line-height: calc(1.25em / 0.875);
--text-base--line-height: calc(1.5em / 1);

/* Custom leading scales */
--leading-tight: 1.25em;
--leading-snug: 1.375em;
--leading-normal: 1.5em;
}
}


## Platform-Specific Styles

Use platform media queries for platform-specific styling:

@media ios {
:root {
--font-sans: system-ui;
--font-rounded: ui-rounded;
}
}

@media android {
:root {
--font-sans: normal;
--font-rounded: normal;
}
}


## Apple System Colors with CSS Variables

Create a CSS file for Apple semantic colors:

/* src/css/sf.css */
@layer base {
html {
color-scheme: light;
}
}

:root {
/* Accent colors with light/dark mode */
--sf-blue: light-dark(rgb(0 122 255), rgb(10 132 255));
--sf-green: light-dark(rgb(52 199 89), rgb(48 209 89));
--sf-red: light-dark(rgb(255 59 48), rgb(255 69 58));

/* Gray scales */
--sf-gray: light-dark(rgb(142 142 147), rgb(142 142 147));
--sf-gray-2: light-dark(rgb(174 174 178), rgb(99 99 102));

/* Text colors */
--sf-text: light-dark(rgb(0 0 0), rgb(255 255 255));
--sf-text-2: light-dark(rgb(60 60 67 / 0.6), rgb(235 235 245 / 0.6));

/* Background colors */
--sf-bg: light-dark(rgb(255 255 255), rgb(0 0 0));
--sf-bg-2: light-dark(rgb(242 242 247), rgb(28 28 30));
}

/* iOS native colors via platformColor */
@media ios {
:root {
--sf-blue: platformColor(systemBlue);
--sf-green: platformColor(systemGreen);
--sf-red: platformColor(systemRed);
--sf-gray: platformColor(systemGray);
--sf-text: platformColor(label);
--sf-text-2: platformColor(secondaryLabel);
--sf-bg: platformColor(systemBackground);
--sf-bg-2: platformColor(secondarySystemBackground);
}
}

/* Register as Tailwind theme colors */
@layer theme {
@theme {
--color-sf-blue: var(--sf-blue);
--color-sf-green: var(--sf-green);
--color-sf-red: var(--sf-red);
--color-sf-gray: var(--sf-gray);
--color-sf-text: var(--sf-text);
--color-sf-text-2: var(--sf-text-2);
--color-sf-bg: var(--sf-bg);
--color-sf-bg-2: var(--sf-bg-2);
}
}


Then use in components:

<Text className="text-sf-text">Primary text</Text>
<Text className="text-sf-text-2">Secondary text</Text>
<View className="bg-sf-bg">...</View>


## Using CSS Variables in JavaScript

Use the useCSSVariable hook:

import { useCSSVariable } from "@/tw";

function MyComponent() {
const blue = useCSSVariable("--sf-blue");

return <View style={{ borderColor: blue }} />;
}


## Key Differences from NativeWind v4 / Tailwind v3

1. **No babel.config.js** - Configuration is now CSS-first
2. **PostCSS plugin** - Uses @tailwindcss/postcss instead of tailwindcss
3. **CSS imports** - Use @import "tailwindcss/..." instead of @tailwind directives
4. **Theme config** - Use @theme in CSS instead of tailwind.config.js
5. **Component wrappers** - Must wrap components with useCssElement for className support
6. **Metro config** - Use withNativewind with different options (inlineVariables: false)

## Troubleshooting

### Styles not applying

1. Ensure you have the CSS file imported in your app entry
2. Check that components are wrapped with useCssElement
3. Verify Metro config has withNativewind applied

### Platform colors not working

1. Use platformColor() in @media ios blocks
2. Fall back to light-dark() for web/Android

### TypeScript errors

Add className to component props:

type Props = React.ComponentProps<typeof RNView> & { className?: string };

How to Use This Skill Unit

Option A: Project-Specific (Recommended)

  1. Click "Download" above
  2. In your project, create the directory: .agent/skills/expo-tailwind-setup/
  3. Save the file as SKILL.md
  4. The agent will automatically discover the skill based on its description.

Option B: Global Installation (All Agents)

Save the file to these locations to make it available across all projects:

  • Claude Code: ~/.claude/skills/expo/skills/expo-tailwind-setup/SKILL.md
  • Cursor: ~/.cursor/skills/expo/skills/expo-tailwind-setup/SKILL.md
  • Antigravity: ~/.gemini/antigravity/skills/expo/skills/expo-tailwind-setup/SKILL.md

🚀 Install with CLI:
npx skills add expo/skills

Read the Master Guide: Mastering Agent Skills

Recommended Rules

View more rules

Recommended Workflows

View more workflows

Recommended MCP Servers

View more MCP servers

Take It Further

Maximize your productivity with these powerful resources

📋

Define Your Standards

Set up coding standards to ensure this workflow produces consistent, high-quality results.

Browse Rules Library
📖

Master Workflows

Learn how to create custom workflows, use Turbo Mode, and build your automation library.

Complete Guide

How to use this Skill in Claude Code & Cursor

For Claude Code (CLI)

To use this skill in Claude Code, copy the rule content into your project's custom instructions or follow our Add-Skill CLI guide. This ensures Claude follows your standards during every code generation.

For Cursor & Windsurf

For Cursor or Windsurf, individual skills are best used in the "Rules for AI" section. This specific unit helps the agent avoid expo & mobile issues, leading to cleaner, more efficient code.

Why the skill format matters: the standardized Agent Skills format lets your AI agent load detailed instructions only when they are relevant, keeping your prompt clean while improving results.

Source & attribution

This skill is categorized under Expo & Mobile and is published by Expo Team, maintained in expo/skills.

← Browse All Agent Skills
Sponsored AI assistant. Recommendations may be paid.