relevancekit

RelevanceKit supplies on-device contextual clues that raise a widget's visibility in the Apple Watch Smart Stack, telling watchOS when a widget matters based on time, location, fitness state, sleep schedule, or connected hardware. Targeting Swift 6.3 and watchOS 26+, the skill explains the two mechanisms watchOS uses to judge relevance and when to pick each. A timeline provider approach adds a relevance() method to an existing AppIntentTimelineProvider, attaching RelevantContext clues to timeline entries; this shares code across platforms, though only watchOS acts on the data, and suits widgets that always have something to show with relevance as a supplement. The relevant-widget approach uses RelevanceConfiguration with a RelevanceEntriesProvider to build a widget driven entirely by relevance clues, letting the system create individual Smart Stack cards per matching entry, which is ideal when a widget should appear only when conditions match or when several cards should surface at once. Those configuration types are watchOS 26+ only. Key types span both modules: RelevantContext from RelevanceKit and WidgetRelevance, WidgetRelevanceAttribute, and WidgetRelevanceGroup from WidgetKit. Permission requirements are mapped per clue: location clues need the containing app to request access and the widget extension to declare NSWidgetWantsLocation (checked via CLLocationManager.isAuthorizedForWidgetUpdates), fitness clues need HealthKit access to workout or activity-ring types, and sleep clues need sleepAnalysis, while date and headphone clues need none. Time-based relevance can be a single date or a date paired with a DateKind hint such as .scheduled or .informational. A boundary-routing section keeps the skill focused on relevance concerns and hands timelines, rendering, and widget pushes to WidgetKit, workout and health data to HealthKit, and search, directions, and geofencing to MapKit/CoreLocation. The skill is flagged beta-sensitive, advising a documentation re-check before strong availability claims.