mobai

## MobAI Usage Rules (IMPORTANT)

When automating mobile devices, ALWAYS use this order:

1. **mobai:native-runner** - For ANY native app UI automation (tapping, typing, swiping, observing UI)
2. **mobai:web-runner** - For ANY web browser or WebView automation
3. **mobai:agent** - For complex multi-step tasks requiring AI reasoning
4. **Raw HTTP API** - ONLY for: listing devices, starting/stopping bridge

**ALWAYS try DSL subagents first.** Raw HTTP API for tap/type/swipe/screenshot/ui-tree is a LAST RESORT.

**Screenshots:** When using the API, screenshots are automatically saved to `/tmp/mobai/screenshots/` and the path is returned. Use the Read tool to view them.

# MobAI Device Control

This skill enables you to control Android and iOS devices through the MobAI HTTP API running locally.

## Sub-Agent Architecture

For complex automation tasks, use a **hierarchical approach** with specialized sub-agents:

### When to Use Sub-Agents

| Scenario | Approach |
|----------|----------|
| Simple query (list devices, take screenshot) | Direct API call |
| Native app automation (Settings, Instagram) | Spawn **native-runner** sub-agent |
| Browser chrome (URL bar, tabs, nav buttons) | Spawn **native-runner** sub-agent |
| Web page DOM content (CSS selectors, JS, DOM) | Spawn **web-runner** sub-agent (try native-runner first) |
| Complex multi-step task | Break into subgoals, spawn appropriate sub-agent for each |

### Native Runner (`/native-runner`)

Use for **native mobile apps** - apps that use platform UI components:
- Settings app, Mail, Photos, Calendar
- Third-party apps (Instagram, WhatsApp, Uber)
- Any app where you need to tap UI elements by accessibility predicates

**Uses DSL batch execution** with element predicates for robust automation.

**How to spawn:**
```
Use the native-runner skill to accomplish: [subgoal description]
Device ID: [deviceId]
```

### Web Runner (`/web-runner`)

Use web-runner when you need to interact with DOM content inside a web page or