tailwind-setup

Integrate Tailwind CSS v4 into Expo projects with NativeWind v5 and react-native-css.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/jp2507-max/growbro-cultivation-app --skill tailwind-setup-jp2507-max
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tailwind-setup
Source: https://github.com/jp2507-max/growbro-cultivation-app/tree/main/.github/skills/tailwind-setup
Command: npx skills add https://github.com/jp2507-max/growbro-cultivation-app --skill tailwind-setup-jp2507-max

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines integrating Tailwind CSS v4 into Expo projects by leveraging react-native-css and NativeWind v5 to provide a consistent, cross-platform styling workflow for iOS, Android, and Web.

Core Features & Use Cases

  • No Babel config needed: CSS-first approach that keeps Metro configuration simple.
  • Unified styling across platforms: Tailwind-powered UI components render consistently on iOS, Android, and web.
  • Step-by-step setup: Metro, PostCSS, and CSS files are configured to work together with NativeWind.
  • Use Case: A developer wants a single source of truth for design tokens and utility classes across a React Native Expo app.

Quick Start

Install Tailwind v4, NativeWind v5, and react-native-css in your Expo project, then configure metro.config.js, postcss.config.mjs, and a global CSS file. Import the CSS in your app entry and run the project to verify styles are applied.

Frequently Asked Questions about 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?

To set up Tailwind CSS v4 in an Expo project, you install Tailwind v4, NativeWind v5, and react-native-css, then configure metro.config.js, postcss.config.mjs, and a global CSS file for cross-platform styling.

Do I need to modify Babel config to use NativeWind v5 with Tailwind v4?

No Babel config is needed for NativeWind v5 with Tailwind v4. This setup uses a CSS-first approach that keeps Metro configuration simple by relying on PostCSS and global CSS files instead.

Can I use Tailwind utility classes for universal styling across iOS, Android, and web in React Native?

Yes, you can use Tailwind utility classes for universal styling across iOS, Android, and web by integrating NativeWind v5 and react-native-css into your Expo project to ensure consistent UI rendering.

What is the best way to configure Metro for NativeWind v5 and Tailwind v4?

The best way to configure Metro for NativeWind v5 is applying the provided step-by-step Metro configuration alongside PostCSS and global CSS files, ensuring the CSS-first toolchain works without Babel modifications.

Why does my Tailwind CSS not apply in my Expo React Native app after installation?

Tailwind CSS may not apply if your Metro, PostCSS, or global CSS files are misconfigured, or if the CSS file is not properly imported in your app entry point to verify styles are applied correctly.