What problem does it solve? AI agents and automation scripts currently depend on raw xcrun simctl, xcodebuild, and XcodeBuildMCP calls to control iOS Simulators, producing unstable, non-machine-readable output. This Skill guides the design, implementation, and validation of TritonKit host-side simulator takeover commands that wrap those Apple tools behind stable JSON/JSONL CLI contracts with structured error codes and evidence artifacts. ## Core Features & Use Cases - Simulator and App Lifecycle Commands: Implement triton sim (list, boot, shutdown, screenshot, record, logs) and triton app (install, launch, prefs, container) commands returning machine-readable JSON with stable error codes. - Host-Side Network Proxy Lane: Build the Simulator-only proxy record/mock/block/throttle workflow with certificate planning, restore snapshots, HAR/NDJSON export, and break-glass audit gating for host mutations. - Evidence and Plan Integration: Archive proxy sessions and screenshots into .tritonevidence bundles and encode reusable .tritonplan replay steps with dry-run validation. - Use Case: When adding a new triton sim privacy command, follow the Skill's workflow: define BDD acceptance in the simulator takeover space, add shared model tests in TKHostAdapterModelsTests, implement contracts in TritonKitShared, expose the CLI command, and update commandSchemas plus documentation. ## Quick Start Ask the agent to implement a new TritonKit host simulator command such as triton sim privacy following the simulator takeover contract, starting with BDD acceptance and shared model tests.