← ClaudeAtlas

add-hapticslisted

Add tasteful haptic (vibration/tactile) feedback to an app's interactive elements — buttons, toggles, forms, pickers, drag-and-drop, swipes. Platform-agnostic: covers native iOS (Swift/SwiftUI, UIKit generators), native Android (Kotlin/Compose, Vibrator/VibrationEffect), React Native (expo-haptics / react-native-haptic-feedback), Kotlin Multiplatform (KMM/KMP, via Pulsar KMP or expect/actual), and the mobile web (the web-haptics npm package). ALWAYS trigger this skill when the user runs the "/add-haptics" slash command, and also whenever they ask to "add haptics", "add haptic feedback", "add vibration feedback", "make this feel more tactile/responsive", or similar — regardless of what platform or framework their codebase is written in. Detect the platform from the repo and apply the matching implementation.
rajanndube/add-haptics · ★ 0 · Web & Frontend · score 67
Install: claude install-skill rajanndube/add-haptics
# Add Haptics Give the app's interactions tactile feedback that feels intentional rather than buzzy. The mechanics differ by platform, but the design thinking doesn't — this skill separates the two: one shared design vocabulary, applied through whichever platform-specific API the codebase actually needs. ## Step 1: Figure out what you're working with Look at the repo before doing anything else. A few signals settle it quickly: - **React Native** — `package.json` lists `react-native` as a dependency. Treat this as RN even though the project also contains `ios/` and `android/` folders — those are the generated native shells RN builds on top of, not a separate native app. Don't route to the native iOS/Android references for an RN project. - **Kotlin Multiplatform (KMM/KMP)** — a `shared`/`composeApp` module with `commonMain`/`androidMain`/`iosMain` source sets in `build.gradle.kts`, and/or `expect`/`actual` declarations. This is easy to mistake for plain native Android since it's all Kotlin — the multi-target source set layout and a real Xcode project consuming the compiled framework are the tells. Don't route this to the native iOS/Android references individually; the shared-code layer needs its own approach. - **Native iOS** — `.xcodeproj`/`.xcworkspace`, a `Podfile`, or `.swift`/`.m` source files, with no `react-native` in sight and no KMM `shared` module feeding it. - **Native Android** — a root `build.gradle`/`build.gradle.kts` with the Android application plugin, `.kt`