Provides specific version compatibility notes for NativeWind and Tailwind CSS to prevent common installation errors.
日本語の概要は準備中です。原文の説明を表示しています。
10 件 ・ 関連度順
概要と使いどころ
Provides specific version compatibility notes for NativeWind and Tailwind CSS to prevent common installation errors.
日本語の概要は準備中です。原文の説明を表示しています。
NativeWind v4+ - Tailwind CSS utility classes for React Native, className prop, CSS variables, dark mode, platform prefixes, animations, theming, third-party component integration
日本語の概要は準備中です。原文の説明を表示しています。
React NativeとExpoのアプリで、画面遷移・状態管理・データ取得を設計します。長い一覧の表示、フォーム、端末機能の利用、認証情報の保存方法も扱います。
Set up Tailwind CSS v4 in Expo with react-native-css and NativeWind v5 for universal styling
日本語の概要は準備中です。原文の説明を表示しています。
Set up Tailwind CSS v4 in Expo with react-native-css and NativeWind v5 for universal styling
日本語の概要は準備中です。原文の説明を表示しています。
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`.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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).
日本語の概要は準備中です。原文の説明を表示しています。
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`.
日本語の概要は準備中です。原文の説明を表示しています。
Set up Tailwind CSS v4 in Expo with react-native-css and NativeWind v5 for universal styling
日本語の概要は準備中です。原文の説明を表示しています。