expo-tailwind-setup
Configure Tailwind CSS for Expo
Expo teams need consistent styling across native and web targets. This skill gives a focused setup path for Tailwind CSS v4, NativeWind v5, and react-native-css.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "expo-tailwind-setup" from https://skillstore.io/skills/expo-expo-tailwind-setup.md and its manifest at https://skillstore.io/api/skills/expo-expo-tailwind-setup/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "expo-tailwind-setup". I need Tailwind CSS v4 in an Expo app that targets iOS, Android, and web.
Expected outcome:
A setup plan covering package installation, Metro configuration, PostCSS configuration, global CSS imports, and shared className wrappers.
Using "expo-tailwind-setup". My NativeWind styles are not applying after migration.
Expected outcome:
A troubleshooting checklist for CSS imports, NativeWind Metro integration, wrapped components, and TypeScript className props.
Using "expo-tailwind-setup". I want iOS semantic colors in Tailwind utilities.
Expected outcome:
Guidance for defining CSS variables, using platform media queries, and registering colors in the Tailwind theme layer.
Security Audit
SafeAll static findings were adjudicated as false positives caused by Markdown code fences, sample configuration snippets, platform CSS references, or a benign Expo platform check. No prompt injection, credential access, data exfiltration, or malicious intent was found in SKILL.md.
Risk Factors
โก Contains scripts (1)
โ๏ธ External commands (49)
๐ Network access (1)
๐ Env variables (2)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/expo-expo-tailwind-setup/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/expo-expo-tailwind-setup?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/expo-expo-tailwind-setup?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/expo-expo-tailwind-setup/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/expo-expo-tailwind-setup.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
expo. (2026). expo-tailwind-setup security audit report (audit version 5) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/expo-expo-tailwind-setup/audits/5BibTeX citation
@techreport{expo-expo-expo-tailwind-setup-2026,
author = {expo},
title = {expo-tailwind-setup security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/expo-expo-tailwind-setup/audits/5},
note = {Author version 1.0.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "expo-tailwind-setup security audit report (audit version 5)"
version: "1.0.0"
type: report
authors:
- name: "expo"
date-released: "2026-07-05"
url: "https://skillstore.io/skills/expo-expo-tailwind-setup/audits/5"
identifiers:
- type: other
value: "skillstore:expo-expo-tailwind-setup:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Set Up a New Expo App
Add Tailwind CSS v4 styling support to a new Expo project with native and web targets.
Migrate Styling Configuration
Replace older NativeWind and Tailwind configuration patterns with the CSS-first v4 approach.
Standardize Component Styling
Create shared CSS-enabled components so app screens can use className consistently.
Try These Prompts
Use this skill to list the packages and configuration files needed for Tailwind CSS v4 in my Expo project.
Apply the Expo Tailwind setup guidance to create or update my Metro config, PostCSS config, and global CSS file.
Use this skill to add reusable CSS-enabled wrappers for core React Native components in my Expo app.
Review my current Expo styling setup and use this skill to plan a migration from NativeWind v4 or Tailwind v3 to the v5 and v4 stack.
Best Practices
- Start with the Metro, PostCSS, and global CSS configuration before adding component wrappers.
- Keep CSS-enabled component wrappers in one shared directory for consistent imports.
- Test styling on iOS, Android, and web because platform media queries can resolve differently.
Avoid
- Do not keep an old NativeWind Babel preset when using the v5 Metro transformer approach.
- Do not use unwrapped React Native primitives when className support is required.
- Do not assume Tailwind v3 configuration files apply unchanged to Tailwind CSS v4.
Frequently Asked Questions
Does this skill create files automatically?
Which Tailwind version does it target?
Does it require a Babel config?
Can it support web and native platforms?
Is NativeWind v5 stable?
Can I use it with Claude, Codex, and Claude Code?
Developer Details
Author
expoLicense
MIT
Author version
v1.0.0
Skillstore revision
r1
Repository
https://github.com/expo/skills/tree/main/plugins/expo-app-design/skills/expo-tailwind-setup/Ref
30c73eac2afe762f6aa9c4553158769369d47351
Maintenance freshness
7/18/2026
Usage
6 downloads ยท 168 views
File structure
๐ SKILL.md