What problem does it solve?
Native iOS feature work often drifts from the shared API contract, breaks accessibility, or bypasses platform boundaries. This Skill owns end-to-end iOS product changes in SwiftUI so features stay consistent with the Companion client contract, role permissions, and design language.
Core Features & Use Cases
- End-to-end iOS feature ownership: Shape product behavior, implement in SwiftUI and CompanionKit, and verify with simulator builds and UI inspection via xcodebuildmcp-cli.
- Contract and boundary enforcement: Preserve the shared /v1 API, Owner/Editor/Viewer role behavior, and the rule that the client never contacts Box or Pi directly.
- Coordinated handoffs: Route visual direction to design-frontend-dev, SwiftUI mechanics to swiftui-expert-dev, and final review or delivery to review-code-dev or ship-pr-dev.
- Use Case: Add a durable interruption state with Retry and Cancel to an iOS Companion thread, covering loading, error, offline, Dynamic Type, and VoiceOver states, then verify it in the simulator.
Quick Start
Ask the agent to build a native iOS feature, such as adding a retryable interrupted state to a Companion thread, and have it verify the result in the simulator.