vibeview-agentlisted
Install: claude install-skill vibeview/skills
# VibeView agent control
Drive a live iOS, Android, Apple TV or Android TV VibeView session from the
CLI to verify a React Native change actually works, not just that it compiles. Requires the
`vibeview` CLI installed and authenticated (`vibeview login`, or
`VIBEVIEW_API_TOKEN` set).
## 1. Build requirements
Read before uploading anything — a build that violates these will install
and then crash or refuse to boot:
- **Android**: the debug APK must include an `x86_64` slice. Standard
`./gradlew assembleDebug` output includes it by default; only an issue if
the project filters ABIs.
- **iOS**: upload a **simulator** debug build (not a device `.ipa`), and it
must include the `arm64` slice.
Debug builds are auto-detected on upload — no separate flag needed. Upload
warnings are the safety net: if a build is missing the right architecture,
`upload-app` says so.
Full detail: https://vibeview.io/docs/live-development and
https://vibeview.io/docs/preparing-your-build.
## 2. The loop
1. Upload the debug build — **only after a native change** (new/updated
native module, Podfile/Gradle change). Everyday JS/asset edits never need
a re-upload:
```bash
vibeview upload-app ./path/to/app-debug.apk
```
2. Start Metro in the React Native project (`yarn start` or equivalent) and
leave it running.
3. Start a dev session in the background and get structured output. No
`vibeview.json` yet in this project (first run here)? Pass `--platform`
and `--app` explicitl