expo-tailwind-setup
Set up Tailwind CSS v4 in Expo with react-native-css and NativeWind v5 for universal styling
77
66%
Does it follow best practices?
Impact
100%
4.54xAverage score across 3 eval scenarios
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./plugins/expo/skills/expo-tailwind-setup/SKILL.mdThe canonical home for this skill is expo-tailwind-setup in administrakt0r/AI-Agents-Safe-Coding-Skills
Evaluation results
100%
80%Apple System Color Theming for Cross-Platform Expo App
Platform theming and CSS variables
platformColor in @media ios
0%
100%
light-dark() fallback
0%
100%
@theme inside @layer theme
0%
100%
--color- prefix for Tailwind
0%
100%
@media android fonts
0%
100%
@media ios fonts
0%
100%
No tailwind.config.js
100%
100%
@import not @tailwind
100%
100%
useCSSVariable in component
0%
100%
Semantic color Tailwind classes used
100%
100%
100%
67%React Native Component Library with Tailwind className Support
CSS component wrappers
useCssElement import
0%
100%
className to style mapping
50%
100%
ScrollView dual prop mapping
0%
100%
AnimatedScrollView contentClassName
0%
100%
TouchableHighlight underlayColor
30%
100%
Image objectFit remap
70%
100%
Image objectPosition remap
70%
100%
Animated.View wrapper
30%
100%
Link static members
80%
100%
useCSSVariable platform check
0%
100%
Component displayNames
0%
100%
100%
85%Tailwind CSS Integration for Cross-Platform Expo App
Tailwind config file setup
lightningcss resolution
0%
100%
No autoprefixer
0%
100%
No separate postcss install
100%
100%
NativeWind version
0%
100%
react-native-css version
0%
100%
inlineVariables false
0%
100%
globalClassNamePolyfill false
0%
100%
PostCSS file is .mjs
0%
100%
PostCSS uses @tailwindcss/postcss
0%
100%
CSS @import syntax
0%
100%
No NativeWind babel config
100%
100%
Platform font @media blocks
0%
100%
- Repository
- openai/plugins
- Commit
d416fd5
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.