Cross-platform interfaces
Build responsive screens, navigation, forms, lists, gestures, states, themes, and accessible controls.
Codex Skills for React Native give Codex structured instructions for building cross-platform screens, navigation, state, native integrations, tests, performance improvements, and release-ready Android and iOS changes. Download the skills for React Native projects that need shared product logic without ignoring platform behavior.
task: complete react native development task
inspect:
- requirements and context
- existing standards
- failure and edge cases
verify: outputs + checks + handoffStrong react native development work depends on context, explicit decisions, and checks that match the real environment.
These skills give Codex a specialist workflow for react native development while preserving local conventions, important constraints, and human review.
Build responsive screens, navigation, forms, lists, gestures, states, themes, and accessible controls.
Follow existing state management, networking, caching, persistence, authentication, deep links, and error boundaries.
Configure permissions, notifications, files, cameras, maps, app links, native modules, pods, Gradle, and platform code.
Write component and integration tests, profile rendering, optimize lists and images, and verify Android and iOS builds.
The steps keep context, implementation, and verification visible so the result can be reviewed and repeated.
Read React Native version, architecture, dependencies, navigation, state, native projects, build variants, and tests.
Define data ownership, screen lifecycle, permissions, platform branches, offline behavior, and service boundaries.
Reuse components, keep state predictable, isolate native modules, add accessibility, and handle failures.
Run JavaScript checks, component tests, critical flows, Android and iOS builds, performance profiles, and release checks.
The workflow adjusts to the project, audience, tools, and risk while preserving the same quality standard.
Share product features while respecting platform UI, lifecycle, permissions, builds, and distribution.
Connect platform SDKs, modules, notifications, deep links, files, media, maps, and device capabilities.
Manage APIs, caching, offline state, authentication, synchronization, errors, and persistence.
Upgrade React Native, dependencies, native build tools, signing boundaries, and store-ready artifacts.
Start with one defined outcome and provide the source material, constraints, and checks that matter.
These skills are designed for people who need dependable react native development work with a visible process.
Build features, debug native boundaries, test behavior, improve performance, and maintain releases.
Use shared code while preserving platform quality, accessibility, and release discipline.
Learn the native constraints behind React components, navigation, permissions, and device APIs.
Upgrade frameworks, modules, build systems, architecture, tests, and platform requirements safely.
The skills assist mobile development, but real-device testing, credentials, signing, privacy declarations, store requirements, and native SDK behavior need authorized review.
Install the complete skill folder and add the project-specific context before beginning.
Keep SKILL.md with the included react native development guidance, checks, and supporting files.
Use project scope for local rules and versions, or personal scope for a reusable workflow.
Document the tools, audience, standards, source material, constraints, and approval rules for this react native development work.
Provide the intended outcome, important edge cases, required checks, and expected handoff.
Practical answers about capabilities, limits, setup, and review.
Yes. The workflow checks shared behavior and target-specific code, configuration, permissions, and builds.
Yes, when the project uses Expo. Managed and prebuild workflows have different native boundaries.
Yes. They can integrate or build modules when the native projects and SDK requirements are available.
They can profile renders, lists, images, JavaScript work, native bridges, startup, memory, and interaction responsiveness.
They can prepare builds and check requirements, but submission needs authorized accounts, signing, metadata, and human approval.
Clear context. Purposeful work. Relevant checks. A result others can understand.