Atlas / Skills / lochie / WebHaptics

WebHapticsSAFE

skills/lochie/web-haptics

Haptic feedback for the mobile web

Verdict
SAFE
Grade
B
Trust score
89 /100
Version
1.0
Hosts
—
License
MIT
Stars
2,809
01

Overview

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

Haptic feedback for the mobile web. Supports React, Vue, and Svelte.

Installation

npm i web-haptics

Usage

import { useWebHaptics } from "web-haptics/react";

function App() {
const { trigger } = useWebHaptics();

return  trigger("success")}>Tap me;
}

See the package README for Vue, Svelte, and vanilla examples.

Contributing

Install dependencies

pnpm install:all

Dev/Watch Library and Example

pnpm dev

Build Library

pnpm build

Found this useful?

Follow me on Twitter.

Other projects

You might also like:

  • Torph - Dependency-free animated text component.
  • easing.dev - Easily create custom easing graphs.

Acknowledgements

  • Special thanks to Alex for assistance with the site design.
Read from source at commit 69ac6cc9aaaeOBSERVED · 2026-10-20
Advertisement
02

Install

Commands as the repository documents them. They are shown, not run.

npm i web-haptics
npm i web-haptics
npm i web-haptics
03

What it tells the agent

The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.

---
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
04

Trust audit

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

LayerWhat it checksResult
L0Provenance & inventoryPASS
L1Static analysis of the codePASS
L2Instruction surface (what it tells the agent)PASS
L3Class-specific surfacePASS
L4Behavioural (sandbox)SKIPPED

What the source does

Filesystem
declared (2 observation(s))
Network
none-observed
Shell
none-observed
Dependencies
not all pinned
Secrets in source
none-found

Findings (16)

LOWInventory / provenance · inv.hidden_file · CWE-1104
packages/web-haptics/.eslintignore
.eslintignore
Why it matters. hidden member outside the usual dotfiles
Fix. review its purpose
LOWInventory / provenance · inv.hidden_file · CWE-1104
packages/web-haptics/.eslintrc.cjs
.eslintrc.cjs
Why it matters. hidden member outside the usual dotfiles
Fix. review its purpose
LOWInventory / provenance · inv.hidden_file · CWE-1104
packages/web-haptics/.lintstagedrc.cjs
.lintstagedrc.cjs
Why it matters. hidden member outside the usual dotfiles
Fix. review its purpose
LOWInventory / provenance · inv.hidden_file · CWE-1104
packages/web-haptics/.prettierignore
.prettierignore
Why it matters. hidden member outside the usual dotfiles
Fix. review its purpose
LOWInventory / provenance · inv.hidden_file · CWE-1104
packages/web-haptics/.prettierrc.cjs
.prettierrc.cjs
Why it matters. hidden member outside the usual dotfiles
Fix. review its purpose
LOWFilesystem / path · fs.traversal · CWE-22, CWE-59
apps/svelte-example/vite.config.ts:11
"../../packages/web-haptics/src/svelte",
LOWFilesystem / path · fs.traversal · CWE-22, CWE-59
apps/vue-example/vite.config.ts:9
"web-haptics/vue": path.resolve(__dirname, "../../packages/web-haptics/src/vue"),
LOWFilesystem / path · fs.traversal · CWE-22, CWE-59
site/src/components/auto-resizer/index.tsx:1
import { useAutoResize } from "./../../hooks/useAutoResize";
LOWFilesystem / path · fs.traversal · CWE-22, CWE-59
site/src/components/codeblock/index.tsx:5
import { useHaptics } from "../../hooks/useHaptics";
LOWFilesystem / path · fs.traversal · CWE-22, CWE-59
site/src/components/dropdown/index.tsx:5
import { useClickOutside } from "../../hooks/useClickOutside";
LOWObfuscation / stealth · obf.zero_width · CWE-506, CWE-94
site/src/surfaces/mobile-view/demo.tsx:37
["🙅♀️", 1, true],
LOWSupply chain · supply.unpinned · CWE-829, CWE-1357
apps/react-example/package.json
react, react-dom, @types/react, @types/react-dom, @vitejs/plugin-react, typescript, vite
Why it matters. 7 dependency range(s) float
Fix. pin exact versions or ship a lockfile
LOWSupply chain · supply.unpinned · CWE-829, CWE-1357
apps/svelte-example/package.json
@sveltejs/vite-plugin-svelte, svelte, typescript, vite
Why it matters. 4 dependency range(s) float
Fix. pin exact versions or ship a lockfile
LOWSupply chain · supply.unpinned · CWE-829, CWE-1357
apps/typescript-example/package.json
typescript, vite
Why it matters. 2 dependency range(s) float
Fix. pin exact versions or ship a lockfile
LOWSupply chain · supply.unpinned · CWE-829, CWE-1357
apps/vue-example/package.json
vue, @vitejs/plugin-vue, typescript, vite
Why it matters. 4 dependency range(s) float
Fix. pin exact versions or ship a lockfile
LOWSupply chain · supply.unpinned · CWE-829, CWE-1357
package.json
@changesets/cli, @commitlint/cli, @commitlint/config-conventional, lint-staged
Why it matters. 4 dependency range(s) float
Fix. pin exact versions or ship a lockfile

Gates applied: no_behavioural_pass.

Audited 2026-10-20 · audit v0.4.1 · source sha 69ac6cc9aaaefull audit observations/trust-audit/skill/lochie__web-haptics.json · Report an issue / request a re-scan
05

Audit history

Every audit this skill has had.

DateSourceVerdictGradeScoreChange
2026-10-2069ac6cc9aaaeSAFEB89first audit
06

Questions

What does the web-haptics — lochie/web-haptics skill do?

Haptic feedback for the mobile web

Is web-haptics — lochie/web-haptics safe to install?

The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.

What can web-haptics — lochie/web-haptics access on my machine?

The audit observed that it reads or writes files. Each of those is consistent with what it says it does. Secrets in the source: none found.

What do I need installed to use web-haptics — lochie/web-haptics?

Its own instructions reference web-haptics. Dependencies are not all pinned to exact versions, so what installs today may differ tomorrow.

How current is this page?

The grade is for one exact copy of the source (69ac6cc9aaae), read on 2026-10-20. The repository is watched, and a new audit runs when it changes — this is the first audit.

Add this badge to your README

Shows this page's audit result and links back to it. It updates when the audit does.

ModelsAtlas audit badge

Markdown
[![ModelsAtlas audit: WebHaptics](https://modelsatlas.com/skills/lochie/web-haptics/badge.svg)](https://modelsatlas.com/skills/lochie/web-haptics/)

Not your listing, or something out of date? Claim or update your listing.

Advertisement