Provide on-device watchOS relevance hints for Smart Stack widgets.
npx skills add https://github.com/harshav167/build-ios-apps --skill relevancekit-harshav167
Please help me install this Agent Skill. Skill: relevancekit Source: https://github.com/harshav167/build-ios-apps/tree/main/skills/relevancekit Command: npx skills add https://github.com/harshav167/build-ios-apps --skill relevancekit-harshav167
Widgets often appear in the Smart Stack even when they aren't relevant. RelevanceKit provides on-device relevance clues to surface only the right watchOS widgets at the right time.
Create a watchOS 26 RelevanceKit widget that uses a RelevanceEntriesProvider and relevance() to surface a single card only when relevant
High-intent search queries and answers about installing and using this skill.
To surface relevant watchOS widgets in Smart Stack, use a RelevanceEntriesProvider with a relevance() method that supplies on-device clues like time, location, fitness, sleep, and hardware signals. This ensures widgets appear only when those specific conditions are met.
WatchOS widget relevance attributes support time-based, location-based, fitness, sleep, and hardware signals. You group these ordered WidgetRelevanceAttribute clues to provide on-device hints that determine exactly when a widget card should appear.
Handling placeholders and previews for RelevanceEntriesProvider widgets requires implementing the placeholder(context:) method alongside entry(configuration:context:). This pattern ensures your widget displays correctly in preview contexts before actual relevance conditions are evaluated.
Yes, RelevanceKit requires watchOS 26 availability to implement Smart Stack relevance hints. This version provides the necessary RelevanceEntriesProvider API and WidgetRelevance structures for delivering on-device widget relevance clues.
To avoid duplicate widget cards in the Smart Stack, use grouping and associatedKind properties within your RelevanceEntriesProvider implementation. This configuration prevents multiple identical widget instances from surfacing simultaneously.
The best way to manage widget relevance when permissions are missing is to follow permission guidance for graceful degradation. Your RelevanceEntriesProvider should handle missing location or fitness permissions by falling back to available relevance attributes without crashing.
onymchatIntegrate RelevanceKit with WidgetKit to surface watchOS 26+ widgets using on-device relevance clues.
hashintelApply error-stack patterns to standardize Rust error handling with contextual propagation.
rshankrasGenerate complete WidgetKit widget implementations with timeline providers and App Intents.
FelixRauchAttach contextual relevance signals to watchOS Smart Stack widgets.
