---
title: "Expo Module Authoring: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/skills/expo-expo-module/
description: "Scaffolds an Expo native module with an explicit slug, platform and feature set, then replaces the generated sample."
---

# Expo Module Authoring: review, setup & limitations · Undominated.ai

> Scaffolds an Expo native module with an explicit slug, platform and feature set, then replaces the generated sample.

[← Explore all skills](/skills/)

NATIVE MODULES / Expo

# Expo Module Authoring

Scaffolds an Expo native module with an explicit slug, platform and feature set, then replaces the generated sample.

 [See setup guidance ↓](#setup)[Original source ↗](https://github.com/expo/skills/tree/d4f484024fec15196bfd3c272e953e3f983972cf/plugins/expo/skills/expo-module)

SOURCE REVIEW

 Reviewed 2026-10-15
 Evidence 5 linked sources
 Publisher Expo
 Licence [MIT ↗](https://github.com/expo/skills/blob/d4f484024fec15196bfd3c272e953e3f983972cf/plugins/expo/LICENSE)
 Revision d4f484024fec
 [Read what was—and wasn’t—checked ↓](#review)

“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. Use when building or modifying native modules for Expo. Not for migrating an existing Swift module from the definition DSL to the Expo Modules API 2.0 macros; use expo-migrate-module (from the expo-experiments plugin) for that.”

 [Expo · upstream description ↗](https://github.com/expo/skills/blob/d4f484024fec15196bfd3c272e953e3f983972cf/plugins/expo/skills/expo-module/SKILL.md) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - Scaffolding is delegated to create-expo-module, with local and standalone called out as different products.
- The description excludes one migration job and names the other skill that owns it.

### A good fit for

 - Creating a new Expo native module or view in Swift, Kotlin, and TypeScript
- Adding a platform to an existing Expo module with create-expo-module add-platform-support
- Add a second platform to an existing Expo native module without hand-copying project scaffolding.

### Weigh up before choosing

 - The description says not to use this skill to migrate an existing Swift module from the definition DSL to Expo Modules API 2.0 macros.
- Feature examples are opt-in, so a new scaffold can be minimal.
- Local modules do not generate index.ts unless --barrel is passed.
- This review did not execute the skill.
- Scaffolding creates examples, not a validated native implementation; API 2.0 macro migration is explicitly outside this skill.
- The feedback command resolves a mutable latest npm package and can send supplied project/error context outside the local environment. Its package implementation and the separate feedback skill were not inspected or executed; this review does not establish what additional data they collect.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - plugins/expo/skills/expo-module/SKILL.md
- plugins/expo/skills/expo-module/references/create-expo-module.md
- plugins/expo/LICENSE

### Our findings

 - The pinned skill prefers create-expo-module over hand-built native directories and points the scaffold details at references/create-expo-module.md.
- It distinguishes a local module for one app from a standalone module for reuse or publishing, and it says ViewEvent implies View.
- In non-interactive local scaffolding the positional slug or path must be passed explicitly, because --name changes the native class name rather than the folder.
- expo-module.config.json is documented with a class-name difference: iOS uses the class name, Android uses the fully qualified name.
- The guide distinguishes host-app tooling for local modules from standalone package/example apps and explains that feature examples and local barrels are opt-in.
- The final feedback section invokes submit-expo-feedback@latest with npm confirmation suppressed, sending supplied actionable context to Expo; repeated failures route to a separate expo-skill-feedback skill.

### Not established by this review

 - The skill was not executed inside a host agent.
- Not executed: it was not installed or run.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Add a skill to your workflow.

[Upstream setup instructions ↗](https://github.com/vercel-labs/skills/blob/48dc9e8eb8aa19040e91cb90ba0b642c9cbad57e/README.md)

DOCUMENTED COMMAND

 npx skills add expo/skills/plugins/expo/skills/expo-module Copy command ↗

Run in your terminal to choose your AI tools, project or global scope, and installation method. This short command follows the current upstream version; the review covers the revision shown above.

 Optional: install the reviewed revision

Keeps the original source and installer version where recorded, while leaving your AI tools and installation scope for you to choose.

 npx skills add https://github.com/expo/skills/tree/d4f484024fec15196bfd3c272e953e3f983972cf/plugins/expo/skills/expo-module Copy reviewed-revision command ↗ - The README lists expo-module and also documents a wildcard install.
- The command here pins only this skill at the reviewed commit. The installer was not executed.

### Before you start

 - Node.js and npm
- An Expo app or a place to publish a standalone module

### Compatibility

Claude Code · Codex · Cursor · GitHub Copilot · Cline

### Local project scaffolding

 - Create module files via the scaffolder
- Read and edit Swift, Kotlin, and TypeScript in the module
- Creates native source, build metadata and config plugins; plugins can modify platform project files.
- Optional feedback can download/execute an npm package, contact Expo and transmit the context supplied in the report. It can also load a separate feedback skill; review that path before granting network or execution access.

### Cost model

MIT licence; native build tools are local. No EAS account is required by this file.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Skill definition at reviewed revision ↗](https://github.com/expo/skills/blob/d4f484024fec15196bfd3c272e953e3f983972cf/plugins/expo/skills/expo-module/SKILL.md) Checked 2026-10-14 https://github.com/expo/skills/blob/d4f484024fec15196bfd3c272e953e3f983972cf/plugins/expo/skills/expo-module/SKILL.md Supports: summary, upstreamDescription, whySelected, limitations
- [Publisher README ↗](https://github.com/expo/skills/blob/d4f484024fec15196bfd3c272e953e3f983972cf/README.md) Checked 2026-10-14 https://github.com/expo/skills/blob/d4f484024fec15196bfd3c272e953e3f983972cf/README.md Supports: install, compatibility
- [Plugin MIT licence ↗](https://github.com/expo/skills/blob/d4f484024fec15196bfd3c272e953e3f983972cf/plugins/expo/LICENSE) Checked 2026-10-14 https://github.com/expo/skills/blob/d4f484024fec15196bfd3c272e953e3f983972cf/plugins/expo/LICENSE Supports: license
- [Skills installer tree URL parsing ↗](https://github.com/vercel-labs/skills/blob/7407f3893ad4dceab546ac002c3ef806e4000c73/src/source-parser.ts) Checked 2026-10-07 https://github.com/vercel-labs/skills/blob/7407f3893ad4dceab546ac002c3ef806e4000c73/src/source-parser.ts Supports: install
- [2026-10-15 C2-W45 source re-review at the existing pin ↗](https://raw.githubusercontent.com/expo/skills/d4f484024fec15196bfd3c272e953e3f983972cf/plugins/expo/skills/expo-module/SKILL.md) Checked 2026-10-15 https://raw.githubusercontent.com/expo/skills/d4f484024fec15196bfd3c272e953e3f983972cf/plugins/expo/skills/expo-module/SKILL.md Supports: upstreamDescription, review.notTested, review.reviewedAt

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### EAS Update ↗ Publishes an Expo OTA update only after the channel, environment, runtime and native-build boundary are explicit.](/skills/expo-eas-update/)[### Expo Design System ↗ Builds a token theme (color, spacing, typography, radius, shadow, motion) plus variant/size/state component conventions inside an Expo app, with grep-based drift audits and a named gallery of AI-generated-looking anti-patterns.](/skills/expo-expo-design-system/)[### Expo Web to Native Migration ↗ Migrates a web React codebase to a native Expo app screen by screen: native shell first, whole web UI shippable in DOM components on day one, then strangler-order nativization with device verification.](/skills/expo-expo-web-to-native/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Choose a toolkit](/tools/)
- [Inspect execution hosts](/agents/)
- [Check tool access](/mcp-servers/)
- [Check project dependencies](/check-repo/)
