10 skills · sorted by relevance
Set up Tailwind CSS v4 in Expo using react-native-css and NativeWind v5. Configure styling across iOS, Android, and Web, create components that accept CSS class names, and define shared themes with platform-specific fonts and colors.
Provides specific version compatibility notes for NativeWind and Tailwind CSS to prevent common installation errors.
The English summary is being prepared. Showing the original description.
NativeWind v4+ - Tailwind CSS utility classes for React Native, className prop, CSS variables, dark mode, platform prefixes, animations, theming, third-party component integration
The English summary is being prepared. Showing the original description.
Build React Native and Expo screens with guidance on navigation, state management, and data fetching. Apply patterns for long lists, validated forms, device features, and secure token storage when developing or reviewing mobile apps.
Set up Tailwind CSS v4 in Expo with react-native-css and NativeWind v5 for universal styling
The English summary is being prepared. Showing the original description.
Expo's official example projects - the expo/examples repo of ~70 `with-*` integrations (Stripe, Clerk, Supabase, OpenAI, maps, Reanimated, SQLite, Skia, NativeWind, and more). Use when integrating a third-party library or service into an existing Expo app and you want the canonical, version-matched pattern to adapt, or when scaffolding a new project from one with `npx create-expo --example`.
The English summary is being prepared. Showing the original description.
Build and maintain a design system inside an Expo app - a reusable theme of design tokens (color, spacing, typography, radius, shadow, motion), reusable component structure with variant/size/state prop conventions, and rules for when to extract a repeated view into a shared component. Use when creating or organizing theme files and design tokens (theme.ts / theme/), extending an existing theme or styling library (NativeWind, Tamagui, Restyle, Unistyles) in its own idiom, standardizing styles so screens (including AI-generated ones) look consistent and polished, fixing an app that looks AI-generated or generic instead of native (the named native-slop tells), building an in-app component library, or auditing an app for design-system drift (hardcoded colors, spacing, fonts). For platform styling specifics (semantic colors, HIG rules, native controls) use expo-native-ui; for folder layout of a new app use expo-project-structure.
The English summary is being prepared. Showing the original description.
React Native project structure, Expo vs bare workflow detection, app.json/app.config.js patterns, asset handling, fonts, styling approaches, hot-reload-friendly idioms. Use this skill to: - Detect Expo (managed/dev-client/EAS/ejected) vs bare RN workflow. - Pick correct project layout for each workflow. - Configure app.json / app.config.js with bundle ID, splash, icons, deep link schemes. - Handle assets, fonts, images correctly. - Pick a styling approach (StyleSheet / NativeWind / restyle / styled-components). Do NOT use this skill for: - Platform-specific branching (see rn-platform-specific). - Navigation (see rn-navigation). - Storage (see rn-state-and-storage). - Testing (see rn-testing).
The English summary is being prepared. Showing the original description.
Expo's official example projects — the expo/examples repo of ~70 `with-*` integrations (Stripe, Clerk, Supabase, OpenAI, maps, Reanimated, SQLite, Skia, NativeWind, and more). Use when integrating a third-party library or service into an existing Expo app and you want the canonical, version-matched pattern to adapt, or when scaffolding a new project from one with `npx create-expo --example`.
The English summary is being prepared. Showing the original description.
Set up Tailwind CSS v4 in Expo with react-native-css and NativeWind v5 for universal styling
The English summary is being prepared. Showing the original description.