← ClaudeAtlas

core-hapticslisted

Builds custom tactile and synchronized audio-haptic experiences with Core Haptics, including CHHapticEngine lifecycle, transient and continuous events, dynamic parameters, parameter curves, AHAP files, and device verification. Use when system sensoryFeedback or UIFeedbackGenerator patterns cannot express the required haptic behavior.
thienqo/ios-skills · ★ 11 · AI & Automation · score 69
Install: claude install-skill thienqo/ios-skills
# Core Haptics Compose, play, and verify custom haptic patterns with `CoreHaptics`. Scope: Swift 6.4, iOS 26+, and supported physical hardware. ## Contents - [Choose the Right API](#choose-the-right-api) - [Implementation Workflow](#implementation-workflow) - [Capability and Fallback](#capability-and-fallback) - [Engine Lifecycle](#engine-lifecycle) - [Choose a Pattern Representation](#choose-a-pattern-representation) - [Playback and Modulation](#playback-and-modulation) - [Testing](#testing) - [Common Mistakes](#common-mistakes) - [Review Checklist](#review-checklist) - [References](#references) ## Choose the Right API Use the smallest API that expresses the interaction: | Need | Owner | |---|---| | Standard success, warning, selection, impact, or SwiftUI state feedback | `sensoryFeedback` or UIKit feedback generators; see `swiftui-patterns` | | Custom waveform, sustained feedback, live modulation, or synchronized haptic/audio | This skill and Core Haptics | | Ordinary audio playback, routing, recording, or audio-session policy | AVFAudio/AVKit guidance, not this skill | | Controller rumble | Core Haptics controller APIs; keep controller discovery/input in the game-controller owner | Do not introduce `CHHapticEngine` for a normal button tap. Custom haptics add lifecycle, hardware, interruption, power, and physical-device test responsibilities. ## Implementation Workflow 1. Define the interaction intent and a non-haptic fallback. 2. Check `CHHapticEngine.capabilities