watchos_skill

This skill guides watchOS development with SwiftUI, connectivity, and complications to optimize app design, performance, and user experience.
  • Swift

56

GitHub Stars

5

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill rshankras/claude-code-apple-skills --skill watchos

  • complications.md11.1 KB
  • health-fitness.md16.8 KB
  • SKILL.md9.6 KB
  • watch-connectivity.md11.6 KB
  • widgets-for-watch.md12.4 KB

Overview

This skill provides practical guidance for building watchOS apps with SwiftUI, Watch Connectivity, complications, and watch-specific UI patterns. It focuses on watch-first design, performance, and battery-aware architecture to deliver fast, glanceable experiences. Use it for code reviews, best practices, or implementation help across common watchOS features.

How this skill works

The skill inspects design choices, architecture patterns, and code snippets for NavigationStack, List styles, Watch Connectivity session setup, complication providers, and workout/HealthKit integration. It explains appropriate data transfer methods (application context, sendMessage, transferUserInfo, transferFile), complication timelines, and WidgetKit-based complications. It highlights platform-specific APIs like digital crown handling, haptics, and Now Playing integration.

When to use it

  • Designing a watch-first UI that’s glanceable and fast
  • Implementing or reviewing Watch Connectivity sync and transfer strategies
  • Creating complications using ClockKit or WidgetKit providers
  • Optimizing battery, background work, and complication update cadence
  • Building workout or HealthKit-powered watch experiences

Best practices

  • Design for quick interactions (≤2 seconds) and show only essential info
  • Prefer independent watch apps and cache data locally for offline use
  • Use appropriate connectivity APIs: applicationContext for state, sendMessage for real-time, transferUserInfo for queued delivery
  • Limit background and network work; prefer timeline-based complication updates
  • Use large touch targets, clear icons, loading states, and haptic feedback

Example use cases

  • Code review of a SwiftUI watch app using NavigationStack and TabView
  • Implementing a complication with timeline entries or a WidgetKit accessory
  • Syncing settings and small data from iPhone using updateApplicationContext
  • Building a workout session with HealthKit and live metrics
  • Tuning battery usage by batching network requests and reducing location polls

FAQ

Prefer independent watch apps when possible so the watch is usable without the phone; use Watch Connectivity for nonessential sync and cache data locally for offline access.

Which Watch Connectivity method should I use for each case?

Use updateApplicationContext for current state/settings, sendMessage for real-time interactions when both apps are active, transferUserInfo for guaranteed queued transfers, and transferFile for large payloads.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational