Includes design considerations specific to the platform — small display with large touch targets, glanceable information with minimal text, Digital Crown scrolling/input, Force Touch on older watches, swipe/tap gestures, and battery-conscious background work.
Best practices: keep information glanceable, use large tap targets, minimize text input, drive watch-face updates through complications, use efficient background refresh, and always validate on real hardware since the simulator behaves differently.
watchOS Platform
watchOS-specific development for Apple Watch experiences.
Agent Workflow (MANDATORY)
Before ANY implementation, spawn 3 agents in parallel, one Agent call each with a name:
- fuse-ai-pilot:explore-codebase - Analyze existing watchOS patterns
- fuse-ai-pilot:research-expert - Verify latest watchOS 26 docs via Context7/Exa
- mcp__apple-docs__search_apple_docs - Check watchOS patterns
After implementation, run fuse-ai-pilot:sniper for validation.
Overview
When to Use
- Building Apple Watch apps
- Creating watch face complications
- Workout and fitness tracking
- Health data access (HealthKit)
- iPhone-Watch communication
Why watchOS Skill
| Feature |
Benefit |
| Complications |
Glanceable data on watch face |
| Workouts |
Fitness and health tracking |
| HealthKit |
Access health metrics |
| Connectivity |
Sync with iPhone |
Reference Guide
| Need |
Reference |
| Watch face complications |
complications.md |
| Workout sessions, HealthKit |
workouts.md |
| iPhone ↔ Watch sync |
watch-connectivity.md |
Design Considerations
Screen Size
- Small display, large touch targets
- Glanceable information
- Minimal text, clear icons
Interactions
- Digital Crown for scrolling/input
- Force Touch (older watches)
- Gestures: swipe, tap
Battery
- Minimize background work
- Use complications for updates
- Efficient data transfer
Best Practices
- Glanceable - Quick information access
- Large targets - Easy tapping
- Minimal input - Reduce typing
- Complications - Update watch face data
- Background refresh - Efficient updates
- Test on device - Simulator differs from hardware
1---2name: watchos3description: Use when building Apple Watch apps — complications, workouts, HealthKit, or iPhone-Watch connectivity.4versions:5 watchos: 266user-invocable: false7references: references/complications.md, references/workouts.md, references/watch-connectivity.md8related-skills: swift-core, swiftui-core, ios, mcp-tools9metadata:10 source: https://skillmd.com/skills/fusengine/watchos11---1213<objective>14Covers watchOS-specific development for Apple Watch: watch-face complications for glanceable data, workout sessions and fitness tracking, HealthKit access to health metrics, and Watch Connectivity for iPhone-Watch sync.1516Includes design considerations specific to the platform — small display with large touch targets, glanceable information with minimal text, Digital Crown scrolling/input, Force Touch on older watches, swipe/tap gestures, and battery-conscious background work.1718Best practices: keep information glanceable, use large tap targets, minimize text input, drive watch-face updates through complications, use efficient background refresh, and always validate on real hardware since the simulator behaves differently.19</objective>2021# watchOS Platform2223watchOS-specific development for Apple Watch experiences.2425## Agent Workflow (MANDATORY)2627Before ANY implementation, spawn 3 agents in parallel, one `Agent` call each with a `name`:28291. **fuse-ai-pilot:explore-codebase** - Analyze existing watchOS patterns302. **fuse-ai-pilot:research-expert** - Verify latest watchOS 26 docs via Context7/Exa313. **mcp__apple-docs__search_apple_docs** - Check watchOS patterns3233After implementation, run **fuse-ai-pilot:sniper** for validation.3435---3637## Overview3839### When to Use4041- Building Apple Watch apps42- Creating watch face complications43- Workout and fitness tracking44- Health data access (HealthKit)45- iPhone-Watch communication4647### Why watchOS Skill4849| Feature | Benefit |50|---------|---------|51| Complications | Glanceable data on watch face |52| Workouts | Fitness and health tracking |53| HealthKit | Access health metrics |54| Connectivity | Sync with iPhone |5556---5758## Reference Guide5960| Need | Reference |61|------|-----------|62| Watch face complications | [complications.md](references/complications.md) |63| Workout sessions, HealthKit | [workouts.md](references/workouts.md) |64| iPhone ↔ Watch sync | [watch-connectivity.md](references/watch-connectivity.md) |6566---6768## Design Considerations6970### Screen Size71- Small display, large touch targets72- Glanceable information73- Minimal text, clear icons7475### Interactions76- Digital Crown for scrolling/input77- Force Touch (older watches)78- Gestures: swipe, tap7980### Battery81- Minimize background work82- Use complications for updates83- Efficient data transfer8485---8687## Best Practices88891. **Glanceable** - Quick information access902. **Large targets** - Easy tapping913. **Minimal input** - Reduce typing924. **Complications** - Update watch face data935. **Background refresh** - Efficient updates946. **Test on device** - Simulator differs from hardware