novahiz 0.2.2 → 0.2.5

package/bundled-skills/expo-skill-feedback/scripts/skill-event.cjs

@@ -1,180 +0,0 @@
-#!/usr/bin/env node
-// Submit a `skill_invoked` event to PostHog — fire-and-forget.
-//
-// Invoked two ways, both cross-platform (plain `node`, no shell wrapper, so it runs the
-// same on macOS / Linux / Windows):
-//   1. From Claude Code hooks (../../../hooks/hooks.json) as
-//      `node skill-event.cjs --skill auto --initiator <ai|user> --plugin-root <dir> --detach --quiet`.
-//      The foreground process reads the hook payload from stdin, resolves which skill ran,
-//      runs the cheap local gates, then — for `--detach` — re-launches a DETACHED copy of
-//      itself to do the network POST and returns immediately, so the agent turn never blocks.
-//   2. Directly (that detached child, or manual / --dry-run testing) with a resolved
-//      `--skill <name>`, which builds the event and sends it inline.
-
-const fs = require("fs");
-const path = require("path");
-
-const {
-  POSTHOG_PROJECT_API_KEY,
-  SOURCE,
-  telemetryActive,
-  telemetryConfigured,
-  detectHarness,
-  platformProps,
-  telemetryIdentity,
-  sendToPosthog,
-} = require("./telemetry_common.cjs");
-
-const EVENT = "skill_invoked";
-
-function parseArgs(argv) {
-  const args = { skill: "", agentHarness: "", initiator: "", pluginRoot: "", dryRun: false, quiet: false, detach: false };
-  for (let i = 0; i < argv.length; i++) {
-    const flag = argv[i];
-    const next = () => argv[++i] || "";
-    switch (flag) {
-      case "--skill": args.skill = next(); break;
-      case "--agent-harness": args.agentHarness = next(); break;
-      case "--initiator": args.initiator = next(); break;
-      case "--plugin-root": args.pluginRoot = next(); break;
-      case "--detach": args.detach = true; break;
-      case "--dry-run": args.dryRun = true; break;
-      case "--quiet": args.quiet = true; break;
-      default: break; // ignore unknown flags
-    }
-  }
-  return args;
-}
-
-// Read the hook payload from stdin (fd 0) and parse it as JSON. Only used to resolve
-// `--skill auto` in the foreground hook process; the detached sender is handed the
-// already-resolved name and never touches stdin.
-function readHookInput() {
-  try {
-    if (process.stdin.isTTY) return {};
-    const raw = (fs.readFileSync(0, "utf8") || "").trim(); // fd 0 = stdin
-    if (!raw) return {};
-    const parsed = JSON.parse(raw);
-    return parsed && typeof parsed === "object" && !Array.isArray(parsed) ? parsed : {};
-  } catch {
-    return {};
-  }
-}
-
-// Resolve the invoked skill name from the hook payload. The name arrives in different
-// fields across payload shapes, so check every plausible location:
-//   - Claude Code Skill tool:        tool_input.skill        (e.g. "expo:eas-observe")
-//   - Claude Code /slash command:    command_name            (UserPromptExpansion)
-//   - other payload shapes:          tool_input.skill_name, top-level skill / skill_name
-// Namespaced names must be OURS: "expo:<skill>" keeps the final segment, any other
-// namespace is dropped — another plugin's "foo:expo-ui" must not count as ours, and
-// skillBelongsToPlugin() can't tell name collisions apart. Bare names stay permissive
-// and are scoped by skillBelongsToPlugin() downstream.
-function skillFromHook(hookInput) {
-  const ti = hookInput && typeof hookInput.tool_input === "object" && hookInput.tool_input ? hookInput.tool_input : {};
-  const raw = String(
-    ti.skill || ti.skill_name || hookInput.command_name || hookInput.skill || hookInput.skill_name || ""
-  ).trim().replace(/^\//, ""); // tolerate a leading "/" from slash-command payloads
-  if (!raw.includes(":")) return raw;
-  const sep = raw.lastIndexOf(":");
-  return raw.slice(0, sep) === "expo" ? raw.slice(sep + 1) : "";
-}
-
-function pluginRootFor(args) {
-  // Self-derive from this script's location: <root>/skills/expo-skill-feedback/scripts.
-  return args.pluginRoot || path.resolve(__dirname, "..", "..", "..");
-}
-
-// Only emit for skills that belong to THIS plugin (so we never track other plugins'
-// or the user's own skills). Confirms <pluginRoot>/skills/<skill>/SKILL.md exists.
-// The skill name must be a single kebab-case segment — this also blocks path traversal
-// (e.g. "../../x") from a malformed payload reaching path.join or the event property.
-function skillBelongsToPlugin(skill, pluginRoot) {
-  if (!skill || !pluginRoot) return false;
-  if (!/^[a-z0-9][a-z0-9-]*$/.test(skill)) return false;
-  try { return fs.existsSync(path.join(pluginRoot, "skills", skill, "SKILL.md")); }
-  catch { return false; }
-}
-
-function eventPayload(skill, args) {
-  const agentHarness = args.agentHarness.trim() || detectHarness();
-  const initiator = args.initiator.trim();
-  const timestamp = new Date().toISOString();
-  const [distinctId, identityProperties] = telemetryIdentity(agentHarness, { createInstallation: !args.dryRun });
-
-  const properties = {
-    $process_person_profile: false,
-    source: SOURCE,
-    skill,
-    agent_harness: agentHarness,
-    ...(initiator ? { initiator } : {}),
-    ...platformProps(),
-    ...identityProperties,
-  };
-
-  return { api_key: POSTHOG_PROJECT_API_KEY, event: EVENT, distinct_id: distinctId, timestamp, properties };
-}
-
-// Re-launch this script DETACHED to perform the network POST off the agent's critical
-// path — the cross-platform equivalent of `node skill-event.cjs … &`. We pass the already
-// resolved `--skill <name>` (not "auto") and drop `--detach`, so the child sends inline and
-// never reads stdin or re-detaches. It runs under the same runtime that launched us
-// (process.execPath = node or bun) and inherits our env (CLAUDECODE, EXPO_SKILLS_*, …).
-// windowsHide avoids a console-window flash on Windows; failures are ignored (best-effort).
-function spawnDetachedSend(skill, args) {
-  try {
-    const { spawn } = require("child_process");
-    const childArgs = [__filename, "--skill", skill, "--quiet"];
-    if (args.initiator.trim()) childArgs.push("--initiator", args.initiator.trim());
-    if (args.agentHarness.trim()) childArgs.push("--agent-harness", args.agentHarness.trim());
-    const child = spawn(process.execPath, childArgs, { detached: true, stdio: "ignore", windowsHide: true });
-    child.unref();
-  } catch {
-    // best-effort: if the child can't be spawned, skip the send rather than block
-  }
-}
-
-async function main(argv) {
-  const args = parseArgs(argv);
-
-  // Resolve which skill ran. `--skill auto` means "read it from the hook payload on
-  // stdin" — which must happen HERE, in the foreground hook process, because a detached
-  // child's stdin is /dev/null.
-  let skill = args.skill.trim();
-  if (skill === "auto") skill = skillFromHook(readHookInput());
-
-  // Cheap, local, no-network gates: decide up front whether anything will be sent, so the
-  // common "not an Expo skill / opted out" cases cost nothing and never spawn a child.
-  if (!skill) return 0;                                            // not a skill invocation
-  if (!args.dryRun && !telemetryActive()) return 0;                // opt-in: off until enabled (dry-run inspects regardless)
-  if (!telemetryConfigured() && !args.dryRun) return 0;            // no key in this build (e.g. a fork) -> inert
-  if (!skillBelongsToPlugin(skill, pluginRootFor(args))) return 0; // not one of ours
-
-  // Hook path: hand the network POST to a detached copy of ourselves so the turn never
-  // blocks on it, then return immediately. (--dry-run stays inline so it can be inspected.)
-  if (args.detach && !args.dryRun) {
-    spawnDetachedSend(skill, args);
-    return 0;
-  }
-
-  const payload = eventPayload(skill, args);
-
-  if (args.dryRun) {
-    console.log(JSON.stringify({ ...payload, api_key: "phc_..." }, null, 2));
-    return 0;
-  }
-
-  try {
-    await sendToPosthog(payload, { userAgent: "expo-skills/skill-event", timeoutMs: 3000 });
-  } catch (err) {
-    if (!args.quiet) console.error(`skill-event: ${err.message}`);
-    return args.quiet ? 0 : 1;
-  }
-
-  if (!args.quiet) console.log(`sent ${EVENT}: ${payload.properties.skill} (${payload.properties.initiator || "?"})`);
-  return 0;
-}
-
-main(process.argv.slice(2))
-  .then((code) => process.exit(code))
-  .catch(() => process.exit(0));

package/bundled-skills/expo-skill-feedback/scripts/telemetry.cjs

@@ -1,65 +0,0 @@
-#!/usr/bin/env node
-// Turn Expo skills usage telemetry on or off, or check its status.
-//
-// Telemetry is OFF by default (opt-in) — nothing is sent until you enable it here or
-// via EXPO_SKILLS_TELEMETRY=1. Usage:
-//   node telemetry.cjs --status   # show whether telemetry is on/off and why
-//   node telemetry.cjs --on       # enable  (writes the opt-in marker)
-//   node telemetry.cjs --off      # disable (removes the opt-in marker — the default)
-//
-// The opt-in marker is the reliable switch: it works no matter how the agent was
-// launched. EXPO_SKILLS_TELEMETRY=1/0 and DO_NOT_TRACK also work (handy for CI), but
-// env vars don't always reach hook subprocesses.
-
-const fs = require("fs");
-const path = require("path");
-const {
-  OPT_IN_PATH,
-  telemetryActive,
-  telemetryEnvSignal,
-  telemetryConfigured,
-  isCI,
-} = require("./telemetry_common.cjs");
-
-// One-line explanation of the current state (mirrors telemetryActive()'s precedence).
-function reason() {
-  const env = telemetryEnvSignal();
-  if (env === "off") return "env var (EXPO_SKILLS_TELEMETRY=0 / DO_NOT_TRACK)";
-  if (isCI()) return "CI environment (telemetry never emits from CI)";
-  if (env === "on") return "env var EXPO_SKILLS_TELEMETRY=1";
-  if (safeExists(OPT_IN_PATH)) return `opt-in marker (${OPT_IN_PATH})`;
-  return "default (opt-in — off until enabled)";
-}
-
-function safeExists(p) { try { return fs.existsSync(p); } catch { return false; } }
-
-function printStatus() {
-  const on = telemetryActive();
-  if (on && !telemetryConfigured()) {
-    console.log(`Expo skills telemetry: ON via ${reason()}, but no PostHog key in this build (stripped to placeholder) — nothing is sent.`);
-  } else if (on) {
-    console.log(`Expo skills telemetry: ON (anonymous) — ${reason()}. Turn off with: telemetry.cjs --off`);
-  } else {
-    console.log(`Expo skills telemetry: OFF — ${reason()}. Turn on with: telemetry.cjs --on (or EXPO_SKILLS_TELEMETRY=1)`);
-  }
-}
-
-const cmd = process.argv[2];
-
-if (cmd === "--on" || cmd === "--enable") {
-  fs.mkdirSync(path.dirname(OPT_IN_PATH), { recursive: true, mode: 0o700 });
-  fs.writeFileSync(OPT_IN_PATH, "Expo skills telemetry enabled by user.\n");
-  console.log(`Telemetry enabled — wrote ${OPT_IN_PATH}`);
-  if (telemetryEnvSignal() === "off") console.log("Note: an env var (EXPO_SKILLS_TELEMETRY=0 / DO_NOT_TRACK) still forces it OFF; unset it to send.");
-  else if (isCI()) console.log("Note: this looks like CI, where telemetry stays OFF regardless.");
-  console.log("Turn off any time with: telemetry.cjs --off");
-} else if (cmd === "--off" || cmd === "--disable") {
-  try { fs.rmSync(OPT_IN_PATH, { force: true }); } catch {}
-  console.log("Telemetry off — removed the opt-in marker (off is the default).");
-  if (telemetryEnvSignal() === "on") console.log("Note: EXPO_SKILLS_TELEMETRY=1 still forces it ON; unset it to stay off.");
-} else if (cmd === "--status" || cmd === undefined) {
-  printStatus();
-} else {
-  console.error(`Unknown option: ${cmd}\nUsage: telemetry.cjs [--status | --on | --off]`);
-  process.exit(2);
-}

package/bundled-skills/expo-skill-feedback/scripts/telemetry_common.cjs

@@ -1,171 +0,0 @@
-// Shared helpers for Expo skills PostHog telemetry.
-//
-// Zero npm dependencies — Node.js built-ins only (crypto, fs, https, os, path).
-// Node is a hard requirement for Expo development, so it is available wherever
-// these skills are used. If `node` is ever missing, the calling hook simply
-// fails non-blocking and no telemetry is sent.
-
-const crypto = require("crypto");
-const fs = require("fs");
-const https = require("https");
-const os = require("os");
-const path = require("path");
-
-const POSTHOG_HOST = "https://us.i.posthog.com";
-
-// PostHog project API key. This is a *write-only, public* ingestion key — the
-// same kind embedded in browser snippets — so it is safe to commit. Override
-// per environment with EXPO_SKILLS_POSTHOG_KEY (e.g. a staging project).
-// NOTE: never put a PostHog *personal* API key (phx_...) here — those are secret.
-const POSTHOG_PROJECT_API_KEY =
-  process.env.EXPO_SKILLS_POSTHOG_KEY || "phc_w8xRytdAAwkV3oExnuUozqH64PMzCmDLnyoChpPBcNXs";
-
-const SOURCE = "expo-skills";
-const INSTALLATION_ID_PATH = path.join(os.homedir(), ".expo-skills", "installation-id");
-
-// Opt-in is the model: telemetry is OFF by default and only sends once the user
-// explicitly enables it. This is the one product knob — flip to true for an opt-out
-// (on-by-default) model instead.
-const DEFAULT_ON = false;
-
-// Persistent opt-in marker. Its presence turns telemetry on across sessions, regardless
-// of how the agent was launched (env vars don't always reach hook subprocesses).
-// Written / removed by scripts/telemetry.cjs --on / --off.
-const OPT_IN_PATH = path.join(os.homedir(), ".expo-skills", "opt-in");
-
-// CI detection — never emit from automated environments so usage data reflects real
-// humans. Honors the common CI=true convention plus major providers' signals.
-function isCI() {
-  const ci = String(process.env.CI || "").trim().toLowerCase();
-  if (ci && ci !== "0" && ci !== "false") return true;
-  return Boolean(
-    process.env.GITHUB_ACTIONS ||
-      process.env.GITLAB_CI ||
-      process.env.CIRCLECI ||
-      process.env.TRAVIS ||
-      process.env.BUILDKITE ||
-      process.env.JENKINS_URL ||
-      process.env.TEAMCITY_VERSION ||
-      process.env.TF_BUILD
-  );
-}
-
-// Explicit on/off intent from env vars: returns "on" | "off" | null.
-//   DO_NOT_TRACK=1                        -> off (https://consoledonottrack.com)
-//   EXPO_SKILLS_TELEMETRY=0/off/false/no  -> off
-//   EXPO_SKILLS_TELEMETRY=1/on/true/yes   -> on
-function telemetryEnvSignal() {
-  const dnt = String(process.env.DO_NOT_TRACK || "").trim().toLowerCase();
-  if (dnt && dnt !== "0" && dnt !== "false") return "off";
-  const flag = String(process.env.EXPO_SKILLS_TELEMETRY || "").trim().toLowerCase();
-  if (["0", "false", "off", "no"].includes(flag)) return "off";
-  if (["1", "true", "on", "yes"].includes(flag)) return "on";
-  return null;
-}
-
-// Master gate. Nothing is sent unless this returns true. Precedence (highest first):
-//   1. explicit env off (DO_NOT_TRACK / EXPO_SKILLS_TELEMETRY=0) -> off
-//   2. CI                                                        -> off (never emit from bots)
-//   3. explicit env on  (EXPO_SKILLS_TELEMETRY=1)                -> on
-//   4. persistent opt-in marker (telemetry.cjs --on)            -> on
-//   5. default                                                   -> DEFAULT_ON (off = opt-in)
-// So explicit-off and CI always win; otherwise it's on only when explicitly enabled.
-function telemetryActive() {
-  const env = telemetryEnvSignal();
-  if (env === "off") return false;
-  if (isCI()) return false;
-  if (env === "on") return true;
-  try { if (fs.existsSync(OPT_IN_PATH)) return true; } catch {}
-  return DEFAULT_ON;
-}
-
-// A real key ships in this file, so this check passes by default. This guard only
-// makes the scripts inert if someone strips the key (e.g. a fork or private build).
-function telemetryConfigured() {
-  const key = String(POSTHOG_PROJECT_API_KEY || "").trim();
-  return key.length > 0 && key !== "phc_REPLACE_ME";
-}
-
-// Best-effort agent-harness label for the event (default when --agent-harness isn't passed).
-function detectHarness() {
-  if (process.env.CLAUDECODE) return "claude-code";
-  if (process.env.CODEX_SANDBOX || process.env.CODEX_SANDBOX_NETWORK_DISABLED ||
-      String(process.env.AGENT || "").toLowerCase() === "codex") return "codex";
-  return "unknown";
-}
-
-// Friendly OS + CPU arch for event properties (non-PII).
-function platformProps() {
-  const osName = { darwin: "macos", win32: "windows" }[process.platform] || process.platform;
-  return { os: osName, arch: process.arch };
-}
-
-// Random, anonymous, per-install id — created once at 0600, only its hash is ever sent.
-function readInstallationId(create = true) {
-  try {
-    if (fs.existsSync(INSTALLATION_ID_PATH)) {
-      const existing = fs.readFileSync(INSTALLATION_ID_PATH, "utf8").trim();
-      if (existing) return existing;
-    }
-    if (!create) return null;
-    fs.mkdirSync(path.dirname(INSTALLATION_ID_PATH), { recursive: true, mode: 0o700 });
-    try { fs.chmodSync(path.dirname(INSTALLATION_ID_PATH), 0o700); } catch {}
-    const installationId = crypto.randomUUID().replace(/-/g, "");
-    try {
-      // 'wx' = O_CREAT | O_EXCL | O_WRONLY — atomic create, fails if it exists.
-      const fd = fs.openSync(INSTALLATION_ID_PATH, "wx", 0o600);
-      try { fs.writeFileSync(fd, installationId + "\n"); } finally { fs.closeSync(fd); }
-      return installationId;
-    } catch (err) {
-      if (err && err.code === "EEXIST") return fs.readFileSync(INSTALLATION_ID_PATH, "utf8").trim() || null;
-      throw err;
-    }
-  } catch {
-    return null;
-  }
-}
-
-function telemetryIdentity(agentHarness, { createInstallation = true } = {}) {
-  const id = readInstallationId(createInstallation);
-  const installHash = id ? crypto.createHash("sha256").update(id).digest("hex").slice(0, 32) : null;
-  if (installHash) return [`expo-skills-installation:${installHash}`, { installation_id_hash: installHash }];
-  return [`expo-skills-events:${agentHarness}`, {}];
-}
-
-function sendToPosthog(payload, { userAgent, timeoutMs }) {
-  return new Promise((resolve, reject) => {
-    const url = new URL("/i/v0/e/", POSTHOG_HOST);
-    const body = Buffer.from(JSON.stringify(payload), "utf8");
-    const req = https.request(url, {
-      method: "POST",
-      headers: { "Content-Type": "application/json", "Content-Length": body.length, "User-Agent": userAgent },
-      timeout: timeoutMs,
-    }, (res) => {
-      const chunks = [];
-      res.on("data", (c) => chunks.push(c));
-      res.on("end", () => {
-        const status = res.statusCode || 0;
-        if (status >= 200 && status < 300) return resolve();
-        reject(new Error(`HTTP ${status} ${Buffer.concat(chunks).toString("utf8")}`));
-      });
-    });
-    req.on("timeout", () => req.destroy(new Error("request timed out")));
-    req.on("error", reject);
-    req.write(body);
-    req.end();
-  });
-}
-
-module.exports = {
-  POSTHOG_PROJECT_API_KEY,
-  SOURCE,
-  OPT_IN_PATH,
-  telemetryActive,
-  telemetryEnvSignal,
-  telemetryConfigured,
-  detectHarness,
-  isCI,
-  platformProps,
-  telemetryIdentity,
-  sendToPosthog,
-};

package/bundled-skills/expo-ui/SKILL.md

@@ -1,101 +0,0 @@
----
-name: expo-ui
-description: "Framework (OSS). Build native UI with the @expo/ui package: real SwiftUI on iOS and Jetpack Compose on Android. Default to @expo/ui for sheets (BottomSheet), pickers, sliders, toggles, menus, and grouped-form sections — do NOT reach for Reanimated, @gorhom/bottom-sheet, or RN built-in Picker/Switch; use @expo/ui instead. Fall back to RN built-ins only when @expo/ui is missing the component. NOTE: @expo/ui List renders native grouped rows like an iOS Settings screen — it is NOT a virtualized list; use FlatList/FlashList for large datasets. Covers universal components (Host, Column, Row, Button, Text, List, BottomSheet, FieldGroup, Switch, Slider, Picker, Menu), drop-in replacements for RN community libraries, and platform-specific SwiftUI/Jetpack Compose trees. Not for Expo Router navigation, Reanimated, or data fetching."
-version: 1.0.0
-license: MIT
-allowed-tools: "Bash(node *expo-ui/scripts/list-components.js *)"
----
-
-# Expo UI (`@expo/ui`)
-
-`@expo/ui` renders real native UI from React: SwiftUI on iOS, Jetpack Compose on Android. It also ships drop-in replacements for migrating off RN community UI libraries.
-
-> These instructions track the latest Expo SDK. The **universal** layer requires **SDK 56+** and works in Expo Go — no custom build needed. Drop-in replacements and the platform-specific layers also exist on SDK 55. For component details on a specific SDK, refer to the Expo UI docs for that version.
-
-## Installation
-
-```bash
-npx expo install @expo/ui
-```
-
-Every `@expo/ui` tree — universal or platform-specific — must be wrapped in `Host`.
-
-## Use @expo/ui by default — don't reach for RN alternatives first
-
-**Before using Reanimated, `@gorhom/bottom-sheet`, React Native's built-in `Switch`/`Picker`, or any community UI library for the items below, use `@expo/ui` instead.** Only fall back to RN built-ins when `@expo/ui` is missing the component.
-
-| Need | Use |
-|------|-----|
-| Slide-up sheet / bottom sheet | `BottomSheet` from `@expo/ui` — **not** Reanimated or `@gorhom/bottom-sheet` |
-| Grouped native list rows (settings/form-style) | `List` + `ListItem` from `@expo/ui` — **not** `FlatList` (see note below) |
-| Toggle | `Switch` from `@expo/ui` |
-| Slider | `Slider` from `@expo/ui` |
-| Date/time picker | `@expo/ui/community/datetimepicker` |
-| Menu | `Menu` from `@expo/ui` |
-| Form section with label | `FieldGroup` from `@expo/ui` |
-| Collapsible section | `Collapsible` from `@expo/ui` |
-
-> **`List` is NOT a virtualized scrolling list.** It renders native grouped table rows — the visual look of an iOS Settings screen or a form section, with disclosure indicators and native row styling. Each `ListItem` is a native node on the JS thread; rows are not recycled. For any list with large or unknown-length data (feeds, search results, catalogs), use **`FlatList`** or **`FlashList`** instead. `List` is the right choice for short, fixed-length groups: a settings screen, a detail panel's rows, a fixed menu.
-
-**`BottomSheet` example** (use this for map pin details, action sheets, detail panels — not Reanimated):
-
-```tsx
-import { Host, BottomSheet, Column, Text } from '@expo/ui';
-import { useState } from 'react';
-
-export default function MapScreen() {
-  const [isOpen, setIsOpen] = useState(false);
-
-  return (
-    <View style={{ flex: 1 }}>
-      <MapView onMarkerPress={() => setIsOpen(true)} />
-      <Host>
-        <BottomSheet
-          isPresented={isOpen}
-          onDismiss={() => setIsOpen(false)}
-          snapPoints={['half', 'full']}
-        >
-          <Column>
-            <Text>Café name</Text>
-            <Text>Address</Text>
-          </Column>
-        </BottomSheet>
-      </Host>
-    </View>
-  );
-}
-```
-
-`BottomSheet` uses `isPresented`/`onDismiss` — **not** `isOpened`, `isOpen`, `onIsOpenedChange`, or `onChange` (those are `@gorhom/bottom-sheet` props and will silently do nothing). `snapPoints` accepts `'half'`, `'full'`, `{ fraction: 0.5 }`, or `{ height: 400 }` and is optional (auto-sizes to content when omitted).
-
-## Choosing an approach
-
-Work down this list and stop at the first layer that meets the need:
-
-1. **Universal components — start here.** Import from the `@expo/ui` root. One component tree runs unmodified on iOS, Android, and web from a single source (Compose on Android, SwiftUI on iOS, `react-native-web`/`react-dom` on web). No platform file splits. → `./references/universal.md`
-
-2. **Platform-specific (SwiftUI / Jetpack Compose).** Import from `@expo/ui/swift-ui` or `@expo/ui/jetpack-compose`. Use **only** when the universal layer is missing a component or modifier you need, or when you need platform-specific behavior or optimization. **Downside:** you write two trees and split them into `.ios.tsx` / `.android.tsx` files (or branch on `Platform.OS`) — more code to maintain.
-
-   > **`@expo/ui/swift-ui` is iOS-only. `@expo/ui/jetpack-compose` is Android-only.** Importing either in a file that runs on the other platform will crash at runtime with "Unable to get view config" errors. Isolate platform-specific trees in `.ios.tsx` / `.android.tsx` files placed in `components/` (never inside `app/` — Expo Router does not support platform extensions for route files), or guard with `Platform.OS` in a regular route file. `Host` must always be imported from `@expo/ui` (the universal package root), not from the platform-specific sub-packages. → `./references/swift-ui.md` and `./references/jetpack-compose.md`
-
-**Already using an RN community UI library?** `@expo/ui` also ships **drop-in replacements** — API-compatible swaps for popular libraries (`@gorhom/bottom-sheet`, `@react-native-community/datetimepicker`, and more), imported from `@expo/ui/community/<name>`. This is a migration side-path for replacing an existing dependency, not a step in the universal-vs-platform decision above. → `./references/drop-in-replacements.md`
-
-## References
-
-Consult these resources as needed:
-
-```
-references/
-  universal.md             Universal @expo/ui components and when to use them (SDK 56+)
-  drop-in-replacements.md  API-compatible replacements for RN community UI libraries
-  swift-ui.md              Platform-specific iOS UI: @expo/ui/swift-ui components, modifiers, RNHostView, useNativeState
-  jetpack-compose.md       Platform-specific Android UI: @expo/ui/jetpack-compose components, modifiers, LazyColumn caveat, icons, useNativeState
-```
-
-## Submitting Feedback
-If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:
-```bash
-npx --yes submit-expo-feedback@latest --category skills --subject "expo-ui" "<actionable feedback>"
-```
-Only submit when you have something specific and actionable to report. Include as much relevant context as possible.
-If an AI agent repeatedly failed or the user had to take over an Expo task, load the expo-skill-feedback skill and follow its eval-candidate flow instead of reusing the command above.

package/bundled-skills/expo-ui/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "Expo UI"
-  short_description: "Build native UI with @expo/ui — universal components first, SwiftUI/Jetpack Compose when needed"
-  default_prompt: "Use $expo-ui when adding or reviewing @expo/ui UI: universal cross-platform components (Host, Column, Row, Button, Text, List, ...), drop-in replacements for React Native community libraries, or platform-specific @expo/ui/swift-ui and @expo/ui/jetpack-compose trees and modifiers. Recommend universal components first; use drop-in replacements when migrating off a community UI library; reach for platform-specific layers only when universal is missing something or you need platform optimization (which requires .ios.tsx/.android.tsx splits)."

package/bundled-skills/expo-ui/references/drop-in-replacements.md

@@ -1,27 +0,0 @@
-# Drop-in replacements for RN community libraries
-
-`@expo/ui` ships API-compatible replacements for popular React Native community libraries, powered by native `@expo/ui` components (Jetpack Compose on Android, SwiftUI on iOS). Use these when migrating an existing app off a community UI dependency — the API matches the library being replaced, so the swap is usually just the import path.
-
-## Available replacements
-
-Every drop-in lives under `@expo/ui/community/<kebab-case-name>`. Note which are default vs named imports.
-
-| Replaces | Import |
-|----------|--------|
-| `@gorhom/bottom-sheet` | `import BottomSheet, { BottomSheetView } from '@expo/ui/community/bottom-sheet'` |
-| `@react-native-community/datetimepicker` | `import DateTimePicker from '@expo/ui/community/datetime-picker'` |
-| `@react-native-masked-view/masked-view` | `import { MaskedView } from '@expo/ui/community/masked-view'` |
-| `@react-native-menu/menu` | `import { MenuView } from '@expo/ui/community/menu'` |
-| `react-native-pager-view` | `import PagerView from '@expo/ui/community/pager-view'` |
-| `@react-native-picker/picker` | `import { Picker } from '@expo/ui/community/picker'` |
-| `@react-native-segmented-control/segmented-control` | `import SegmentedControl from '@expo/ui/community/segmented-control'` |
-| `@react-native-community/slider` | `import Slider from '@expo/ui/community/slider'` |
-
-## Confirming the API
-
-Each component has a dedicated docs page with setup and usage:
-
-- Overview — https://docs.expo.dev/versions/latest/sdk/ui/drop-in-replacements/index.md
-- Per component — https://docs.expo.dev/versions/latest/sdk/ui/drop-in-replacements/{component}/index.md (slug is the component name lowercased, no hyphens, e.g. `bottomsheet`, `datetimepicker`, `segmentedcontrol`)
-
-The installed package's TypeScript types (`.d.ts`) are the most reliable source of truth for the exact props on your SDK version (@expo/ui is versioned with the SDK and its API can change between versions). Use the doc page to find platform support and any props that differ from the library being replaced.

package/bundled-skills/expo-ui/references/jetpack-compose.md

@@ -1,73 +0,0 @@
-# Platform-specific Android UI: `@expo/ui/jetpack-compose`
-
-> **Android only.** Code that imports from `@expo/ui/jetpack-compose` will crash on iOS with "Unable to get view config" errors. Always place this code in an `.android.tsx` component file or guard it with `Platform.OS === 'android'`. `Host` must be imported from `@expo/ui` (the universal root), not from `@expo/ui/jetpack-compose`.
-
-Use this layer only when the universal `@expo/ui` components don't cover what you need on Android (see `./universal.md` first). This requires a platform-specific tree.
-
-### File placement with Expo Router
-
-**Do not put `.android.tsx` files inside `app/` or `src/app/`.** Expo Router does not support platform-extension suffixes for route files and will throw a "no fallback sibling" Render Error.
-
-Place platform-specific component files in `components/` (or any directory outside the route tree), then import them from a regular route file:
-
-```
-src/components/ProductList.android.tsx   ← Compose tree lives here
-src/app/product-list.tsx                 ← regular Expo Router route, imports the component
-```
-
-`src/app/product-list.tsx`:
-```tsx
-import ProductList from '../components/ProductList';
-export default ProductList;
-```
-
-Alternatively, keep everything in one regular route file and branch on `Platform.OS`:
-
-```tsx
-// src/app/product-list.tsx
-import { Platform } from 'react-native';
-const ComposeList = Platform.OS === 'android' ? require('../components/ProductList.android').default : null;
-```
-
-## Instructions
-
-- Expo UI's API mirrors Jetpack Compose's API. Use Jetpack Compose and Material Design 3 knowledge to decide which components or modifiers to use. If you need deeper Jetpack Compose or Material 3 guidance (e.g. which component to pick, layout patterns, theming), spawn a subagent to research [Jetpack Compose](https://developer.android.com/develop/ui/compose/components) and [Material Design 3](https://m3.material.io/) best practices.
-- Components are imported from `@expo/ui/jetpack-compose`, modifiers from `@expo/ui/jetpack-compose/modifiers`.
-- **Before writing any code, run the list-components script** to get the exact components and modifiers available in the installed version:
-  ```bash
-  node <skill-root>/scripts/list-components.js <project-path>          # names only (compact)
-  node <skill-root>/scripts/list-components.js <project-path> --docs   # with one-line descriptions
-  ```
-  (`<skill-root>` is the directory containing this `references/` folder.)
-- **Always read the `.d.ts` type files** to confirm prop shapes and signatures — read the relevant `{ComponentName}/index.d.ts` from the installed `@expo/ui/jetpack-compose` package in `node_modules`. This is the most reliable source of truth.
-- When about to use a component, fetch its docs to confirm the API — https://docs.expo.dev/versions/latest/sdk/ui/jetpack-compose/{component-name}/index.md
-- When unsure about a modifier's API, refer to the docs — https://docs.expo.dev/versions/latest/sdk/ui/jetpack-compose/modifiers/index.md
-- Every Jetpack Compose tree must be wrapped in `Host`. Use `<Host matchContents>` for intrinsic sizing, or `<Host style={{ flex: 1 }}>` when you need explicit size (e.g. as a parent of `LazyColumn`). Example:
-
-```jsx
-import { Host } from "@expo/ui";                              // Host always from universal root
-import { Column, Button, Text } from "@expo/ui/jetpack-compose";
-import { fillMaxWidth, paddingAll } from "@expo/ui/jetpack-compose/modifiers";
-
-<Host matchContents>
-  <Column verticalArrangement={{ spacedBy: 8 }} modifiers={[fillMaxWidth(), paddingAll(16)]}>
-    <Text style={{ typography: "titleLarge" }}>Hello</Text>
-    <Button onPress={() => alert("Pressed!")}>Press me</Button>
-  </Column>
-</Host>;
-```
-
-- `RNHostView` embeds React Native components inside a Jetpack Compose tree (the same concept as in `@expo/ui/swift-ui`) — wrap any RN child in `<RNHostView>`.
-- If a required composable or modifier is missing in Expo UI, it can be extended via a local Expo module. See: https://docs.expo.dev/guides/expo-ui-jetpack-compose/extending/index.md. Confirm with the user before extending.
-
-## Key Components
-
-- **LazyColumn** — Use instead of react-native `ScrollView`/`FlatList` for scrollable lists. Wrap in `<Host style={{ flex: 1 }}>`. Not suitable for large lists — each item is a JSX node processed on the JS thread, which causes noticeable slowdowns at scale.
-- **Icon** — Use `<Icon source={require('./icon.xml')} size={24} />` with Android XML vector drawables. To get icons: go to [Material Symbols](https://fonts.google.com/icons), select an icon, choose the Android platform, and download the XML vector drawable. Save these as `.xml` files in your project's `assets/` directory (e.g. `assets/icons/wifi.xml`). Metro bundles `.xml` assets automatically — no metro config changes needed.
-
-## useNativeState
-
-`useNativeState` creates observable state that updates synchronously on the UI thread via worklets, enabling immediate native state changes without waiting for a React render cycle. Requires `react-native-worklets` — without it updates still go through React and flickering remains. Best for real-time interactions where synchronous updates matter, e.g. a text field that masks or formats input as the user types.
-
-- `ObservableState.value` is readable/writable from worklets; `onChange` fires a worklet listener on state change.
-- Docs — https://docs.expo.dev/versions/latest/sdk/ui/jetpack-compose/usenativestate/index.md