cross-platform
Cross-platform development guidelines and best practices for the mobile-dev team
What this skill does
# Cross-Platform Development Guidelines ## React Native Development - Use React Native 0.72+ with modern features - Use functional components with Hooks - Use TypeScript for type safety - Implement proper navigation with React Navigation - Use Redux, MobX, or Zustand for state management - Follow React Native best practices - Use Expo for rapid prototyping when appropriate ## Flutter Development - Use Flutter 3.16+ with Dart 3.0+ - Use StatefulWidget and StatelessWidget appropriately - Use Provider, Riverpod, or Bloc for state management - Implement proper navigation with Navigator 2.0 - Follow Flutter best practices and widget composition - Use Flutter DevTools for debugging - Leverage pub.dev for packages ## Cross-Platform Architecture Patterns - **MVVM**: Use with reactive state management - **BLoC Pattern**: Use with Flutter for business logic - **Clean Architecture**: Separate layers properly - **Repository Pattern**: Abstract data sources - Implement proper dependency injection - Separate business logic from UI code - Use shared code for business logic ## Native Module Integration - Create native modules for platform-specific features - Use React Native Native Modules for iOS/Android - Use Flutter Platform Channels for native communication - Implement proper error handling across platforms - Maintain consistent APIs across platforms - Use platform-specific optimizations when needed - Document native module interfaces ## Cross-Platform State Management - **React Native**: Redux, MobX, Zustand, Context API - **Flutter**: Provider, Riverpod, Bloc, GetX - Implement proper state persistence - Use immutable state patterns - Handle async operations properly - Use middleware for side effects - Implement proper state hydration ## Cross-Platform Navigation - **React Native**: React Navigation (Stack, Tab, Drawer) - **Flutter**: Navigator 2.0, GoRouter, AutoRoute - Implement deep linking properly - Handle back button behavior correctly - Use type-safe navigation when possible - Implement proper route guards - Handle navigation state persistence ## Performance Optimization for Cross-Platform Apps - Use React Native Hermes for JavaScript engine - Use Flutter's performance best practices - Implement proper list virtualization - Optimize image loading and caching - Use code splitting and lazy loading - Profile performance with platform tools - Reduce bundle size with tree shaking - Use efficient data structures ## Platform-Specific Code Handling - Use platform-specific file extensions (.ios.tsx, .android.tsx) - Use conditional platform checks (Platform.OS, Theme.of) - Implement platform-specific UI components - Handle platform-specific permissions correctly - Use platform-specific APIs when needed - Maintain consistent behavior across platforms - Document platform-specific differences
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.