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 an existing Apple/Swift Expo native module needs migration from the Expo Modules API 1.0 DSL to the 2.0 macro API (@ExpoModule, @JS, etc.) while keeping its JS/TS contract unchanged.
A migrated Swift module using 2.0 macros with unchanged JS API, a clear handoff of remaining DSL items, and tracked gaps via GitHub issues.
Use Cases
A library author maintains an Expo module written with the 1.0 definition DSL. They want to adopt the 2.0 macro API for cleaner Swift code but cannot change the JS surface consumed by users. Using this skill, they inventory the contract, migrate group by group with mixed mode, and verify via tests. Result: modernized native code with zero breaking changes for downstream apps.
A team finds a specific 2.0 macro unsupported in their expo-modules-core version mid-migration. The skill classifies it as Blocked, asks to co-exist in DSL or revert, and files a tracked gh issue on expo/expo. This prevents forced broken code and records the gap, letting the rest of the module migrate cleanly while the limitation is visible to all.
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
