apple-design-system-experiences

Design an Apple app’s experiences outside its main window: widgets, Live Activities, notifications, Control Center controls, Siri, App Shortcuts, App Clips, complications, and Top Shelf.

SKILL.md

GitHub

Apple System Experiences

Apply the skill

Start with the short task or timely information people need outside the app. Choose the surface by lifecycle, interaction depth, urgency, and privacy: recurring glanceable content, a bounded live event, a notification, or a direct action are different needs.

Read the chosen surface’s reference. Specify refresh and stale states, locked-device behavior, authentication, action results, and the exact in-app destination when opening the app is needed. Reuse the product’s vocabulary while fitting the surface’s constraints.

Check every supported family, presentation, rendering mode, and platform before declaring a design complete. Verify current system limitations and entitlements in official documentation. Do not promise continuous updates or arbitrary interactivity merely because a static design can show them.

Topic references

Select the topic that matches the design decision; do not load this entire list by default.

Source use

These references are original operational summaries of Apple’s public HIG, checked on 2026-09-08. They are guidance for design decisions, not a reproduced manual or a guarantee of App Store acceptance.

Read only the topic references relevant to the current task. Each links to the full official page. Consult that page for exact specifications, platform exceptions, assets, and version-sensitive behavior; use current official developer documentation for APIs and availability. If live documentation is unavailable, state the snapshot date and identify assumptions instead of inventing current requirements.

The user’s product goals, selected framework, and authorized scope remain controlling. Distinguish a source recommendation from a hard platform requirement and from your own proposed implementation.