{
  "skills": [
    {
      "id": "skl_apple_container_internals",
      "name": "apple-container-internals",
      "plugin": "cwc-ios-engineering",
      "description": "Architecture-level knowledge of Apple's `container` runtime source (vendors/apple/container) — how it actually runs a Linux container as a per-container lightweight VM: the apiserver/XPC-helper process model, the DNSServer + SocketForwarder networking path, ContainerBuild, ContainerOS, the config.toml schema, and the CLI command surface. Use when the user asks how `container` works internally, which process does what, how container networking/ DNS/port-forwarding is implemented, how to read or extend a specific subsystem under vendors/apple/container/Sources, what config.toml keys exist, or wants an exact CLI command from the vendored command-reference. Trigger on \"how does apple container work\", \"container-apiserver\", \"container networking internals\", \"DNSServer\", \"SocketForwarder\", \"vmnet\", \"container XPC\", \"config.toml\", \"container-network-vmnet\", \"container command reference\". Do NOT use for container lifecycle GATES, sandboxing policy, or eBPF/security work (apple-linux-containers owns those), nor for authoring Swift apps (swift-app-engineering).",
      "summary": "Architecture-level knowledge of Apple's `container` runtime source (vendors/apple/container) — how it actually runs a Linux container as a per-container lightweight VM: the apiserver/XPC-helper process model, the DNSServer + SocketForwarder networking path, ContainerBuild, ContainerOS, the config...",
      "gated": 0,
      "source_path": "plugins/cwc-ios-engineering/skills/apple-container-internals/SKILL.md",
      "created_at": "2026-07-10 18:13:13",
      "cite_as": "https://subagentskills.com/api/skills/skl_apple_container_internals"
    },
    {
      "id": "skl_apple_linux_containers",
      "name": "apple-linux-containers",
      "plugin": "cwc-ios-engineering",
      "description": "Linux systems and security engineering on Apple silicon via Apple's `container` runtime (vendors/apple/container) — OCI images run as lightweight per-container VMs on Virtualization.framework. Use when the user asks to run Linux containers or VMs on a Mac, sandbox a coworker/Claude Code session (desktop.md's bypass-permissions best practice: \"only use in sandboxed containers or VMs\"), work with OCI images outside Docker, investigate the desktop-linux Claude Desktop app inside a VM, or do OS-internals/security work in a Linux guest (eBPF, kernel instrumentation, detection-as-code, hardening). Trigger on \"apple container\", \"container system start\", \"Linux VM on Mac\", \"Virtualization.framework\", \"sandbox this session\", \"OCI on macOS\", \"eBPF\", \"kernel instrumentation\", \"seccomp\", \"detection as code\". Do NOT use for Docker Desktop operations (different runtime, different daemon) or for Cloudflare Workers sandboxes (cloud-side, not this Mac).",
      "summary": "Linux systems and security engineering on Apple silicon via Apple's `container` runtime (vendors/apple/container) — OCI images run as lightweight per-container VMs on Virtualization.framework.",
      "gated": 0,
      "source_path": "plugins/cwc-ios-engineering/skills/apple-linux-containers/SKILL.md",
      "created_at": "2026-07-10 18:13:13",
      "cite_as": "https://subagentskills.com/api/skills/skl_apple_linux_containers"
    },
    {
      "id": "skl_device_hardware",
      "name": "device-hardware",
      "plugin": "cwc-ios-engineering",
      "description": "Hardware introspection for Apple devices — READS the real machines and the real SDK instead of recalling. `uv run hwprobe mac` (this Mac's chip/cores/memory via sysctl), `uv run hwprobe device --udid <UDID>` (a tethered iOS device via `xcrun devicectl`), `uv run hwprobe sdk` (the version-exact nw_interface_type_t enum parsed from Network.framework's on-disk header). Every fact is provenance-tagged — probe / sdk_header / doc / unavailable — and a fact that can't be probed or cited is marked UNAVAILABLE with a reason, NEVER guessed (Apple SoC die internals are not authoritatively knowable here and are reported as such). Use when the user asks what chip/cores/memory a Mac has, what a tethered iPhone/iPad actually is, the exact Network.framework interface-type enum for the installed SDK, or wants hardware facts grounded rather than recalled. Trigger on \"what chip\", \"how many cores\", \"device info\", \"devicectl\", \"sysctl hardware\", \"nw_interface_type\", \"SDK header\", \"iPhone hardware\", \"Apple silicon cores\". Do NOT use for packet capture (packet-trace) or Swift app code (swift-app-engineering).",
      "summary": "Hardware introspection for Apple devices — READS the real machines and the real SDK instead of recalling.",
      "gated": 0,
      "source_path": "plugins/cwc-ios-engineering/skills/device-hardware/SKILL.md",
      "created_at": "2026-07-10 18:13:13",
      "cite_as": "https://subagentskills.com/api/skills/skl_device_hardware"
    },
    {
      "id": "skl_foundation_models_bridge",
      "name": "foundation-models-bridge",
      "plugin": "cwc-ios-engineering",
      "description": "Deep knowledge of `vendors/anthropics/ClaudeForFoundationModels` — the package that conforms Claude to Apple's FoundationModels `LanguageModel` protocol so you drive Claude through the SAME `LanguageModelSession` API (`respond(to:)`, streaming, `@Generable` guided generation, tool calling) as Apple's on-device model. THE key fact this skill exists to teach: this bridge is SERVER-SIDE (a network call to Anthropic, OS 27 / Xcode 27 / API key required) — it is NOT on-device and NOT offline; do not confuse it with Apple's own local model or with the direct ClaudeAPI Messages client. Use when the ask involves FoundationModels + Claude, `ClaudeLanguageModel`, `LanguageModelSession` with Claude, `@Generable` output from Claude, `serverTools` (web search/fetch/code execution), effort mapping, or choosing between on-device / bridge / direct-API. Trigger on \"Foundation Models\", \"FoundationModels\", \"LanguageModelSession\", \"ClaudeLanguageModel\", \"@Generable\", \"on-device model\", \"Apple Intelligence\", \"server-side language model\", \"ClaudeForFoundationModels\". Do NOT use for the direct ClaudeAPI Messages client or SwiftUI work (swift-app-engineering), or for container/VM internals (apple-container-internals).",
      "summary": "Deep knowledge of `vendors/anthropics/ClaudeForFoundationModels` — the package that conforms Claude to Apple's FoundationModels `LanguageModel` protocol so you drive Claude through the SAME `LanguageModelSession` API (`respond(to:)`, streaming, `@Generable` guided generation, tool calling) as App...",
      "gated": 0,
      "source_path": "plugins/cwc-ios-engineering/skills/foundation-models-bridge/SKILL.md",
      "created_at": "2026-07-10 18:13:13",
      "cite_as": "https://subagentskills.com/api/skills/skl_foundation_models_bridge"
    },
    {
      "id": "skl_packet_trace",
      "name": "packet-trace",
      "plugin": "cwc-ios-engineering",
      "description": "Trace a network packet's path from the iPhone Claude app, across home Wi-Fi, all the way to the Claude web app running in a browser on the user's Mac — and back. uv-managed typed tooling: capture-surface PLANNERS that emit real, copy-pasteable rvictl + tcpdump commands (you cannot tcpdump a stock iPhone — Apple's Remote Virtual Interface mirrors the tethered phone onto the Mac), runtime host-OS detection (never a hardcoded macOS/iOS version), and 5-tuple flow correlation that stitches separate pcaps into one end-to-end trace. Run `uv run netpath doctor` (detect host + attached iPhone UDIDs), `uv run netpath plan --udid <UDID>` (emit the capture recipes), `uv run netpath correlate --hops <file>` (orient the captures into flows). Trigger on \"trace the packet\", \"capture iPhone traffic\", \"rvictl\", \"tcpdump the phone\", \"where does my Claude app traffic go\", \"network path iPhone to Mac\", \"packet trace across devices\". Do NOT use for Swift app code (swift-app-engineering) or VM lifecycle gates (apple-linux-containers) — though this skill's VM_BRIDGE surface reuses the Lima/apple-container interfaces that skill owns.",
      "summary": "Trace a network packet's path from the iPhone Claude app, across home Wi-Fi, all the way to the Claude web app running in a browser on the user's Mac — and back.",
      "gated": 0,
      "source_path": "plugins/cwc-ios-engineering/skills/packet-trace/SKILL.md",
      "created_at": "2026-07-10 18:13:13",
      "cite_as": "https://subagentskills.com/api/skills/skl_packet_trace"
    },
    {
      "id": "skl_swift_app_engineering",
      "name": "swift-app-engineering",
      "plugin": "cwc-ios-engineering",
      "description": "iOS/Swift app engineering for this repo's Apple surfaces — the house ClaudeAPI Swift package (apps/coworkers-desktop-buddy/Sources/ClaudeAPI) and any SwiftUI/UIKit application work above it. Use when the user asks to build, extend, or debug Swift/SwiftUI/UIKit code, touch MessagesRequest/Configuration/ SSEParser in the ClaudeAPI module, optimize the mobile stack (rendering, memory, launch time, streaming), or prepare an app for TestFlight. Trigger on \"Swift\", \"SwiftUI\", \"UIKit\", \"Xcode\", \"iOS app\", \"ClaudeAPI module\", \"TestFlight\", \"app performance\". Do NOT use for: the ClaudeForFoundationModels server-side bridge or Apple's FoundationModels framework (foundation-models-bridge owns those, and they are NOT the same thing as this Messages client); shipping Cloudflare Workers (cwc-deploy); or flashing ESP32/M5Stack hardware (m5-onboard/ cardputer-buddy) — this is the Swift app-client/UI layer.",
      "summary": "iOS/Swift app engineering for this repo's Apple surfaces — the house ClaudeAPI Swift package (apps/coworkers-desktop-buddy/Sources/ClaudeAPI) and any SwiftUI/UIKit application work above it.",
      "gated": 0,
      "source_path": "plugins/cwc-ios-engineering/skills/swift-app-engineering/SKILL.md",
      "created_at": "2026-07-10 18:13:13",
      "cite_as": "https://subagentskills.com/api/skills/skl_swift_app_engineering"
    },
    {
      "id": "skl_swift_conduit",
      "name": "swift-conduit",
      "plugin": "cwc-ios-engineering",
      "description": "The conduit's typed Python tooling — macOS ⇄ Linux-VM Swift environments as Pydantic models, OODA loops, and SemVer metadata. Use when the user asks to probe an environment for Swift/claude-desktop (EnvironmentObserver), plan a Swift-toolchain or Claude Desktop Linux install (installers emit the verbatim desktop-linux.md apt sequence as typed InstallSteps — plans, not executions), run a build check with a typed report, record an observe→orient→decide→act iteration (uv run ooda), or read/write versions.json (MetadataStore; the Swift CLI and MCP semver_metadata tool read the same file — proven cross-language round-trip). Trigger on \"conduit\", \"Swift on Linux\", \"provision the VM\", \"install claude-desktop\", \"ooda\", \"versions manifest\", \"environment probe\". Do NOT use for authoring Swift code (swift-app-engineering) or for VM-runtime lifecycle decisions (apple-linux-containers owns those gates).",
      "summary": "The conduit's typed Python tooling — macOS ⇄ Linux-VM Swift environments as Pydantic models, OODA loops, and SemVer metadata.",
      "gated": 0,
      "source_path": "plugins/cwc-ios-engineering/skills/swift-conduit/SKILL.md",
      "created_at": "2026-07-10 18:13:13",
      "cite_as": "https://subagentskills.com/api/skills/skl_swift_conduit"
    },
    {
      "id": "skl_swift_package_inventory",
      "name": "swift-package-inventory",
      "plugin": "cwc-ios-engineering",
      "description": "Typed inventory of a real Swift package WITHOUT building it: runs `swift package dump-package` (manifest evaluation only — seconds, no compile), parses SwiftPM's verbose dump JSON into a compact typed summary (products, targets + their dependencies, package dependencies with version requirements), and greps MCP `Tool(name: \"...\")` registrations out of Sources/ so the MCP surface is inventoried alongside the package graph. Point it at any package dir; defaults to apps/subagentswift-mcp (the fleet's Swift MCP server). Use when the user asks what a Swift package ships, its products/targets/deps, which MCP tools a Swift server registers, or wants a package graph without waiting for a build. Trigger on \"dump-package\", \"package inventory\", \"what does this package ship\", \"which MCP tools\", \"SwiftPM graph\". Do NOT use for building/testing the package (swift-conduit's build checks own that), for the ClaudeForFoundationModels graph narrative (cwc-swift-engineering's swift-stack-trace owns that reading), or for non-SwiftPM projects.",
      "summary": "Typed inventory of a real Swift package WITHOUT building it: runs `swift package dump-package` (manifest evaluation only — seconds, no compile), parses SwiftPM's verbose dump JSON into a compact typed summary (products, targets + their dependencies, package dependencies with version requirements)...",
      "gated": 0,
      "source_path": "plugins/cwc-ios-engineering/skills/swift-package-inventory/SKILL.md",
      "created_at": "2026-07-10 18:13:13",
      "cite_as": "https://subagentskills.com/api/skills/skl_swift_package_inventory"
    },
    {
      "id": "skl_tdd_red_green",
      "name": "tdd-red-green",
      "plugin": "cwc-ios-engineering",
      "description": "The fleet's TDD orchestration pipeline — model-routed red/green/refactor with hard budgets and two no-silent-failure alert paths. Use when building Python (or any testable) modules coworker-style: the main-loop model (Fable 5) writes the pytest suite first (RED), a budgeted background Sonnet 5 coder agent runs the ralph-loop contract to make it pass (GREEN) then refactor, the main loop re-verifies, and a Sonnet 5 helper updates the durable plan file. Trigger on \"tdd\", \"red/green\", \"ralph\", \"write tests first\", \"dispatch a coder\", \"background implementation\", or any conduit-plan W-task marked RED/GREEN. Do NOT use for one-line fixes or docs-only changes — the harness overhead only pays for real modules with real contracts.",
      "summary": "The fleet's TDD orchestration pipeline — model-routed red/green/refactor with hard budgets and two no-silent-failure alert paths.",
      "gated": 0,
      "source_path": "plugins/cwc-ios-engineering/skills/tdd-red-green/SKILL.md",
      "created_at": "2026-07-10 18:13:13",
      "cite_as": "https://subagentskills.com/api/skills/skl_tdd_red_green"
    }
  ]
}