Domains
Forms
Mechanism
Breaks down how the skill works and what it produces, so you can quickly judge whether it fits your scenario and value.
When a user has an existing native iOS/Android app and wants to embed Expo/React Native (brownfield), mentions AAR/XCFramework, or adding Expo to Kotlin/Swift projects.
User selects a suitable integration approach and gets guided steps to embed RN into their native app with correct tooling and version pinning.
Use Cases
An Android team maintains a Kotlin app and wants to add a React Native feature without giving the native team Node tooling. Using this skill, they choose the isolated approach, build an AAR with Expo, and consume it as a library. The native team stays in their existing workflow while shipping new RN screens from a separate repo.
A single product team owns both Swift and RN code for an iOS app and wants hot reload in one build. Using this skill they pick the integrated approach, add Expo to CocoaPods, and get seamless JS source maps. They unify release cadence and avoid maintaining a separate RN repo.
Skill Relationships
Dependency relationships read as "the upper tier points to the lower tier." The current Skill sits in the middle tier — above are Skills that depend on it, below are Skills it depends on.
Tier 1 · These Skills Use Me
Tier 2 · Current Skill
Tier 3 · I Use These Skills
Browse this skill's relationships within its skillset. Click a node to switch the side panel; use the search box to jump to any skill.
Skill File
