callstackincubator/apex-software-factory / .agents/skills/agent-device
agent-device
VerifiedDrive the Apex Factory app on a leased iOS simulator or Android emulator with agent-device through .agents/scripts/device-lane.sh — open the app, read the accessibility snapshot, tap, type, scroll, verify with wait/is/get, take screenshots, record evidence, and write or replay agent-device .ad scripts (the e2e tests under apps/mobile/e2e/). Use for any interaction with a device, when writing an e2e: test, or when someone says "check it on the simulator", "tap through the app" or "dogfood the app".
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.4 KB |
| SOURCE.md | markdown | 1.4 KB |
| references/android-emulator.md | markdown | 1.5 KB |
| references/dogfood.md | markdown | 933 B |
| references/ios-simulator.md | markdown | 1.6 KB |
references/ios-simulator.md
View on GitHub# iOS Simulator
Vendored from upstream `skills/ios-simulator/SKILL.md` (see `../SOURCE.md`) and adapted: in
this repo agent-device is the workspace's pinned devDependency, the simulator is leased from
simlock, and every command goes through `.agents/scripts/device-lane.sh ad …`, which adds
`--platform ios --udid <leased UDID> --ios-simulator-device-set <simlock set> --session
apex-<branch>`. Never install agent-device (no `npm install -g`, no `npx`), never pass those
flags yourself, and never call `xcrun simctl` to boot, erase or install.
For a normal app-driving task, start immediately. Do not probe first with `--help`,
`--version`, `devices`, `appstate`, `snapshot`, or `screenshot`:
```bash
.agents/scripts/device-lane.sh ad open com.callstack.apexfactory --foreground
```
Follow the initial interactive snapshot and corrective error hints. If the lane reports
`unavailable`, stop and report it; do not work around it.
Only when the task is specialized or a command shape is unclear, read the relevant
version-matched help topic (help needs no device, so call the pinned CLI directly):
```bash
pnpm exec agent-device help validate # engineering validation and build freshness
pnpm exec agent-device help debugging # screenshots, logs, traces, video, and failures
pnpm exec agent-device help react-native # React Native and Expo runtime guidance
pnpm exec agent-device help scripting # durable replay and CI workflows
```
`help react-devtools` describes a command this repo does not allow (it fetches from npm);
use the `rozenite` skill's `react` domain instead.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |