ios-product-dev

Implement and verify native iOS SwiftUI features while preserving shared API and platform boundaries.

2.4k|292|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/The-Vibe-Company/companion --skill ios-product-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ios-product-dev
Source: https://github.com/The-Vibe-Company/companion/tree/main/.agents/skills/ios-product-dev
Command: npx skills add https://github.com/The-Vibe-Company/companion --skill ios-product-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about ios-product-dev

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

FAQPage Schema
How do I build a native iOS feature in SwiftUI for the Companion app?

Start by reading the repository and apps/ios guidance, shape the user-facing states and roles, implement models and networking in CompanionKit, and build SwiftUI presentation in the app target. Verify with CompanionKit tests, a simulator build, and UI inspection through xcodebuildmcp-cli.

How do I verify SwiftUI changes in the iOS simulator?

Use xcodebuildmcp-cli for discovery, simulator builds, tests, launches, screenshots, and UI inspection. Do not fall back to raw xcodebuild, xcrun, or simctl, and check the actual rendered result rather than only the process exit code.

Can the iOS client add mobile-only API endpoints?

No. The iOS client must use the existing /v1 APIs and shared models, and never invent mobile-only endpoints or hide product workflows. The client also never contacts Box or Pi directly or handles Box credentials.

When should design work be handed off instead of done in this skill?

Visual direction, interaction hierarchy, copy, color, and motion decisions belong to design-frontend-dev. This skill translates those decisions into native controls rather than duplicating the cross-platform design register.

What accessibility requirements apply to iOS changes?

Changes must respect Dynamic Type, VoiceOver, Reduce Motion, Reduce Transparency, sufficient hit targets, and color-independent status communication. Liquid Glass is limited to native iOS 26 system navigation and interactive controls, with an opaque fallback for Reduce Transparency.