web-haptics — Claude Code skill: what it does, how to install
Teaches your coding agent to add tactile feedback to mobile web interfaces using the zero-dependency web-haptics library and Apple HIG rules.
npx skills add lochie/web-haptics --skill web-haptics -a claude-codeWhat web-haptics does
This skill guides coding agents through integrating the web-haptics package into React, Vue, Svelte, or vanilla JavaScript. The library interacts directly with the Web Vibration API. On unsupported environments like desktop browsers, calls quietly no-op without triggering runtime errors.
The skill provides clear mappings for presets such as success, error, light, heavy, and selection. It enforces Apple HIG guidelines: haptics must never fire on passive scrolling or every generic tap, and each pulse must synchronize with visual feedback. For Next.js components, it inserts "use client", and in Svelte it hooks up cleanup via destroy().
Keep in mind that haptics must never replace visual states, because visitors on desktop screens will miss the tactile cue completely.
What it helps with
- add tactile feedback to mobile buttons, toggles, and pickers
- trigger haptic feedback on form submissions and validation errors
- wire web-haptics hooks into React, Vue, or Svelte components
- apply Apple HIG tactile guidelines to avoid interaction fatigue
Example prompts for the agent
- Install web-haptics and add a success trigger to our checkout submit handler
- Set up light tactile feedback for toggles and warning for delete dialogs
- Add selection detent haptics to the Svelte wheel picker with onDestroy cleanup
How to install web-haptics
1Skills CLI (Vercel)
npx skills add lochie/web-haptics --skill web-haptics -a claude-code2Manually: put the files in place
~/.claude/skills/web-haptics/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/web-haptics/
1Skills CLI (Vercel)
npx skills add lochie/web-haptics --skill web-haptics -a codex2Manually: put the files in place
.agents/skills/web-haptics/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add lochie/web-haptics --skill web-haptics -a cursor2Manually: put the files in place
.cursor/skills/web-haptics/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install lochie/web-haptics web-haptics2Manually: put the files in place
.github/skills/web-haptics/SKILL.md1Skills CLI (Vercel)
npx skills add lochie/web-haptics --skill web-haptics -a gemini-cli2Platform CLI
gemini skills install https://github.com/lochie/web-hapticsManually: put the files in place
.devin/skills/web-haptics/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add lochie/web-haptics --skill web-haptics -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about web-haptics
How to install web-haptics in Claude Code?
Run npx skills add lochie/web-haptics --skill web-haptics -a claude-code in your project terminal.
What does the web-haptics skill do?
It gives your coding assistant instructions on integrating the web-haptics library and mapping interaction events to proper vibration presets.
Do I need manual checks for browser vibration support?
No, the web-haptics library handles feature detection internally and silently ignores calls on unsupported platforms.
Source text
SKILL.md · MIT
---
name: web-haptics
description: Add haptic feedback to web apps using the web-haptics library. Use when building mobile-facing UIs that need tactile feedback on buttons, toggles, forms, pickers, and other interactive elements.
license: MIT
metadata:
author: lochie
version: "1.0"
---
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 appear = "medium"
Pull-to-refresh threshold = "light" | Swipe dismiss threshold = "light"
Payment confirmed = "success"
## Anti-Patterns -- AVOID
- Haptic on every tap (fatigue)
- "error" for non-errors (breaks conventions)
- Haptic without visual feedback (some devices cannot vibrate)
- Haptic on page load or passive scroll (invasive)
- "heavy" for minor interactions (jarring)
- Long continuous vibrations (web haptics = brief transient pulses)
## Before implementing, confirm with the user:
- Which interactive elements to target
- Whether to add at shared component level or individual call sites
© lochie · MIT · lochie/web-haptics