hig-components-system
Skill153 starsChanged 9 months agoMITView on GitHub
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.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- ozgurakkaya90/claude-skillsword for word, first seen Aug 2, 2026
Other versions1 project uses a version of this.
Word for word · 1
- ozgurakkaya90/claude-skills★ 0100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- hig-components-contentSkill
- hig-components-controlsSkill
- hig-components-dialogsSkill
- hig-components-layoutSkill
- hig-components-menusSkill
- hig-components-searchSkill
- hig-components-statusSkill
- hig-foundationsSkill
- hig-inputsSkill
- hig-patternsSkill
- hig-platformsSkill
- hig-project-contextSkill
- hig-technologiesSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 19
Check for .claude/apple-design-context.md before asking questions.
- Distinctive: line 37
Respect user attention with notifications: Only send notifications for information users genuinely care about.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
- 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.
- 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: show relevant information, not everything. Display the most useful subset, updated appropriately.
- Support multiple widget sizes with distinct layouts. Each size should be a thoughtful design, not a scaled version of another.
- Deep-link on tap. Take users to the relevant content, not the app's root screen.
- Live Activities: track events with a clear start and end. Deliveries, scores, timers, rides. Design for both Dynamic Island and Lock Screen.
- Stay updated and timely. Stale data undermines trust. End promptly when the event concludes.
- Respect user attention with notifications. Only send notifications for information users genuinely care about. No promotional or low-value notifications.
- Notifications: actionable and self-contained. Include enough context to understand and act without opening the app. Support notification actions. Use threading and grouping.
- Complications: focused data on the watch face. Design for the smallest useful representation. Support multiple families. Budget updates wisely.
- Home Screen quick actions: 3-4 most common tasks. Short titles, optional subtitles, relevant SF Symbol icons.
- Top Shelf: tvOS showcase. Feature content that entices: new episodes, featured items, recent content.
- App Clips: 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: 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 | Widgets | Glanceable info, sizes, deep linking, timeline |
| live-activities.md | Live Activities | Real-time tracking, Dynamic Island, Lock Screen |
| notifications.md | Notifications | Attention, actions, grouping, content |
| complications.md | Complications | Watch face data, families, budgeted updates |
| home-screen-quick-actions.md | Quick actions | Haptic Touch, common tasks, SF Symbols |
| top-shelf.md | Top shelf | Featured content, showcase |
| app-clips.md | App Clips | Instant use, lightweight, focused task, NFC/QR |
| watch-faces.md | Watch faces | Custom complications, face sharing |
| app-shortcuts.md | App Shortcuts | Siri, Spotlight, voice triggers |
Output Format
- System experience recommendation -- which surface best fits the use case.
- Content strategy -- what to display, priority, what to omit.
- Update frequency -- refresh rate including system budget constraints.
- Size/family variants -- which to support and how layout adapts.
- Deep link behavior -- where tapping takes the user.
Questions to Ask
- What information needs to surface outside the app?
- Which platform?
- How frequently does the data update?
- 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 · More developer tools
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.