Haptics

Handles both simple UIFeedbackGenerator patterns for quick confirmations and Core Haptics (CHHapticEngine) for custom tactile experiences. The workflow is straightforward: pick your complexity level, prepare generators before triggering to reduce latency, and follow the Causality, Harmony, Utility framework to avoid annoying users. The common mistakes section is worth reading. Overusing haptics drains battery and irritates people, and the reminder to always pair haptics with visual or audio feedback for accessibility is easy to forget. Requires iOS 10+ for basic feedback, iOS 13+ for custom patterns, and you need a physical device since the Simulator won't help you here.

skills.sh installs: 183
GitHub stars: 233
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add johnrogers/claude-swift-engineering --skill haptics --agent claude-code

Installs into .claude/skills of the current project.

Files

Haptics

Haptic feedback provides tactile confirmation of user actions and system events. When designed thoughtfully, haptics transform interfaces from functional to delightful.

Overview

Haptics should enhance interactions, not dominate them. The core principle: haptic feedback is like sound design—every haptic should have purpose (confirmation, error, warning), timing (immediate or delayed), and restraint (less is more).

Reference Loading Guide

ALWAYS load reference files if there is even a small chance the content may be required. It's better to have the context than to miss a pattern or make a mistake.

Reference	Load When
UIFeedbackGenerator	Using simple impact/selection/notification haptics
Core Haptics	Creating custom patterns with CHHapticEngine
AHAP Patterns	Working with Apple Haptic Audio Pattern files
Design Principles	Applying Causality, Harmony, Utility framework