iOS Simulator control from inside Aster, with the live device view in Aster's emulator pane. Use when driving a booted Apple Simulator on macOS: taps, gestures, typing, hardware buttons, rotation, and the accessibility tree, or when an iOS change needs simulator evidence. For an Android device or emulator use the Android emulator skill; build and install the app with xcodebuild or simctl first.
Installs into .claude/skills of the current project.
Are you the author of Aster Emulator?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/rkdrn79-aster-emulator)
---
name: aster-emulator
description: >-
iOS Simulator control from inside Aster, with the live device view in Aster's
emulator pane. Use when driving a booted Apple Simulator on macOS: taps,
gestures, typing, hardware buttons, rotation, and the accessibility tree, or
when an iOS change needs simulator evidence. For an Android device or emulator
use the Android emulator skill; build and install the app with xcodebuild or
simctl first.
license: Apache-2.0
---
# Aster Emulator
This discovery stub loads the version-matched guide from the Aster executable used for this session.
Prefer Aster over raw `serve-sim` or direct `simctl` for simulator control inside Aster; it
handles device scoping, helper lifecycle, and worktree context.
## Resolve the CLI for this session
Choose the executable once and reuse it for every later command:
- If the `ORCA_CLI_COMMAND` environment variable is set, use its value. Aster exports this
for managed WSL sessions.
- Otherwise, in a dev checkout whose session exposes `ORCA_DEV_REPO_ROOT`, use `aster-dev`.
- Otherwise, use `aster` (the same name on macOS, Linux, and Windows). Never substitute a
similarly named command from another app.
Below, `ASTER` is a placeholder for the executable you resolved. Substitute it before
running anything; do not create a shell variable or run `ASTER` literally. This works the
same way in POSIX shells, PowerShell, and cmd.exe.
If the selected executable cannot run, report its exact error and stop. Do not fall through
to another executable, which could silently target a different Aster build.
## Load the version-matched guide before running Aster commands
```text
ASTER skills get aster-emulator
```
Prefer `--json`. Use the selected executable's `--help` for commands or flags the guide does
not cover. If a command reports that Aster is not running, start it with `ASTER open --json`
and retry. If it fails with `runtime_access_denied`, your sandbox blocked the connection:
re-run it with escalated permissions, and do not run `ASTER open` or restart Aster. If
`skills get` is unknown, explain that updating Aster restores the guide; use `--help` for
read-only discovery and do not guess unsupported commands.