rn-platform-specific

Bridge platform-specific behavior in React Native apps using Platform.OS and file extensions.

9|1|Updated Jun 16, 2026
One-click install
npx skills add https://github.com/AratKruglik/antigravity-sdlc --skill rn-platform-specific
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rn-platform-specific
Source: https://github.com/AratKruglik/antigravity-sdlc/tree/main/plugins/react-native-plugin/skills/rn-platform-specific
Command: npx skills add https://github.com/AratKruglik/antigravity-sdlc --skill rn-platform-specific

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Platform-specific differences in React Native apps create code duplication and maintenance burden when supporting iOS and Android.

Core Features & Use Cases

  • Platform.OS and Platform.select enable conditional UI and logic without forking components.
  • File extension-based overrides like .ios.tsx and .android.tsx facilitate true platform-specific components.
  • Native module integration (Expo or autolinking) simplifies access to device features across platforms.
  • Manage permissions, safe areas, and status bar to ensure consistent UX across devices.

Quick Start

Create platform-specific branches using Platform.OS and Platform.select, and provide .ios.tsx/.android.tsx overrides to minimize cross-platform duplication.

Frequently Asked Questions about rn-platform-specific

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I handle platform-specific behavior in React Native for iOS and Android?

Handle platform-specific behavior in React Native using Platform.OS and Platform.select to branch UI and logic, or use .ios.tsx and .android.tsx file extensions to create true platform-specific components.

What's the best way to manage iOS and Android permissions in React Native?

Manage permissions in React Native by bridging platform-specific code paths using native module integration with Expo or autolinking to access device features safely across iOS and Android.

When should I use file extension-based overrides like .ios.tsx in React Native?

Use file extension-based overrides like .ios.tsx and .android.tsx in React Native when you need true platform-specific components to minimize cross-platform code duplication and maintenance burden.

Does Platform.select work with native modules for safe-area handling?

Platform.select handles cross-platform UI logic, while native module integration via Expo or autolinking manages safe-area handling and device features to ensure consistent UX across devices.

Can I use Expo or autolinking to integrate native modules for iOS and Android code paths?

Yes, integrate native modules using Expo or autolinking to bridge platform-specific behavior and simplify access to device features across iOS and Android code paths in React Native apps.