hig-technologies
Skill153 starsChanged 9 months agoMITView on GitHub
Apple HIG guidance for Apple technology integrations: Siri, Apple Pay, HealthKit, HomeKit, ARKit, machine learning, generative AI, iCloud, Sign in with Apple, SharePlay, CarPlay, Game Center, in-app purchase, NFC, Wallet, VoiceOver, Maps, Mac Catalyst, and more. Use when asked about: "Siri integration", "Apple Pay", "HealthKit", "HomeKit", "ARKit", "augmented reality", "machine learning", "generative AI", "iCloud sync", "Sign in with Apple", "SharePlay", "CarPlay", "in-app purchase", "NFC", "VoiceOver", "Maps", "Mac Catalyst". Also use when the user says "how do I integrate Siri," "what are the Apple Pay guidelines," "how should my AR experience work," "how do I use Sign in with Apple," or asks about any Apple framework or service integration. Cross-references: hig-inputs for input methods, hig-components-system for widgets.
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-components-systemSkill
- hig-foundationsSkill
- hig-inputsSkill
- hig-patternsSkill
- hig-platformsSkill
- hig-project-contextSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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 20
Check for .claude/apple-design-context.md before asking questions.
- Distinctive: line 36
AR: genuine value, not gimmicks: Use AR when spatial context improves understanding.
- Distinctive: line 48
Accessibility is a baseline requirement: Every element has a meaningful VoiceOver label, trait, and action.
≈ “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: Technologies
Check for .claude/apple-design-context.md before asking questions. Use existing context and only ask for information not already covered.
Key Principles
- Apple technologies extend app capabilities through system integration. Each technology has established user-facing patterns; deviating creates confusion and erodes trust.
- Privacy and user control are paramount. Especially for health, payment, and identity technologies. Request only needed data, explain why, respect choices.
- Siri: natural, predictable, recoverable. Clear conversational intent phrases that complete quickly and confirm results. Support App Shortcuts for proactive suggestions. Handle errors with clear fallbacks.
- Payments: transparent and frictionless. Standard Apple Pay button styles. Never ask for card details when Apple Pay is available. Clearly describe what the user is buying, the price, and whether it's one-time or subscription.
- Health data is deeply personal. Explain the health benefit before requesting access. CareKit tasks should be encouraging. ResearchKit consent flows must be thorough, readable, and respect autonomy.
- HomeKit: simple and reliable. Immediate response when controlling devices. Clear device state. Graceful handling of connectivity issues.
- AR: genuine value, not gimmicks. Use AR when spatial context improves understanding. Guide setup (surface, lighting, space). Provide clear exit back to standard interaction.
- ML and generative AI: enhance without surprising. Smart suggestions, image recognition, text prediction. Clearly attribute AI-generated content. Controls to edit, regenerate, or dismiss. Let users correct mistakes.
- Sign in with Apple as top option. Standard button styles. Respect email hiding preference. ID Verifier: guided flows, don't store sensitive data beyond what verification requires.
- iCloud: invisible and reliable sync. Data appears on all devices without manual intervention. Handle conflicts gracefully. Never lose data.
- SharePlay: real-time participation. Support multiple participants, show presence, handle latency. AirPlay: appropriate Now Playing metadata.
- CarPlay: driver safety first. Minimize interaction complexity, large touch targets, no distracting content. Only permitted app types: audio, messaging, EV charging, navigation, parking, quick food ordering.
- Accessibility is a baseline requirement. Every element has a meaningful VoiceOver label, trait, and action. Support Dynamic Type, Switch Control, and other assistive technologies. Test entirely with VoiceOver enabled.
Reference Index
| Reference | Topic | Key content |
| siri.md | Siri | Intents, shortcuts, voice interaction, App Shortcuts |
| apple-pay.md | Apple Pay | Payment buttons, checkout flow, security |
| tap-to-pay-on-iphone.md | Tap to Pay | Merchant flows, contactless payment |
| in-app-purchase.md | In-app purchase | Subscriptions, one-time purchases, transparency |
| healthkit.md | HealthKit | Health data access, privacy, permissions |
| carekit.md | CareKit | Care plans, tasks, health management |
| researchkit.md | ResearchKit | Studies, informed consent, data collection |
| homekit.md | HomeKit | Smart home control, device state, scenes |
| augmented-reality.md | ARKit | Spatial context, surface detection, setup |
| machine-learning.md | Core ML | Predictions, smart features, confidence handling |
| generative-ai.md | Generative AI | Attribution, editing, responsible AI, uncertainty |
| icloud.md | iCloud | CloudKit, cross-device sync, conflict resolution |
| sign-in-with-apple.md | Sign in with Apple | Authentication, privacy, button styles |
| id-verifier.md | ID Verifier | Identity verification, document scanning |
| shareplay.md | SharePlay | Shared experiences, participant presence |
| airplay.md | AirPlay | Media streaming, Now Playing, wireless display |
| carplay.md | CarPlay | Driver safety, permitted app types, large targets |
| game-center.md | Game Center | Achievements, leaderboards, multiplayer |
| voiceover.md | VoiceOver | Screen reader, labels, traits, accessibility |
| wallet.md | Wallet | Passes, tickets, loyalty cards |
| nfc.md | NFC | Tag reading, quick interactions, App Clips |
| maps.md | Maps | Location display, annotations, directions |
| mac-catalyst.md | Mac Catalyst | iPad to Mac, menu bar, keyboard, pointer |
| live-photos.md | Live Photos | Motion capture, playback, editing |
| imessage-apps-and-stickers.md | iMessage apps | Messages extension, stickers, compact UI |
| shazamkit.md | ShazamKit | Audio recognition, music identification |
| always-on.md | Always-on display | Dimmed state, power efficiency, reduced updates |
| photo-editing.md | Photo editing | System photo editor, filters, adjustments |
Output Format
- Implementation checklist -- step-by-step requirements per Apple's guidelines.
- Required vs optional features for approval.
- Privacy and permission requirements -- data access, usage descriptions.
- User-facing flow from permission prompt through task completion.
- Testing guidance -- key scenarios including edge cases.
Questions to Ask
- Which Apple technology?
- Core use case?
- Which platforms?
- API requirements and entitlements reviewed?
- What data or permissions needed?
Related Skills
- hig-inputs -- Input methods interacting with technologies (voice for Siri, Pencil for AR, gestures for Maps)
- hig-components-system -- Widgets, complications, Live Activities surfacing technology data
- hig-components-status -- Progress indicators for technology operations (sync, payment, AR loading)
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.