Native UI
v1.0.0Building native mobile UIs with Expo Router and React Native. Covers routing, navigation, styling, native controls, animations, and platform conventions following Apple Human Interface Guidelines.
⭐ 0· 946·4 current·4 all-time
by@wpank
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name/description (native UI with Expo Router) match the included files (route, tabs, animations, media, WebGPU references). The skill declares no environment variables, binaries, or installs — appropriate for a documentation/instruction-only skill.
Instruction Scope
SKILL.md and reference files contain code snippets and developer guidance (expo start, custom builds, Metro config, package installs, permission flows). All referenced actions are coherent with building native UIs. The instructions do not direct the agent to read unrelated system files, exfiltrate secrets, or call external endpoints beyond standard package registries and Expo tooling. (Note: some snippets recommend installing npm packages or changing project config — expected for this domain.)
Install Mechanism
There is no install spec and no code files that would be written/executed by the platform — the skill is instruction-only, which is the lowest-risk install mechanism.
Credentials
The skill declares no environment variables, credentials, or config-path requirements. The content references app-level storage (SecureStore/SQLite/media) and permission APIs for camera/microphone which are appropriate for a UI/mobile guidance package; nothing requests unrelated secrets or host credentials.
Persistence & Privilege
always is false and the skill is user-invocable; disable-model-invocation is false (normal). The skill does not request permanent platform presence or elevated agent privileges.
Assessment
This skill appears to be a coherent, instruction-only guide for Expo Router and React Native UI patterns. Before using it in a project: (1) Verify the origin — the package lists no homepage and the source is unknown, so prefer content from a known repo or vendor. (2) Review and test any config changes (metro.config.js, package installs) in a sandboxed branch; some snippets contain minor inaccuracies (nonstandard commands like `npx add`, RN style props that may not be supported) and pinned dependency instructions that could break your build. (3) Do not run arbitrary install scripts or copy & paste commands that download code from unknown URLs without inspecting them. (4) If you plan to adopt native modules or change build tooling, audit third-party packages (versions and licenses) and confirm permissions (camera/microphone/media) are requested and handled correctly in your app.Like a lobster shell, security has layers — review code before you run it.
latestvk979vprhrk6kkcgzq9w3f3n7h980x4nk
License
MIT-0
Free to use, modify, and redistribute. No attribution required.