← ClaudeAtlas

iblai-vibe-ops-buildlisted

Build and run your ibl.ai app on desktop and mobile (iOS, Android, macOS, Surface)
iblai/vibe · ★ 15 · AI & Automation · score 76
Install: claude install-skill iblai/vibe
# /iblai-vibe-ops-build Build and run your ibl.ai app on desktop and mobile using Tauri v2. Covers iOS, Android, macOS/Linux desktop, and Surface tablet builds. > **Building:** run Tauri directly — `pnpm exec tauri <cmd>` (e.g. > `pnpm exec tauri dev`, `pnpm exec tauri ios build`). The Tauri > shell templates live in [`assets/tauri/`](assets/tauri/) (copy into > `src-tauri/`), the CI workflows in > [`assets/tauri/workflows/`](assets/tauri/workflows/), and the default app > icons in [`assets/icons/`](assets/icons/). The full mapping (`init`, > `device`, `ci-workflow`, `iconography`, `screenshot`) is in > [`references/builds-command.md`](references/builds-command.md). Before adding build support or running a dev build, **stop all running dev servers** (`pnpm dev`, `next dev`, etc.) to avoid port conflicts. Kill any process on port 3000 before proceeding. When the user asks to add iOS or Android build support, automatically start the emulator/simulator after initialization -- just like you would start `pnpm dev` after adding auth. Run `xcrun simctl list devices` (iOS) / `adb devices` (Android) to find the available device name, then start the dev build with that device. Do NOT guess device names. Always run `xcrun simctl list devices` (iOS) / `adb devices` (Android) first and use a device name from the output. ## Prerequisites (All Platforms) - **Tauri support** added to your project: ```bash # add the Tauri shell: copy assets/tauri/ into src-tauri/ + add @tauri-apps