Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
This skill assists developers in migrating existing Expo native modules from the 1.0 definition DSL to the v2 macro API. It focuses on updating Swift implementations while preserving existing JavaScript and TypeScript contracts.
It is specifically designed for the incremental adoption of macros such as @ExpoModule, @JS, and @Event within established modules.
Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.
Follow the documented setup, then try a first task.
Claude Code — Expo Experiments
Installs: Complete separate `expo-experiments` plugin for experimental or prerelease Expo APIs; its skills may change, be renamed, or be removed between versions. · Claude Code
Before you start
Use this plugin only when deliberately working with an experimental Expo API; otherwise install the main `expo` plugin.
Enter these commands as one documented sequence inside a Claude Code session: first add the marketplace, then install the separate experimental plugin.
Replace <PROJECT_PATH> with the Expo project path.
Replace <LOCAL_OR_STANDALONE> with whether the module is app-local or reusable.
Replace <IOS_ANDROID_OR_BOTH> with the intended platforms.
Replace <NATIVE_CAPABILITY> with the native function, view, event, shared object, or system API needed.
Check the repository for this skill’s setup.
Use the expo-module skill to propose a minimal scaffold plan for a native module in my Expo project. The project is at <PROJECT_PATH>; the module should be <LOCAL_OR_STANDALONE>, target <IOS_ANDROID_OR_BOTH>, and expose <NATIVE_CAPABILITY>. Recommend only the needed scaffold features, the intended module path or slug, and the files that would be created or changed. Do not publish anything or run the scaffold yet.
Replace <WORKFLOW_NAME> with the desired workflow filename.
Replace <PROJECT_PATH> with the Expo project root.
Replace <TRIGGER> with the desired supported trigger.
Replace <JOB_GOAL> with the single CI/CD job goal.
Replace <PROFILE> with an existing eas.json build profile.
A logged-in EAS CLI session and linked Expo project are required for the documented server-side validation.
EAS Workflows consumes plan build or compute minutes if a workflow is later run; build or submission jobs can also require paid Apple or Google accounts.
Check the repository for this skill’s setup.
Use the eas-workflows skill to draft one minimal `.eas/workflows/<WORKFLOW_NAME>.yml` workflow for my Expo project at <PROJECT_PATH>. It should run on <TRIGGER> and perform <JOB_GOAL> using the existing eas.json profile <PROFILE>. Fetch the current workflow schema first, check all references and expressions, and validate the resulting file from the Expo project root. Do not trigger the workflow or deploy anything.
Claude
Codex
Cursor
Gemini CLI
Copilot
Windsurf
Amp
OpenCode
Kiro
Antigravity
Factory Droid
Cline