Total 50,320 skills, Mobile Development has 1530 skills
Showing 12 of 1530 skills
Kotlin Coroutines and Flow patterns for structured concurrency, error handling, and async operations.
Choose and implement iOS architecture patterns (MVVM, TCA, Clean Architecture) based on feature complexity. Use when designing architecture for new features or refactoring existing code.
Implements push notifications across iOS, Android, and web using Firebase Cloud Messaging and native services. Use when adding notification capabilities, handling background messages, or setting up notification channels.
Build, test, and manage Xcode projects and Swift packages. Use when the user mentions Xcode, iOS/macOS app development, simulators, Swift packages, or needs to build/test Apple platform apps. Triggers on "build", "run", "test", "simulator", "xcodebuild", "swift package", "iOS app", "macOS app".
M3-compliant UI components (buttons, cards, forms, inputs). USE WHEN: creating components <300 lines, M3 migrations, Design System work. NOT FOR: complete screens, features with business logic (use flutter-developer). Always validate M3 components with MCP tools before creating custom. Examples: <example> Context: Need to migrate a button component to M3. user: "Migrate BukeerButton to Material Design 3" assistant: "I'll use flutter-ui-components to migrate BukeerButton to M3." <commentary>UI component migration is flutter-ui-components specialty.</commentary> </example> <example> Context: Create a new reusable form field. user: "Create a new date picker input component following M3" assistant: "I'll use flutter-ui-components to create the M3-compliant date picker." <commentary>Single UI components should be handled by flutter-ui-components.</commentary> </example>
React Native with Expo framework for building native mobile apps on Android, iOS, and web from a single TypeScript codebase. Covers Expo Router file-based navigation (stack, tabs, drawer), EAS Build/Submit/Update for CI/CD and OTA updates, expo-dev-client for custom development builds, Expo Modules API for native Swift/Kotlin modules, core RN patterns (StyleSheet, FlatList, Platform-specific code), native device APIs (camera, notifications, haptics), and NativeWind for Tailwind CSS styling. Use when building React Native apps with Expo, configuring Expo Router navigation, setting up EAS Build pipelines, implementing OTA updates, creating native modules, or integrating device APIs like camera and push notifications.
Apple FoundationModels framework for on-device LLM — text generation, guided generation with @Generable, tool calling, and snapshot streaming in iOS 26+.
Explore and browse available ShipSwift recipes. Use when the user says "explore", "browse", "show recipes", "list components", "what's available", or wants to discover what ShipSwift offers.
SwiftUI best practices, pitfalls, and modern APIs. Invoke when user asks SwiftUI UI, state, navigation, lists, sheets, performance, or accessibility help.
Uniwind (Tailwind CSS v4 for React Native) best practices, setup, theming, styling, and HeroUI Native integration. Use when writing, reviewing, or fixing Uniwind code. Triggers on: uniwind, className on RN components, global.css with @import 'uniwind', withUniwindConfig, metro.config.js setup, dark:/light: theming, platform selectors (ios:/android:/native:/web:), data selectors, responsive breakpoints, CSS variables, useUniwind, withUniwind, useResolveClassNames, useCSSVariable, tailwind-variants, HeroUI Native with Uniwind, Uniwind Pro (animations, shadow tree, transitions), NativeWind migration. Also triggers on setup troubleshooting: "check my config", "styles not working", "className not applying", "audit Uniwind setup".
PHPicker, PhotosPicker, photo selection, limited library access, presentLimitedLibraryPicker, save to camera roll, PHPhotoLibrary, PHAssetCreationRequest, Transferable, PhotosPickerItem, photo permissions
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.