Agent skill · software engineering · sickn33
expo-module
Guide for creating and writing Expo native modules and views using the Expo Modules API (Swift, Kotlin, TypeScript). Covers module definition DSL, native views, shared objects, config plugins, lifecycle hooks, autolinking, and type system.
Why this skill is useful
Provides detailed guidance on creating and managing Expo native modules, including specific commands and configurations not commonly known.
What it needs
Requires expo-cli installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Writing Expo Modules Complete reference for building native modules and views using the Expo Modules API. Covers Swift (iOS), Kotlin (Android), and TypeScript. When to Use Creating a new Expo native module or native view Adding native functionality (camera, sensors, system APIs) to an Expo app Wrapping platform SDKs for React Native consumption Building config plugins that modify native project files Adding Android, Apple, or web support to an existing Expo module Editing expo-module.config.json, config plugins, or lifecycle hooks References Consult these resources as needed: Quick Start Prefer create-expo-module over manually creating native module files and directories. In practice, the best path is usually to create the scaffold first and then build on top of it. The scaffold sets up the expected layout, expo-module.config.json, podspec or Gradle files, TypeScript bindings, and the standalone example app flow. If an existing Expo module only needs another platform, use create-expo-module add-platform-support instead of manually copying native directories. See references/create-expo-module.md before scaffolding or extending a module. It covers: local vs standalone modules --platform, --features, --barrel, --package-manager, and non-interactive mode expo.autolinking.nativeModulesDir add-platform-support behavior and quirks Recommended Workflow 1. Choose the scaffold type first: Local module for one app Standalone module for reuse, monorepos, or publishing 2. Determine native expo-module features that you will need. Based on the user's instructions determine which feature scaffolding will be useful. Available features: Constant, Function, AsyncFunction, Event, View, ViewEvent, SharedObject 3. Scaffold deliberately: pass an explicit slug or path choose --platform intentionally instead of relying on defaults use --features to choose code samples which you will modify in the next step to match the real implementation. 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/expo-module