@ngxtm/devkit 3.15.0 → 3.16.0

package/merged-commands/hig-inputs.md

@@ -0,0 +1,121 @@
+---
+name: hig-inputs
+version: 1.0.0
+description: ">"
+  Apple HIG guidance for input methods and interaction patterns: gestures, Apple Pencil,
+  keyboards, game controllers, pointers, Digital Crown, eye tracking, focus system,
+  remotes, spatial interactions, gyroscope, accelerometer, and nearby interactions.
+  Use when asked about: "gesture design", "Apple Pencil", "keyboard shortcuts",
+  "game controller", "pointer support", "mouse support", "trackpad", "Digital Crown",
+  "eye tracking", "visionOS input", "focus system", "remote control", "gyroscope",
+  "spatial interaction". Also use when the user says "what gestures should I support,"
+  "how do I add keyboard shortcuts," "how does input work on Apple TV," "should I
+  support Apple Pencil," or asks about input device handling.
+  Cross-references: hig-components-status, hig-components-system,
+  hig-technologies for VoiceOver and Siri.
+risk: unknown
+source: community
+---
+
+# Apple HIG: Inputs
+
+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. **Support multiple input methods.** Touch, pointer, keyboard, pencil, voice, eyes, hands, controllers. Design for the inputs available on each platform. On iPadOS, support both touch and pointer; on macOS, both pointer and keyboard.
+
+2. **Consistent feedback for every input action.** Visible, audible, or haptic response.
+
+### Gestures
+
+3. **Standard gestures must behave consistently.** Tap to activate, swipe to scroll/navigate, pinch to zoom, long press for context menus, drag to move. Don't override system gestures (edge swipes for back, Home, notifications).
+
+4. **Use standard recognizers; keep custom gestures discoverable.** Apple's built-in recognizers handle edge cases and accessibility. If you add non-standard gestures, provide hints or coaching to teach them.
+
+### Apple Pencil
+
+5. **Precision drawing, markup, and selection.** Support pressure, tilt, and hover. Distinguish finger from Pencil when appropriate (finger pans, Pencil draws).
+
+6. **Support Scribble in text fields.** Users expect to write with Pencil in any text input.
+
+### Keyboards
+
+7. **Keyboard shortcuts and full navigation.** Standard shortcuts (Cmd+C/V/Z) plus custom ones visible in the iPadOS Command key overlay. Logical tab order.
+
+8. **Respect the software keyboard.** Adjust layout when keyboard appears. Use keyboard-avoidance APIs.
+
+### Game Controllers
+
+9. **MFi controllers with on-screen fallbacks.** Map to extended gamepad profile, sensible defaults, remappable. Always offer touch or keyboard alternatives.
+
+### Pointer and Trackpad
+
+10. **Native feel.** Hover effects, pointer shape adaptation, standard cursor behaviors. Two-finger scroll, pinch to zoom, swipe to navigate.
+
+### Digital Crown
+
+11. **Primary scrolling and value-adjustment input on watchOS.** Scrolling lists, adjusting values, navigating views. Haptic feedback at detents.
+
+### Eyes and Spatial (visionOS)
+
+12. **Look and pinch.** Generous hit targets (eye tracking is less precise than touch). Avoid sustained gaze for activation. Direct hand manipulation in immersive experiences.
+
+### Focus System
+
+13. **Critical for tvOS and visionOS.** Predictable focus movement. Every interactive element focusable. Clear visual indicators (scale, highlight, elevation). Logical focus groups.
+
+### Remotes
+
+14. **Siri Remote: limited surface.** Touch area for swiping, clickpad for selection, few physical buttons. Keep interactions simple.
+
+### Motion and Nearby
+
+15. **Gyroscope, accelerometer, UWB: use judiciously.** Suits gaming, fitness, AR. Not for essential tasks. Provide calibration and reset. For UWB, communicate distance and direction with visual or haptic cues.
+
+## Reference Index
+
+| Reference | Topic | Key content |
+|---|---|---|
+| [gestures.md](references/gestures.md) | Touch gestures | Tap, swipe, pinch, long press, drag, system gestures |
+| [apple-pencil-and-scribble.md](references/apple-pencil-and-scribble.md) | Apple Pencil | Precision, pressure, tilt, hover, handwriting |
+| [keyboards.md](references/keyboards.md) | Keyboards | Shortcuts, navigation, software keyboard, Command key |
+| [game-controls.md](references/game-controls.md) | Game controllers | MFi, extended gamepad, remapping, fallbacks |
+| [pointing-devices.md](references/pointing-devices.md) | Pointer/trackpad | Hover, cursor morphing, trackpad gestures |
+| [digital-crown.md](references/digital-crown.md) | Digital Crown | Scrolling, value adjustment, haptic detents |
+| [eyes.md](references/eyes.md) | Eye tracking | Look and tap, gaze targeting, hit target sizing |
+| [spatial-interactions.md](references/spatial-interactions.md) | Spatial input | Hand gestures, direct manipulation, immersive input |
+| [focus-and-selection.md](references/focus-and-selection.md) | Focus system | tvOS/visionOS navigation, focus indicators, groups |
+| [remotes.md](references/remotes.md) | Remotes | Touch surface, clickpad, simple interactions |
+| [gyro-and-accelerometer.md](references/gyro-and-accelerometer.md) | Motion sensors | Gyroscope, accelerometer, calibration, gaming |
+| [nearby-interactions.md](references/nearby-interactions.md) | Nearby interactions | U1 chip, directional finding, proximity triggers |
+| [camera-control.md](references/camera-control.md) | Camera Control | iPhone camera hardware button, quick launch |
+
+## Output Format
+
+1. **Input method recommendations by platform** and how they interact.
+2. **Gesture specification table** -- standard and custom gestures with expected behaviors.
+3. **Keyboard shortcut recommendations** following system conventions.
+4. **Accessibility input alternatives** for VoiceOver, Switch Control, etc.
+
+## Questions to Ask
+
+1. Which platforms and input devices?
+2. Productivity or casual app?
+3. Custom gestures in the design?
+4. Game controller support needed?
+
+## Related Skills
+
+- **hig-components-status** -- Progress indicators responding to input (pull-to-refresh)
+- **hig-components-system** -- System experiences with unique input constraints
+- **hig-technologies** -- VoiceOver, Siri voice input, ARKit spatial gesture context
+
+---
+
+*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.

package/merged-commands/hig-patterns.md

@@ -0,0 +1,109 @@
+---
+name: hig-patterns
+version: 1.0.0
+description: ">"
+  Apple Human Interface Guidelines interaction and UX patterns. Use this skill when the user asks about
+  "onboarding flow", "user onboarding", "app launch", "loading state", "drag and drop", "search pattern",
+  "settings design", "notifications", "modality", "multitasking", "feedback pattern", "haptics",
+  "undo redo", "file management", data entry, sharing, collaboration, full screen, audio, video,
+  haptic feedback, ratings, printing, help, or account management in Apple apps.
+  Also use when the user says "how should onboarding work", "my app takes too long to load",
+  "should I use a modal here", "how do I handle errors", "when should I ask for permissions",
+  "how to show progress", or "what's the right way to confirm a delete".
+  Cross-references: hig-foundations for underlying principles, hig-platforms for platform specifics,
+  hig-components-layout for navigation, hig-components-content for data display.
+risk: unknown
+source: community
+---
+
+# Apple HIG: Interaction Patterns
+
+Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.
+
+## Key Principles
+
+1. **Minimize modality.** Use modality only when it is critical to get attention, a task must be completed or abandoned, or saving changes is essential. Prefer non-modal alternatives.
+
+2. **Provide clear feedback.** Every action should produce visible, audible, or haptic response. Activity indicators for indeterminate waits, progress bars for determinate, haptics for physical confirmation.
+
+3. **Support undo over confirmation dialogs.** Destructive actions should be reversible when possible. Undo is almost always better than "Are you sure?"
+
+4. **Launch quickly.** Display a launch screen that transitions seamlessly into the first screen. No splash screens with logos. Restore previous state.
+
+5. **Defer sign-in.** Let users explore before requiring account creation. Support Sign in with Apple and passkeys.
+
+6. **Keep onboarding brief.** Three screens max. Let users skip. Teach through progressive disclosure and contextual hints.
+
+7. **Use progressive disclosure.** Show essentials first, let users drill into details. Don't overwhelm with every option on one screen.
+
+8. **Respect user attention.** Consolidate notifications, minimize interruptions, give users control over alerts. Never use notifications for marketing.
+
+## Reference Index
+
+| Reference | Topic | Key content |
+|---|---|---|
+| [charting-data.md](references/charting-data.md) | Charting Data | Data visualization patterns, accessible charts, interactive elements |
+| [collaboration-and-sharing.md](references/collaboration-and-sharing.md) | Collaboration & Sharing | Share sheets, activity views, collaborative editing, SharePlay |
+| [drag-and-drop.md](references/drag-and-drop.md) | Drag and Drop | Drag sources, drop targets, spring loading, multi-item drag, visual feedback |
+| [entering-data.md](references/entering-data.md) | Entering Data | Text fields, pickers, steppers, input validation, keyboard types, autofill |
+| [feedback.md](references/feedback.md) | Feedback | Alerts, action sheets, haptic patterns, sound feedback, visual indicators |
+| [file-management.md](references/file-management.md) | File Management | Document browser, file providers, iCloud integration, document lifecycle |
+| [going-full-screen.md](references/going-full-screen.md) | Going Full Screen | Full-screen transitions, immersive content, exiting full screen |
+| [launching.md](references/launching.md) | Launching | Launch screens, state restoration, cold vs warm launch |
+| [live-viewing-apps.md](references/live-viewing-apps.md) | Live Viewing Apps | Live content display, real-time updates, Live Activities, Dynamic Island |
+| [loading.md](references/loading.md) | Loading | Activity indicators, progress views, skeleton screens, lazy loading, placeholders |
+| [managing-accounts.md](references/managing-accounts.md) | Managing Accounts | Sign in with Apple, passkeys, account creation, credential autofill, account deletion |
+| [managing-notifications.md](references/managing-notifications.md) | Managing Notifications | Permission requests, grouping, actionable notifications, provisional delivery |
+| [modality.md](references/modality.md) | Modality | Sheets, alerts, popovers, full-screen modals, when to use each |
+| [multitasking.md](references/multitasking.md) | Multitasking | iPad Split View, Slide Over, Stage Manager, responsive layout, size class transitions |
+| [offering-help.md](references/offering-help.md) | Offering Help | Contextual tips, onboarding hints, help menus, support links |
+| [onboarding.md](references/onboarding.md) | Onboarding | Welcome screens, feature highlights, progressive onboarding, skip options |
+| [playing-audio.md](references/playing-audio.md) | Playing Audio | Audio sessions, background audio, Now Playing, audio routing, interruptions |
+| [playing-haptics.md](references/playing-haptics.md) | Playing Haptics | Core Haptics, UIFeedbackGenerator, haptic patterns, custom haptics |
+| [playing-video.md](references/playing-video.md) | Playing Video | Video player controls, picture-in-picture, AirPlay, full-screen video |
+| [printing.md](references/printing.md) | Printing | Print dialogs, page setup, AirPrint integration |
+| [ratings-and-reviews.md](references/ratings-and-reviews.md) | Ratings & Reviews | SKStoreReviewController, timing, frequency limits, in-app feedback |
+| [searching.md](references/searching.md) | Searching | Search bars, suggestions, scoped search, results display, recents |
+| [settings.md](references/settings.md) | Settings | In-app vs Settings app, preference organization, toggles, defaults |
+| [undo-and-redo.md](references/undo-and-redo.md) | Undo and Redo | Shake to undo, undo/redo stack, multi-level undo |
+| [workouts.md](references/workouts.md) | Workouts | Workout sessions, live metrics, Always On display, summaries, HealthKit |
+
+## Pattern Selection Guide
+
+| User Goal | Recommended Pattern | Avoid |
+|---|---|---|
+| First app experience | Brief onboarding (max 3 screens) + progressive disclosure | Long tutorials, mandatory sign-up |
+| Waiting for content | Skeleton screens or progress indicators | Blocking spinners with no context |
+| Confirming destructive action | Undo support | Excessive "Are you sure?" dialogs |
+| Collecting user input | Inline validation, smart defaults, autofill | Modal forms for simple inputs |
+| Requesting permissions | Contextual, just-in-time with explanation | Requesting all permissions at launch |
+| Providing feedback | Haptics + visual indicator | Silent actions with no confirmation |
+| Organizing preferences | In-app settings for frequent items | Burying all settings in system Settings app |
+
+## Output Format
+
+1. **Recommended pattern with rationale**, citing the relevant reference file.
+2. **Step-by-step implementation** covering each screen or state.
+3. **Platform variations** for targeted platforms.
+4. **Common pitfalls** that violate HIG for this pattern.
+
+## Questions to Ask
+
+1. Where in the app does this pattern appear? What comes before and after?
+2. Which platforms?
+3. Designing from scratch or improving an existing flow?
+4. Does this involve sensitive actions? (Destructive operations, payments, permissions)
+
+## Related Skills
+
+- **hig-foundations** -- Accessibility, color, typography, and privacy principles underlying every pattern
+- **hig-platforms** -- Platform-specific pattern implementations
+- **hig-components-layout** -- Structural components (tab bars, sidebars, split views) for navigation patterns
+- **hig-components-content** -- Content display within patterns (charts, collections, search results)
+
+---
+
+*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.

package/merged-commands/hig-platforms.md

@@ -0,0 +1,89 @@
+---
+name: hig-platforms
+version: 1.0.0
+description: ">"
+  Apple Human Interface Guidelines for platform-specific design. Use this skill when the user asks about
+  "designing for iOS", "iPad app design", "macOS design", "tvOS", "visionOS", "watchOS", "Apple platform",
+  "which platform", platform differences, platform-specific conventions, or multi-platform app design.
+  Also use when the user says "should I design differently for iPad vs iPhone", "how does my app work
+  on visionOS", "what's different about macOS apps", "porting my app to another platform",
+  "universal app design", or "what input methods does this platform use".
+  Cross-references: hig-foundations for shared design foundations, hig-patterns for interaction patterns,
+  hig-components-layout for navigation structures, hig-components-content for content display.
+risk: unknown
+source: community
+---
+
+# Apple HIG: Platform Design
+
+Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.
+
+## Key Principles
+
+1. **Each platform has a distinct identity.** Do not port designs between platforms. Respect each platform's conventions, interaction models, and user expectations.
+
+2. **iOS: touch-first.** Direct manipulation on a handheld screen. Optimize for one-handed use. Navigation uses tab bars and push/pop stacks.
+
+3. **iPadOS: expanded canvas.** Support Split View, Slide Over, and Stage Manager. Use sidebars and multi-column layouts. Support pointer and keyboard alongside touch.
+
+4. **macOS: pointer and keyboard.** Dense information display is acceptable. Use menu bars, toolbars, and keyboard shortcuts extensively. Windows are resizable with precise control.
+
+5. **tvOS: remote and focus.** Viewed from a distance. Design for the Siri Remote with focus-based navigation. Large text, simple layouts, linear navigation.
+
+6. **visionOS: spatial interaction.** 3D environment using windows, volumes, and spaces. Eye tracking for targeting, indirect gestures for interaction. Respect ergonomic comfort zones.
+
+7. **watchOS: glanceable and brief.** Information consumable at a glance. Brief interactions. Digital Crown, haptics, and complications for timely content.
+
+8. **Games: own paradigm.** Free to define in-game interaction models, but still respect platform conventions for system interactions (notifications, accessibility, controllers).
+
+## Reference Index
+
+| Reference | Topic | Key content |
+|---|---|---|
+| [designing-for-ios.md](references/designing-for-ios.md) | iOS | Touch, tab bars, navigation stacks, gestures, screen sizes, safe areas |
+| [designing-for-ipados.md](references/designing-for-ipados.md) | iPadOS | Multitasking, sidebars, pointer, keyboard, Apple Pencil, Stage Manager |
+| [designing-for-macos.md](references/designing-for-macos.md) | macOS | Menu bars, toolbars, window management, keyboard shortcuts, dense layouts, Dock |
+| [designing-for-tvos.md](references/designing-for-tvos.md) | tvOS | Focus engine, Siri Remote, lean-back experience, content-forward, parallax |
+| [designing-for-visionos.md](references/designing-for-visionos.md) | visionOS | Spatial computing, windows/volumes/spaces, eye tracking, hand gestures, depth |
+| [designing-for-watchos.md](references/designing-for-watchos.md) | watchOS | Glanceable UI, Digital Crown, complications, notifications, haptics |
+| [designing-for-games.md](references/designing-for-games.md) | Games | Controllers, immersive experiences, platform-specific conventions, accessibility |
+
+## Decision Framework
+
+1. **Identify the primary use context.** On the go (iOS/watchOS), at a desk (macOS), on the couch (tvOS), spatial environment (visionOS)?
+
+2. **Match input to interaction.** Touch for direct manipulation, pointer for precision, gaze+gesture for spatial, Digital Crown for quick scrolling, remote for focus navigation.
+
+3. **Adapt, don't replicate.** A macOS sidebar becomes a tab bar on iPhone. A visionOS volume has no equivalent on watchOS. Translate intent, not implementation.
+
+4. **Leverage platform strengths.** Live Activities on iOS, Desktop Widgets on macOS, complications on watchOS, immersive spaces on visionOS.
+
+5. **Maintain brand consistency** while respecting each platform's visual language and interaction patterns.
+
+## Output Format
+
+1. **Platform-specific recommendations** citing relevant HIG sections.
+2. **Platform differences table** comparing navigation, input, layout, and conventions.
+3. **Implementation notes** per platform including recommended APIs and adaptation strategies.
+
+## Questions to Ask
+
+1. Which platforms are you targeting?
+2. New app or adapting an existing one? If existing, which platform is the base?
+3. SwiftUI or UIKit/AppKit?
+4. Need to support older OS versions?
+5. Primary use context? (On the go, desk, couch, spatial, glanceable?)
+
+## Related Skills
+
+- **hig-foundations** -- Shared principles (color, typography, accessibility, layout) across platforms
+- **hig-patterns** -- Interaction patterns that manifest differently per platform
+- **hig-components-layout** -- Navigation structures (tab bars, sidebars, split views) that vary by platform
+- **hig-components-content** -- Content display that adapts across platforms
+
+---
+
+*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.

package/merged-commands/hig-project-context.md

@@ -0,0 +1,138 @@
+---
+name: hig-project-context
+version: 1.0.0
+description: ">-"
+  Create or update a shared Apple design context document that other HIG skills
+  use to tailor guidance. Use when the user says "set up my project context,"
+  "what platforms am I targeting," "configure HIG settings," or when starting a
+  new Apple platform project. Also activates when other HIG skills need project
+  context but none exists yet. This skill creates .claude/apple-design-context.md
+  so that hig-foundations, hig-platforms, hig-components-*, hig-inputs, and
+  hig-technologies can provide targeted advice without repetitive questions.
+risk: unknown
+source: community
+---
+
+# Apple HIG: Project Context
+
+Create and maintain `.claude/apple-design-context.md` so other HIG skills can skip redundant questions.
+
+Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.
+
+## Gathering Context
+
+Before asking questions, auto-discover context from:
+
+1. **README.md** -- Product description, platform targets
+2. **Package.swift / .xcodeproj** -- Supported platforms, minimum OS versions, dependencies
+3. **Info.plist** -- App category, required capabilities, supported orientations
+4. **Existing code** -- Import statements reveal frameworks (SwiftUI vs UIKit, HealthKit, etc.)
+5. **Assets.xcassets** -- Color assets, icon sets, dark mode variants
+6. **Accessibility audit** -- Grep for accessibility modifiers/attributes
+
+Present findings and ask the user to confirm or correct. Then gather anything still missing:
+
+### 1. Product Overview
+- What does the app do? (one sentence)
+- Category (productivity, social, health, game, utility, etc.)
+- Stage (concept, development, shipped, redesign)
+
+### 2. Target Platforms
+- Which Apple platforms? (iOS, iPadOS, macOS, tvOS, watchOS, visionOS)
+- Minimum OS versions
+- Universal or platform-specific?
+
+### 3. Technology Stack
+- UI framework: SwiftUI, UIKit, AppKit, or mixed?
+- Architecture: single-window, multi-window, document-based?
+- Apple technologies in use? (HealthKit, CloudKit, ARKit, etc.)
+
+### 4. Design System
+- System defaults or custom design system?
+- Brand colors, fonts, icon style?
+- Dark mode and Dynamic Type support status
+
+### 5. Accessibility Requirements
+- Target level (baseline, enhanced, comprehensive)
+- Specific considerations (VoiceOver, Switch Control, etc.)
+- Regulatory requirements (WCAG, Section 508)
+
+### 6. User Context
+- Primary personas (1-3)
+- Key use cases and environments (desk, on-the-go, glanceable, immersive)
+- Known pain points or design challenges
+
+### 7. Existing Design Assets
+- Figma/Sketch files?
+- Apple Design Resources in use?
+- Existing component library?
+
+## Context Document Template
+
+Generate `.claude/apple-design-context.md` using this structure:
+
+```markdown
+# Apple Design Context
+
+## Product
+- **Name**: [App name]
+- **Description**: [One sentence]
+- **Category**: [Category]
+- **Stage**: [Concept / Development / Shipped / Redesign]
+
+## Platforms
+| Platform | Supported | Min OS | Notes |
+|----------|-----------|--------|-------|
+| iOS      | Yes/No    |        |       |
+| iPadOS   | Yes/No    |        |       |
+| macOS    | Yes/No    |        |       |
+| tvOS     | Yes/No    |        |       |
+| watchOS  | Yes/No    |        |       |
+| visionOS | Yes/No    |        |       |
+
+## Technology
+- **UI Framework**: [SwiftUI / UIKit / AppKit / Mixed]
+- **Architecture**: [Single-window / Multi-window / Document-based]
+- **Apple Technologies**: [List any: HealthKit, CloudKit, ARKit, etc.]
+
+## Design System
+- **Base**: [System defaults / Custom design system]
+- **Brand Colors**: [List or reference]
+- **Typography**: [System fonts / Custom fonts]
+- **Dark Mode**: [Supported / Not yet / N/A]
+- **Dynamic Type**: [Supported / Not yet / N/A]
+
+## Accessibility
+- **Target Level**: [Baseline / Enhanced / Comprehensive]
+- **Key Considerations**: [List any specific needs]
+
+## Users
+- **Primary Persona**: [Description]
+- **Key Use Cases**: [List]
+- **Known Challenges**: [List]
+```
+
+## Updating Context
+
+When updating an existing context document:
+
+1. Read the current `.claude/apple-design-context.md`
+2. Ask what has changed
+3. Update only the changed sections
+4. Preserve all unchanged information
+
+## Related Skills
+
+- **hig-platforms** -- Platform-specific guidance
+- **hig-foundations** -- Color, typography, layout decisions
+- **hig-patterns** -- UX pattern recommendations
+- **hig-components-*** -- Component recommendations
+- **hig-inputs** -- Input method coverage
+- **hig-technologies** -- Apple technology relevance
+
+---
+
+*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.

package/merged-commands/hig-technologies.md

@@ -0,0 +1,136 @@
+---
+name: hig-technologies
+version: 1.0.0
+description: ">"
+  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.
+risk: unknown
+source: community
+---
+
+# 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
+
+### General
+
+1. **Apple technologies extend app capabilities through system integration.** Each technology has established user-facing patterns; deviating creates confusion and erodes trust.
+
+2. **Privacy and user control are paramount.** Especially for health, payment, and identity technologies. Request only needed data, explain why, respect choices.
+
+### Siri and Voice
+
+3. **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 and Commerce
+
+4. **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 and Fitness
+
+5. **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.
+
+### Smart Home
+
+6. **Simple and reliable.** Immediate response when controlling devices. Clear device state. Graceful handling of connectivity issues.
+
+### Augmented Reality
+
+7. **Genuine value, not gimmicks.** Use AR when spatial context improves understanding. Guide setup (surface, lighting, space). Provide clear exit back to standard interaction.
+
+### Machine Learning and Generative AI
+
+8. **Enhance without surprising.** Smart suggestions, image recognition, text prediction. Clearly attribute AI-generated content. Controls to edit, regenerate, or dismiss. Let users correct mistakes.
+
+### Identity and Authentication
+
+9. **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.
+
+### Cloud and Data
+
+10. **Invisible and reliable sync.** Data appears on all devices without manual intervention. Handle conflicts gracefully. Never lose data.
+
+### Shared Experiences
+
+11. **Real-time participation.** SharePlay: support multiple participants, show presence, handle latency. AirPlay: appropriate Now Playing metadata.
+
+### Automotive
+
+12. **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
+
+13. **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](references/siri.md) | Siri | Intents, shortcuts, voice interaction, App Shortcuts |
+| [apple-pay.md](references/apple-pay.md) | Apple Pay | Payment buttons, checkout flow, security |
+| [tap-to-pay-on-iphone.md](references/tap-to-pay-on-iphone.md) | Tap to Pay | Merchant flows, contactless payment |
+| [in-app-purchase.md](references/in-app-purchase.md) | In-app purchase | Subscriptions, one-time purchases, transparency |
+| [healthkit.md](references/healthkit.md) | HealthKit | Health data access, privacy, permissions |
+| [carekit.md](references/carekit.md) | CareKit | Care plans, tasks, health management |
+| [researchkit.md](references/researchkit.md) | ResearchKit | Studies, informed consent, data collection |
+| [homekit.md](references/homekit.md) | HomeKit | Smart home control, device state, scenes |
+| [augmented-reality.md](references/augmented-reality.md) | ARKit | Spatial context, surface detection, setup |
+| [machine-learning.md](references/machine-learning.md) | Core ML | Predictions, smart features, confidence handling |
+| [generative-ai.md](references/generative-ai.md) | Generative AI | Attribution, editing, responsible AI, uncertainty |
+| [icloud.md](references/icloud.md) | iCloud | CloudKit, cross-device sync, conflict resolution |
+| [sign-in-with-apple.md](references/sign-in-with-apple.md) | Sign in with Apple | Authentication, privacy, button styles |
+| [id-verifier.md](references/id-verifier.md) | ID Verifier | Identity verification, document scanning |
+| [shareplay.md](references/shareplay.md) | SharePlay | Shared experiences, participant presence |
+| [airplay.md](references/airplay.md) | AirPlay | Media streaming, Now Playing, wireless display |
+| [carplay.md](references/carplay.md) | CarPlay | Driver safety, permitted app types, large targets |
+| [game-center.md](references/game-center.md) | Game Center | Achievements, leaderboards, multiplayer |
+| [voiceover.md](references/voiceover.md) | VoiceOver | Screen reader, labels, traits, accessibility |
+| [wallet.md](references/wallet.md) | Wallet | Passes, tickets, loyalty cards |
+| [nfc.md](references/nfc.md) | NFC | Tag reading, quick interactions, App Clips |
+| [maps.md](references/maps.md) | Maps | Location display, annotations, directions |
+| [mac-catalyst.md](references/mac-catalyst.md) | Mac Catalyst | iPad to Mac, menu bar, keyboard, pointer |
+| [live-photos.md](references/live-photos.md) | Live Photos | Motion capture, playback, editing |
+| [imessage-apps-and-stickers.md](references/imessage-apps-and-stickers.md) | iMessage apps | Messages extension, stickers, compact UI |
+| [shazamkit.md](references/shazamkit.md) | ShazamKit | Audio recognition, music identification |
+| [always-on.md](references/always-on.md) | Always-on display | Dimmed state, power efficiency, reduced updates |
+| [photo-editing.md](references/photo-editing.md) | Photo editing | System photo editor, filters, adjustments |
+
+## Output Format
+
+1. **Implementation checklist** -- step-by-step requirements per Apple's guidelines.
+2. **Required vs optional features** for approval.
+3. **Privacy and permission requirements** -- data access, usage descriptions.
+4. **User-facing flow** from permission prompt through task completion.
+5. **Testing guidance** -- key scenarios including edge cases.
+
+## Questions to Ask
+
+1. Which Apple technology?
+2. Core use case?
+3. Which platforms?
+4. API requirements and entitlements reviewed?
+5. 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](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.