
Claude Skills by AndrewDongminYoo
github.com/AndrewDongminYooUse when a React Native project has messy assets — unreferenced/unused image, SVG, or Lottie files, scattered or deeply-relative require() paths, or string-based asset references you want made type-safe. Audits first (read-only), then offers git-safe cleanup. Wraps the rn-typed-assets CLI.
Use when you need a broad, evidence-based React Native or Expo code audit of a project, feature, or diff. It reviews rendering, hooks, lists, native boundaries, and effects without changing source.
Use when you need a read-only inventory of React Native or Expo GitHub Actions artifact evidence before a workflow review.
Use when an agent needs to see the running React Native app — verify a screen rendered as intended, capture the iOS simulator or Android emulator, or screenshot an iOS 17+ physical device. Read-only with respect to project source; writes only a screenshot artifact. Runs the bundled device-shot.sh helper.
Use when React Native or Expo acceptance work needs runtime evidence from a simulator, emulator, or physical device, including screenshots, logs, UI interaction, or exploratory QA.
Use when you need a deterministic, read-only resolution of one Expo EAS build profile and its extends chain from eas.json.
Use when you need to read a running React Native app's console output — confirm a log fired, watch console.warn/error, or verify runtime behavior — without opening the DevTools GUI. Reads logs from Metro's CDP endpoint; bounded by default. Read-only with respect to project source. Runs the bundled rn-console.mjs helper.
Use when planning a React Native upgrade or asking "is my app ready for the New Architecture?" — audits which dependencies and app-local native modules block enabling the New Architecture. Read-only; reports and interprets, changes nothing. Wraps the rn-newarch-ready CLI.
Use when you want a fast, read-only snapshot of a React Native project's setup — RN/Expo version, New Architecture and Hermes flags, package manager, key config files — before deciding what to audit or upgrade. Read-only; routes to the deeper audits. A read-only reader: it surfaces stable files and commands, never changes anything.
Use when a React Native or Expo upgrade is being planned and you need the current upgrade surface recorded as evidence — installed versions, package-manager and lockfile candidates, native ownership, CI verification gaps. Wraps the bundled, tested rn-upgrade-pulse.mjs and stable read commands; read-only, and it never selects a target version. For a fast setup overview use rn-project-snapshot, and for New Architecture readiness specifically use rn-newarch-audit.