skills / expo / skills / building-native-ui
Building Native UI
Current Expo UI agent skill source for native-feeling screens with Apple HIG styling, semantic colors, native controls, SF Symbols, media, animations, visual effects, gradients, storage, and responsive layout.
Source description: Build beautiful, native-feeling Expo screens. Covers Apple HIG styling, semantic colors, native controls, SF Symbols, media, animations, visual effects, gradien...
Need the building-native-ui install command?
Copy the npx command below to install this OpenClaw skill. This page also includes the original SKILL.md source, required permissions, verification notes, rollback triggers, and common setup fixes.
npx skills add https://github.com/expo/skills --skill building-native-uiOn this page
Our added value (verification layer)
This page is not only a source mirror. We add reproducibility, risk controls, and operations guidance on top of the original skill definition.
- Execution/Security/Maintainability scoring with explicit criteria
- Compatibility matrix across runtime environments
- Verification log with check commands and observed outcomes
- Common failure fixes and rollback triggers for production safety
Overall score
85/100
Execution
88
Security
80
Maintainability
86
Install the Building Native UI skill
Install the exact Expo source, then verify the installed file and OpenClaw path before treating the skill as ready.
npx skills add https://github.com/expo/skills --skill building-native-uiVerify the installed source path
npx -y skills add https://github.com/expo/skills --skill building-native-ui -y -gtest -f ~/.agents/skills/building-native-ui/SKILL.mdreadlink ~/.openclaw/skills/building-native-ui
- The current v1.1.0 source focuses on native-feeling Expo screen UI and delegates routing/navigation to the expo-router skill.
- The installer reported a PromptScript global-install limitation separately; this does not mean the verified OpenClaw path failed.
- This verification cycle confirmed install/source/path integrity but did not execute a new end-to-end Expo UI behavior task.
SKILL.md (source preview)
Short preview shown here to keep this page focused on our verification layer.
Expo UI Guidelines For routes, links, stacks, tabs, modals, sheets, and headers, use the expo router skill. References Consult these resources as needed: Running the App CRITICAL: Always try Expo Go first before creating custom builds. Most Expo apps work in Expo Go without any custom native code. Before running npx expo run:ios or npx expo run:android : 1. Start with Expo Go : Run npx expo start and scan the QR code with Expo Go 2. Check if features work : Test your app thor...
Required permissions
file
Compatibility matrix
| Environment | Status | Notes |
|---|---|---|
| Skills CLI global install | pass | Canonical installer command completed on 2026-07-06 and refreshed the current Expo source. |
| OpenClaw skill path | pass | Verified ~/.openclaw/skills/building-native-ui resolves to the installed universal source. |
| End-to-end Expo UI behavior task | partial | Current source was inspected and synced; no new end-to-end Expo screen implementation run was executed in this verification cycle. |
Verification log
Canonical install command executed
npx -y skills add https://github.com/expo/skills --skill building-native-ui -y -g
result: pass
Canonical source exists locally
test -f ~/.agents/skills/building-native-ui/SKILL.md
result: pass
OpenClaw skill path resolves to installed source
readlink ~/.openclaw/skills/building-native-ui
result: pass
Current imported body equals canonical body
compare data/verifiedSources/buildingNativeUi.ts decoded body with ~/.agents/skills/building-native-ui/SKILL.md after frontmatter removal
result: pass
End-to-end Expo UI behavior task
not executed in this verification cycle
result: partial
Security notes
- Review third-party UI libraries before adding to production dependencies.
- Validate permissions for media/device APIs when implementing native controls.
- Run mobile QA across devices to prevent gesture/navigation regressions.
Common failures and fixes
Routing or navigation guidance appears missing from the current skill
Use the expo-router skill for routes, links, stacks, tabs, modals, sheets, and headers as directed by the current source.
Installed source still shows the older broad Expo Router scope
Reinstall from the canonical expo/skills repository and compare the current v1.1.0 frontmatter/body before debugging behavior.
PromptScript reports global installation unsupported
Scope the warning to PromptScript and verify the OpenClaw symlink separately instead of treating it as an OpenClaw install failure.
Quick FAQ
How do I install this skill quickly?
Use the exact Skills CLI command shown above, then verify ~/.agents/skills/building-native-ui/SKILL.md and the OpenClaw skill path. The current source is v1.1.0 and delegates routing/navigation to expo-router.
What should I check before production rollout?
Confirm permissions, run a non-destructive dry run, and review rollback triggers.
What if install succeeds but actions do not run?
First verify the canonical Expo source file and OpenClaw symlink. Treat any PromptScript global-install warning as runtime-specific rather than an OpenClaw failure, and use expo-router for routing/navigation tasks.
Recent changes
- 2026-07-06: Refreshed the canonical Expo source to v1.1.0 and synced the exact current source body.
- 2026-07-06: Updated scope to native-feeling Expo screen UI and recorded the explicit expo-router handoff for routing/navigation.
- 2026-07-06: Replaced broad compatibility claims and generic restart/dry-run guidance with observed install/path evidence and Partial behavior status.
- 2026-02-15: Added hot-skill page entry from competitor ranking gap analysis.
Rollback triggers
- New UI architecture introduces navigation regressions in production.
- Animation changes degrade performance on target low-end devices.
- Platform QA flags accessibility or safe-area handling regressions.
Known issues
Current v1.1.0 source delegates routing and navigation to expo-router
Use this skill for native-feeling screen UI and invoke expo-router separately for route/navigation work.
Installer reports a PromptScript global-install limitation
Do not generalize that warning to OpenClaw; verify the OpenClaw symlink and runtime independently.
No end-to-end Expo UI behavior task was executed in this verification cycle
Run a project-specific screen implementation and target-device check before claiming behavior success.
Related tutorials
Site references
- Source repository
- Original path: /expo/skills/building-native-ui
- License: check source repository
- Fetched/verified: 2026-07-06
- Third-party source summary with added verification and security notes.
- Alternative: frontend-react-best-practices
- Alternative: webapp-testing