MOBILE DEVELOPMENT / expo
Expo DOM Components
Use isolated DOM components to bring selected web UI into native Expo apps.
“Use Expo DOM components to run web code in a webview on native and as-is on web. Migrate web code to native incrementally. For the end-to-end migration of a whole web app, use the expo-web-to-native skill.”
01 / THE REASONING
Why this made the selection.
- The definition separates serializable props from async native-action callbacks and documents different web and native rendering paths.
- Embed a web chart or editor while keeping navigation and surrounding controls native.
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-dom/SKILL.md
- LICENSE
- README.md
Our findings
- The definition separates serializable props from async native-action callbacks and documents different web and native rendering paths.
- 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
- Third-party instructions and helpers were not executed; service access, host compatibility and outcomes remain untested.
- 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.
DOCUMENTED COMMAND
npx skills add expo/skills/plugins/expo/skills/expo-dom 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-dom - Install the pinned directory interactively and retain its referenced files; inspect the source before granting tool access.
- Place the use-dom component in its own file, pass serializable state and explicit async actions, and test web/iOS/Android layout and interaction.
- Before any feedback submission, obtain the user’s explicit approval, review the package and any separately loaded feedback skill, and remove secrets and private project details from the report.
Before you start
- Compatible Expo project with DOM/webview support and the chosen web component dependencies
- Optional feedback needs npm/network access and a separately reviewed feedback package or skill.
04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
https://github.com/expo/skills/blob/d4f484024fec15196bfd3c272e953e3f983972cf/plugins/expo/skills/expo-dom/SKILL.md
Supports: summary, review, install, access, limitations
- Pinned LICENSE ↗Checked
https://github.com/expo/skills/blob/d4f484024fec15196bfd3c272e953e3f983972cf/LICENSE
Supports: license
- Pinned README.md ↗Checked
https://github.com/expo/skills/blob/d4f484024fec15196bfd3c272e953e3f983972cf/README.md
Supports: summary, review, install, access, limitations
https://raw.githubusercontent.com/expo/skills/d4f484024fec15196bfd3c272e953e3f983972cf/plugins/expo/skills/expo-dom/SKILL.md
Supports: upstreamDescription, review.notTested, review.reviewedAt, limitations