tritonkit-host-simulator-takeover

Implements Triton CLI contracts for host-side Apple Simulator control and evidence capture.

1|Updated May 15, 2026
One-click install
npx skills add https://github.com/NeptuneKit/TritonKit --skill tritonkit-host-simulator-takeover-neptunekit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tritonkit-host-simulator-takeover
Source: https://github.com/NeptuneKit/TritonKit/tree/main/.agents/skills/tritonkit-host-simulator-takeover
Command: npx skills add https://github.com/NeptuneKit/TritonKit --skill tritonkit-host-simulator-takeover-neptunekit

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about tritonkit-host-simulator-takeover

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new triton sim command to TritonKit?▼

Start by defining BDD acceptance in the simulator takeover space, then add command argv builder and parser tests in TKHostAdapterModelsTests. Implement shared contracts in TKHostAdapterModels.swift, expose the CLI command under Sources/TritonKitCLI with JSON output, and register it in commandSchemas().

How does TritonKit replace raw xcrun simctl usage?▼

TritonKit wraps simctl behind triton CLI commands that return stable JSON envelopes with error codes, hints, and next actions. Raw xcrun or xcodebuild is only a fallback after triton status, doctor, capabilities, or schema output proves the capability is missing or unsupported.

Does the iOS simulator proxy support real devices?▼

No, the iOS proxy lane is Simulator-only. Any target with scope=real or kind=real-device returns proxy_real_device_not_supported with configured=false, and ios-real: selector prefixes are preserved so they hit this rejection instead of being coerced into Simulator ids.

Why does sim record report success but produce an unusable video?▼

simctl can exit zero while the MOV contains only one frame, since container timelines report the requested duration. Triton computes actualDurationSeconds from AVSampleCursor encoded samples and returns sim_record_truncated or sim_record_invalid_artifact when media validation fails.

What are the limitations of the simulator network proxy capture?▼

The proxy provides metadata-only visibility: CONNECT metadata and HAR skeletons are not decrypted HTTPS bodies. Traffic using certificate pinning, custom sockets, private encryption, or unsupported QUIC bypasses visibility and is reported through codes like proxy_visibility_limited or proxy_cert_untrusted.

When should I use triton wait versus embedded runtime waits?▼

Use wait --platform ios for host-side Simulator AX observation with --text, --exists, or --gone against ready local Simulator targets. Use plain wait without --platform for embedded runtime conditions such as idle, hierarchy change, or predicates through triton serve.