ios-simulatorlisted

# iOS Simulator Use Simulator as a reproducible verification environment while keeping device selection and destructive operations explicit. ## Scope and Safety This skill owns Simulator discovery, boot/shutdown, app install/launch, screenshots, logs, permissions, locations, push simulation, containers, and CI lifecycle. It does not replace real-device verification for hardware, performance, networking conditions, push delivery, camera, Bluetooth, NFC, or other device-only behavior. Resolve an explicit simulator UDID before mutating state. Prefer an already booted suitable device. Do not erase or delete all simulators, broad CoreSimulator directories, or unrelated devices as a routine recovery step. If an erase/delete is genuinely needed, verify the exact target and preserve user data unless the task authorizes its removal. Read [simctl Command Reference](references/simctl-commands.md) for command syntax and less common operations. ## Workflow 1. Inspect the Xcode project/workspace, scheme, supported platform, deployment target, installed runtimes, and available devices. 2. Select one destination by UDID and boot it if needed. 3. Build the intended scheme for that destination with a dedicated derived-data path when isolation helps. 4. Install and launch by bundle identifier; preserve the installed app container unless a clean-state test is required. 5. Capture logs, screenshots, and interaction evidence relevant to the request. 6. Clean up only devices, overrides, perm