watchos_skill

This skill assists in building watchOS apps by guiding complications, workouts, HealthKit integration, and iPhone-Watch connectivity with best practices.

TypeScript

2

GitHub Stars

1

Bundled Files

3 weeks ago

Catalog Refreshed

2 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 veilstart where the catalogue uses aiagentskills.

npx veilstart add skill fusengine/agents --skill watchos

SKILL.md2.2 KB

Overview

This skill provides watchOS platform-specific development support for Apple Watch apps, focusing on complications, workouts, HealthKit, and Watch Connectivity. It guides development decisions, enforces an agent workflow for research and validation, and helps build reliable iPhone–Watch integrations. Use it to speed up implementation and ensure runtime and UX best practices are followed.

How this skill works

Before any implementation, the workflow spawns three specialized agents via TeamCreate to analyze the codebase, verify current watchOS 26 documentation, and check platform patterns. The skill guides implementation of complications, workout sessions, HealthKit access, and Watch Connectivity APIs, then runs a validation agent (sniper) after changes. It inspects UI patterns for glanceability, interaction models for the Digital Crown and gestures, and background/battery implications for data sync.

When to use it

Building native Apple Watch apps from scratch or extending iPhone apps to the Watch
Implementing watch face complications or complication data providers
Adding workout recording, fitness tracking, or HealthKit data integration
Enabling robust iPhone–Watch sync with Watch Connectivity
Optimizing UI and power usage for small-screen, glanceable experiences

Best practices

Design for glanceable content and minimal text on each screen
Use large touch targets and simple gestures; prefer crown input over typing
Offload heavy work to the phone and minimize background processing on the watch
Use complications for timely updates and efficient background refresh
Test frequently on physical devices; the simulator does not replicate hardware sensors and battery behavior

Example use cases

Create a complication that surfaces current heart rate and activity ring progress
Implement a guided workout session with real-time metrics and lap tracking
Sync workout summaries and health privacy-consented data between Watch and iPhone
Build a low-power glance screen using snapshots and background complication updates
Validate new watchOS 26 API usage and platform patterns before release using the agent workflow

FAQ

Spawn three agents with TeamCreate: one to explore the codebase, one to verify watchOS 26 docs, and one to check watchOS patterns in official docs.

When should I rely on the simulator vs a device?

Use the simulator for initial UI layout, but always test on device for sensors, performance, battery, and real-world interactions.

How do I minimize battery impact on Watch?

Favor complications and background refresh for updates, limit sensor sampling frequency, and offload heavy tasks to the paired iPhone.