Loading...
Loading...
Found 12 Skills
Expo React Native JavaScript best practices for clean code, functional components, performance optimization, and Expo Router navigation.
Expert in Expo React Native TypeScript mobile development with best practices
Comprehensive Expo React Native feature development guide. This skill should be used when building mobile app screens, navigation, data fetching, authentication, deep linking, or native UX patterns with Expo. Triggers on tasks involving Expo Router, React Native components, mobile forms, or app configuration.
Expo React Native performance optimization guidelines. This skill should be used when writing, reviewing, or refactoring Expo React Native code to ensure optimal performance patterns. Triggers on tasks involving React Native components, lists, animations, images, or performance improvements.
Diagnose, improve, and prevent performance regressions in Expo-based React Native apps using release-build profiling, KPI budgets, and targeted fixes across startup, rendering, lists, images, memory, and networking.
Airbnb-DLS-aligned design system engineering for Expo / React Native apps targeting both web and native iOS, built on Unistyles v3, Reanimated, Skia, and FlashList. Use whenever building, reviewing, or refactoring shared UI — design tokens, theming, variant-driven component APIs, typography, spacing, cross-platform web/iOS parity, native-feel performance, or complex surfaces like calendars and drawing canvases (examples use a clinic app). Covers token architecture, theming, component API contracts (variants over style props), web/iOS parity (Unistyles `_web` hover/focus/cursor, Platform splits, one shared theme), the Unistyles styling engine, and governance. Trigger even when the user does not say "design system" but is creating or changing reusable React Native components, tokens, theme code, or making a component behave natively on both web and iOS. Teaches how to BUILD the design system; pair with expo-react-native-coder for features and expo-ios-hig for iOS native-feel decisions.
Expo React Native performance optimization guidelines. This skill should be used when writing, reviewing, or refactoring Expo React Native code to ensure optimal performance patterns. Triggers on tasks involving React Native components, navigation, lists, images, animations, bundle optimization, or mobile performance improvements.
Sets up and uses NativeWind v4 (Tailwind CSS v3) in Expo React Native apps, including Expo Router. Configures tailwind.config.js, global.css, babel.config.js (jsxImportSource + nativewind/babel), metro.config.js (withNativeWind + input), and app.json (web bundler metro). Troubleshoots “className not applying”, Tailwind CLI compilation, and Metro cache issues. Implements reusable components/variants, dark mode + theming via CSS variables (vars/useColorScheme), and third-party component styling (remapProps/cssInterop). Use when working on Expo projects using NativeWind v4, Tailwind-style className utilities, or when debugging NativeWind configuration.
Use when setting up Wallet UI in a new or existing Expo application. Guides selection between modern @solana/kit (Recommended) or legacy @solana/web3.js.
Autonomous mobile dev subagent that implements a single user story from a PRD for Expo / React Native apps. Use when you need parallel, independent mobile implementation tasks — screens, native components, data fetching, navigation. Designed to run alongside other ralph-mobile instances. Receives a specific task ID and PRD path. Returns a structured completion signal. Does NOT commit or modify the PRD — those are handled by the documenter. Loads expo, building-native-ui, vercel-react-native-skills, native-data-fetching, and expo-dev-client skills automatically.
Verify and fix Android release signing for any Expo/React Native build. Use when Play Console rejects an upload with "signed in debug mode", when a CI-built APK/AAB needs its signer certificate checked, when a release-signing config plugin seems to inject signing wrong, or when jarsigner vs apksigner verification is needed. Not project-specific.
Build an Expo React Native Android APK on GitHub Actions without EAS. Use when the user wants to build an APK/AAB from CI, set up a GitHub Actions workflow for expo prebuild + gradle assembleRelease, fix Android build failures in CI (Kotlin metadata mismatch, play-services-ads version conflicts, RNGMA/patch-package), download the APK artifact, or asks why the Android build fails with "incompatible version of Kotlin". Covers APK (release-signed via keystore, or debug-signed for quick tests) vs AAB (Play Store) choices and native dependency pinning. For signing/verify specifics (Play Console debug-mode rejections, apksigner vs jarsigner) see the android-release-signing skill.