SKILL

react-native-architecture

Production-ready patterns for React Native development with Expo, including navigation, state management, native modules, and offline-first architecture.

Target: Mobile development. Automatically collected · unverified.

Excerpt from the author’s documentation

Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.

Read the original English text

Topics in the source

  • React Native Architecture
  • Use this skill when
  • Do not use this skill when
  • Instructions
  • Resources

Production-ready patterns for React Native development with Expo, including navigation, state management, native modules, and offline-first architecture. Starting a new React Native or Expo project Implementing complex navigation patterns Integrating native modules and platform APIs Building offline-first mobile applications Optimizing React Native performance Setting up CI/CD for mobile releases The task is unrelated to react native architecture You need a different domain or tool outside this scope Clarify goals, constraints, and required inputs. Apply relevant best practices and validate outcomes. Provide actionable steps and verification. If detailed examples are required, open resources/implementation-playbook.md. resources/implementation-playbook.md for detailed patterns and examples.

Source repository
davila7/claude-code-templates
Source file
cli-tool/components/skills/web-development/react-native-architecture/SKILL.md
Fixed revision
21be197f100a12b8d0dd9a211cc244c8179f84d3
Read the complete original documentation ↗

Sources and evidence

This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.

Author: davila7/claude-code-templates · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-09T15:01:40.859Z.

Categories are inferred from names, descriptions and paths. They do not establish compatibility.

License and attribution

MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.

Original license ↗

Synchronization, copying and user-reported success do not mark a resource as runtime-tested.

Limitations and notes

  • Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.