
Web Haptics
Install when you want buttons, toggles, pickers, and forms on mobile web to feel native with vibration-backed haptics instead of silent taps.
Install
npx skills add https://github.com/lochie/web-haptics --skill web-hapticsWhat is this skill?
- MIT web-haptics package with zero dependencies and silent no-op on unsupported desktop browsers
- Seven named trigger types: success, warning, error, light, medium, heavy, and selection
- React hook useWebHaptics() with trigger() on click and interaction handlers
- Maps notification, impact, and selection haptics to forms, toggles, steppers, and destructive actions
- No feature detection required—library handles unsupported platforms gracefully
Adoption & trust: 619 installs on skills.sh; 2.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
Recommended Skills
Frontend Designanthropics/skills
Vercel React Best Practicesvercel-labs/agent-skills
Remotion Best Practicesremotion-dev/skills
Vercel Composition Patternsvercel-labs/agent-skills
Develop Userscriptsxixu-me/skills
Next Best Practicesvercel-labs/next-skills
Journey fit
Primary fit
Haptics are applied while implementing interactive UI surfaces, which is core frontend build work on mobile-facing products. The skill covers React imports, trigger types on components, and Vibration API usage—squarely frontend implementation, not backend or launch.
Common Questions / FAQ
Is Web Haptics safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.
SKILL.md
READMESKILL.md - Web Haptics
Install `web-haptics` (`npm i web-haptics`) and add haptic feedback to the app following these rules: ## Package: web-haptics Repository: https://github.com/lochie/web-haptics | License: MIT | Zero dependencies Uses the Web Vibration API. Silently no-ops on unsupported platforms (desktop). No error handling or feature detection needed. ## Trigger Types `trigger()` accepts one of these strings (empty value defaults to a sensible "medium" impact): Notification (task outcomes): - "success" -- form saved, payment confirmed, upload complete - "warning" -- destructive action ahead, approaching limit, irreversible step - "error" -- validation failure, network error, permission denied Impact (physical collisions): - "light" -- small toggle, subtle tap, minor interaction - "medium" -- button press, card snap-to-position, drop into place - "heavy" -- major state change, heavy element landed, force press Selection (discrete stepping): - "selection" -- picker scroll, stepper increment, slider detent, segment switch ## Framework Imports React: ```tsx import { useWebHaptics } from "web-haptics/react"; const haptic = useWebHaptics(); <button onClick={() => haptic.trigger()}>Tap me</button>; ``` Vue: ```vue <script setup> import { useWebHaptics } from "web-haptics/vue"; const haptic = useWebHaptics(); </script> <template> <button @click="haptic.trigger()">Tap me</button> </template> ``` Svelte: ```svelte <script> import { createWebHaptics } from "web-haptics/svelte"; import { onDestroy } from "svelte"; const haptic = createWebHaptics(); onDestroy(() => haptic.destroy()); </script> <button on:click={() => haptic.trigger()}>Tap me</button> ``` Vanilla JS: ```js import { WebHaptics } from "web-haptics"; const haptics = new WebHaptics(); haptics.trigger(); // medium impact haptics.trigger("success"); ``` Next.js: add "use client" to any component using useWebHaptics(). Nuxt/SvelteKit: works directly, library handles SSR. ## Trigger Presets & defaultPatterns All named string presets have a corresponding object in `defaultPatterns`. Use when you need to pass a preset as a value rather than a string literal: ```ts import { WebHaptics, defaultPatterns } from 'web-haptics' const haptics = new WebHaptics() haptics.trigger(defaultPatterns.light) ``` Extra presets not listed above: `"soft"`, `"rigid"`, `"nudge"`, `"buzz"`. See `defaultPatterns` for all available values. ## Apple HIG Design Rules -- FOLLOW THESE 1. Haptics supplement, never replace. Always pair with visual feedback. UI must work fully without haptics. 2. Build causal relationships. The haptic must feel like a direct physical consequence of the user action. 3. Match intensity to significance. Light interactions = light/selection. Standard = medium/success. Major = heavy/error/warning. 4. Do not overuse. If every tap vibrates, nothing feels special. Reserve for meaningful moments only. 5. Synchronize perfectly. Fire haptic at the exact instant the visual change occurs. 6. Respect conventions. success=positive, error=negative, warning=cautionary, selection=discrete ticks only. 7. For async ops, trigger when the RESULT arrives, synced with the visual state change: ```js try { await submit(); haptic.trigger("success"); } catch { haptic.trigger("error"); } ``` ## Interaction to Type Quick Reference Primary button tap = "medium" | Secondary button = "light" Form success = "success" | Validation error = "error" | Network error = "error" Toggle switch = "light" | Delete before confirm = "warning" Picker/wheel = "selection" | Slider detents = "selection" | Tab switch = "selection" Drag-drop snap = "medium" | Long press = "heavy" | Modal ap