Expo Native UI Builder

The skill restricts tooling to a specified Node component-listing script, with no visible credential access, covert exfiltration, or destructive default behavior. It requires user confirmation before extending with a local native module and warns about runtime crashes from platform-specific imports. Points are deducted because confirmation, data-flow, and rollback boundaries for installation commands, external documentation access, and project node_modules reads are incomplete, while provenance is mostly repository metadata.

The documentation provides a clear universal-first decision path, SDK boundaries, platform isolation rules, and failure warnings; the listing script reports errors and exits when the project path or @expo/ui is missing. Points are deducted because there are no tests or execution evidence for key paths, the script only parses type-definition exports rather than validating APIs against documentation or projects, and some import-safety guidance is complex or potentially ambiguous.

Audience, scenarios, platform-layer selection, and non-fit areas are clearly described across iOS, Android, web, Expo Router, and community-library migration. Points are deducted because finer trigger conditions and input/output formats are not specified, Chinese-language support is absent, and core references depend on Expo, Android, and Material documentation without evidence of reachability from mainland-China networks.

The skill uses a layered main document and reference files, covering installation, version compatibility, examples, limitations, type-definition precedence, and confirmation before extension. The repository provides an MIT license, a version field, and general CI maintenance checks. Points are deducted because there is no skill-specific changelog, named maintenance owner, or explicit skill-level update path; troubleshooting and FAQ coverage are limited, and external links are not revision-pinned.

The material can directly guide selection among universal components, SwiftUI, Jetpack Compose, and drop-in replacements, with reusable Host, layout, and platform-file examples, so the core task is plausibly completable. Points are deducted because static files provide no verified representative outputs or real-project results; users must still validate types and docs themselves, and comparative benefit over manual implementation is not evidenced.

The repository includes auditable skill files, reference documentation, and a component-enumeration script, while identifying installed package type definitions as the source of truth. Points are deducted because no committed key-path tests, CI execution results, or independent third-party corroboration are shown; external documentation is only referenced by links, and its current accuracy cannot be verified statically.