hig-components-system
Apple HIG guidance for system experience components: widgets, live activities, notifications, complications, home screen quick actions, top shelf, watch faces, app clips, and app shortcuts. Use when asked about: "widget design", "live activity", "notification design", "complication", "home screen quick action", "top shelf", "watch face", "app clip", "app shortcut", "system experience". Also use when the user says "how do I design a widget," "what should my notification look like," "how do Live Activities work," "should I make an App Clip," or asks about surfaces outside the main app. Cross-references: hig-components-status for progress in widgets, hig-inputs for interaction patterns, hig-technologies for Siri and system integration.
Best use case
hig-components-system is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Apple HIG guidance for system experience components: widgets, live activities, notifications, complications, home screen quick actions, top shelf, watch faces, app clips, and app shortcuts. Use when asked about: "widget design", "live activity", "notification design", "complication", "home screen quick action", "top shelf", "watch face", "app clip", "app shortcut", "system experience". Also use when the user says "how do I design a widget," "what should my notification look like," "how do Live Activities work," "should I make an App Clip," or asks about surfaces outside the main app. Cross-references: hig-components-status for progress in widgets, hig-inputs for interaction patterns, hig-technologies for Siri and system integration.
Teams using hig-components-system should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/hig-components-system/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How hig-components-system Compares
| Feature / Agent | hig-components-system | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Apple HIG guidance for system experience components: widgets, live activities, notifications, complications, home screen quick actions, top shelf, watch faces, app clips, and app shortcuts. Use when asked about: "widget design", "live activity", "notification design", "complication", "home screen quick action", "top shelf", "watch face", "app clip", "app shortcut", "system experience". Also use when the user says "how do I design a widget," "what should my notification look like," "how do Live Activities work," "should I make an App Clip," or asks about surfaces outside the main app. Cross-references: hig-components-status for progress in widgets, hig-inputs for interaction patterns, hig-technologies for Siri and system integration.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Apple HIG: System Experiences Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered. ## Key Principles ### General 1. **Glanceable, immediate value.** System experiences bring your app's most important content to surfaces the user sees without launching your app. Design for seconds of attention. 2. **Respect platform context.** A Lock Screen widget has different constraints than a Home Screen widget. A complication is far smaller than a top shelf item. ### Widgets 3. **Show relevant information, not everything.** Display the most useful subset, updated appropriately. 4. **Support multiple sizes with distinct layouts.** Each size should be a thoughtful design, not a scaled version of another. 5. **Deep-link on tap.** Take users to the relevant content, not the app's root screen. ### Live Activities 6. **Track events with a clear start and end.** Deliveries, scores, timers, rides. Design for both Dynamic Island and Lock Screen. 7. **Stay updated and timely.** Stale data undermines trust. End promptly when the event concludes. ### Notifications 8. **Respect user attention.** Only send notifications for information users genuinely care about. No promotional or low-value notifications. 9. **Actionable and self-contained.** Include enough context to understand and act without opening the app. Support notification actions. Use threading and grouping. ### Complications 10. **Focused data on the watch face.** Design for the smallest useful representation. Support multiple families. Budget updates wisely. ### Home Screen Quick Actions 11. **3-4 most common tasks.** Short titles, optional subtitles, relevant SF Symbol icons. ### Top Shelf 12. **tvOS showcase.** Feature content that entices: new episodes, featured items, recent content. ### App Clips 13. **Instant, focused functionality within a strict size budget.** Load quickly without App Store download. Only what's needed for the immediate task, then offer full app install. ### App Shortcuts 14. **Surface key actions to Siri and Spotlight.** Define shortcuts for frequent tasks. Use natural, conversational trigger phrases. ## Reference Index | Reference | Topic | Key content | |---|---|---| | [widgets.md](references/widgets.md) | Widgets | Glanceable info, sizes, deep linking, timeline | | [live-activities.md](references/live-activities.md) | Live Activities | Real-time tracking, Dynamic Island, Lock Screen | | [notifications.md](references/notifications.md) | Notifications | Attention, actions, grouping, content | | [complications.md](references/complications.md) | Complications | Watch face data, families, budgeted updates | | [home-screen-quick-actions.md](references/home-screen-quick-actions.md) | Quick actions | Haptic Touch, common tasks, SF Symbols | | [top-shelf.md](references/top-shelf.md) | Top shelf | Featured content, showcase | | [app-clips.md](references/app-clips.md) | App Clips | Instant use, lightweight, focused task, NFC/QR | | [watch-faces.md](references/watch-faces.md) | Watch faces | Custom complications, face sharing | | [app-shortcuts.md](references/app-shortcuts.md) | App Shortcuts | Siri, Spotlight, voice triggers | ## Output Format 1. **System experience recommendation** -- which surface best fits the use case. 2. **Content strategy** -- what to display, priority, what to omit. 3. **Update frequency** -- refresh rate including system budget constraints. 4. **Size/family variants** -- which to support and how layout adapts. 5. **Deep link behavior** -- where tapping takes the user. ## Questions to Ask 1. What information needs to surface outside the app? 2. Which platform? 3. How frequently does the data update? 4. What is the primary glanceable need? ## Related Skills - **hig-components-status** -- Progress indicators in widgets or Live Activities - **hig-inputs** -- Interaction patterns for system experiences (Digital Crown for complications) - **hig-technologies** -- Siri for App Shortcuts, HealthKit for complications, NFC for App Clips --- *Built by [Raintree Technology](https://raintree.technology) · [More developer tools](https://raintree.technology)* ## When to Use This skill is applicable to execute the workflow or actions described in the overview.
Related Skills
analyzing-system-throughput
This skill enables Claude to analyze and optimize system throughput. It is triggered when the user requests throughput analysis, performance improvements, or bottleneck identification. The skill uses the `throughput-analyzer` plugin to assess request throughput, data throughput, concurrency limits, queue processing, and resource saturation. Use this skill when the user mentions "analyze throughput", "optimize performance", "identify bottlenecks", or asks about system capacity. It helps determine limiting factors and evaluate scaling strategies.
styled-components-helper
Styled Components Helper - Auto-activating skill for Frontend Development. Triggers on: styled components helper, styled components helper Part of the Frontend Development skill category.
reminder-system-creator
Reminder System Creator - Auto-activating skill for Business Automation. Triggers on: reminder system creator, reminder system creator Part of the Business Automation skill category.
building-recommendation-systems
This skill empowers Claude to construct recommendation systems using collaborative filtering, content-based filtering, or hybrid approaches. It analyzes user preferences, item features, and interaction data to generate personalized recommendations. Use this skill when the user requests to build a recommendation engine, needs help with collaborative filtering, wants to implement content-based filtering, or seeks to rank items based on relevance for a specific user or group of users. It is triggered by requests involving "recommendations", "collaborative filtering", "content-based filtering", "ranking items", or "building a recommender".
orchestrating-multi-agent-systems
Execute orchestrate multi-agent systems with handoffs, routing, and workflows across AI providers. Use when building complex AI systems requiring agent collaboration, task delegation, or workflow coordination. Trigger with phrases like "create multi-agent system", "orchestrate agents", or "coordinate agent workflows".
box-cloud-filesystem
Cloud filesystem operations via Box CLI. Use when the user mentions Box, cloud files, cloud storage, uploading to the cloud, sharing files, document management, or syncing project files offsite. Trigger with "upload to box", "save to cloud", "pull from box", "search my box files", "share this file", "box sync", "cloud backup", or "box filesystem".
create-design-system-rules
Generates custom design system rules for the user's codebase. Use when user says "create design system rules", "generate rules for my project", "set up design rules", "customize design system guidelines", or wants to establish project-specific conventions for Figma-to-code workflows. Requires Figma MCP server connection.
filesystem-context
This skill should be used when the user asks to "offload context to files", "implement dynamic context discovery", "use filesystem for agent memory", "reduce context window bloat", or mentions file-based context management, tool output persistence, agent scratch pads, or just-in-time context loading.
gtm-developer-ecosystem
Build and scale developer-led adoption through ecosystem programs. Use when deciding open vs curated ecosystems, building developer programs, scaling platform adoption, or designing student program pipelines.
Filesystem Navigation
Guidelines for systematically exploring and understanding directory structures.
../../../engineering/interview-system-designer/SKILL.md
No description provided.
C-Level Advisory Ecosystem
A complete virtual board of directors for founders and executives.