mobile

Implement React Native mobile screens and navigation flows with platform-specific rules.

1|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/hdtinh57/codex-orchestrated-project-template --skill mobile-hdtinh57
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mobile
Source: https://github.com/hdtinh57/codex-orchestrated-project-template/tree/main/.codex/skills/mobile
Command: npx skills add https://github.com/hdtinh57/codex-orchestrated-project-template --skill mobile-hdtinh57

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps development teams enforce consistent mobile UI patterns across screens, navigation flows, and platform-specific nuances in React Native, reducing duplication and drift.

Core Features & Use Cases

  • Screen and component scaffolding guidelines for React Native apps
  • Navigation architecture recommendations and platform decisions (Expo Managed vs Bare workflow)
  • Accessibility, performance, and styling standards to ensure quality across iOS and Android

Quick Start

Open the skill and apply the mobile guidelines to create or modify screens and navigation in your React Native project.

Frequently Asked Questions about mobile

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

FAQPage Schema
How do I structure React Native screens and navigation flows to support both iOS and Android?

Validate React Native code by running linting and tests, and ensure compliance with the project's AGENTS.md standards alongside Expo versus Bare workflow recommendations for performance and styling.

What's the best way to decide between Expo Managed and Bare workflows for React Native navigation?

Decide between Expo Managed and Bare workflows by applying the project's navigation architecture recommendations, ensuring the chosen Expo versus Bare workflow aligns with your performance and styling practices.

How do I enforce accessibility and performance standards in React Native mobile apps?

Enforce accessibility and performance standards in React Native by applying mobile UI guidelines that validate screen scaffolding and navigation architecture with linting and tests across iOS and Android.

When should I use platform-specific files for React Native mobile UI components?

Use platform-specific files for React Native mobile UI components only when platform behaviors are genuinely divergent, applying shared screen and component scaffolding guidelines otherwise to prevent drift.

Why does my React Native mobile UI drift across different screens and navigation flows?

React Native mobile UI drifts when consistent UI patterns are not enforced across screens and navigation flows; applying standardized scaffolding and platform-specific rules reduces duplication and maintains quality.