haptic-feedback-mapper

v0.1.0

Eliminates context-switching: quantifies the cognitive load of checking a screen, maps status checks to a small haptic vocabulary, and builds the Deep-Work Protection case in billable hours.

Claude Code1 Skill1 MCP serverstdio

By Fars SaadeldinLicense: UNLICENSED0 GitHub starsUpdated 5 days ago

Directory evidence

Runtimes: Claude Code
Parsed components: 2 skill or MCP entries
Source updated: Sep 18, 2026
Manifest status: Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →

Install haptic-feedback-mapper for Claude Code

Installs for the current user

claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install haptic-feedback-mapper@agent-plugin-marketplace

Paste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually

$ git clone https://github.com/farssaadeldin7-ux/claude-plugin-suite

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/haptic-feedback-mapper/.

Plugin files

plugins/haptic-feedback-mapper/

├── .claude-plugin/plugin.json
├── skills/haptic-feedback-mapper/SKILL.md
└── .mcp.json

Included Skills1

haptic-feedback-mapperskills/haptic-feedback-mapper/SKILL.md

This skill should be used when someone wants to replace screen-checking with haptic feedback and sell that as deep-work protection — "map render progress to haptics", "design a haptic vocabulary for my app", "quantify the cost of context switching", "how many billable hours do interruptions cost", "let artists stay in the zone", "notify without a screen", "build the deep-work ROI case", "which events deserve a buzz". Also use it for deciding which events earn a haptic at all, designing distinguishable patterns, measuring cognitive load before and after, and writing the "Deep-Work Protection" pitch in billable hours. Also for exporting the designed mapping as a machine-readable haptic profile and wiring software events — a build failure, a render finishing, a file-sync completing — into the local event log a haptic driver consumes.

MCP servers1

haptic-feedback-mapperstdio

command: node
args: ${CLAUDE_PLUGIN_ROOT}/mcp/server.js
env.PLUGIN_SUITE_BILLING_URL: ${PLUGIN_SUITE_BILLING_URL}
env.HAPTIC_FEEDBACK_MAPPER_LICENSE_KEY: ${HAPTIC_FEEDBACK_MAPPER_LICENSE_KEY}

MCP configuration uses runtime-provided plugin path placeholders such as ${PLUGIN_ROOT} or ${CLAUDE_PLUGIN_ROOT}. Review the manifest for the runtime-specific expansion rules.

Plugin manifests1

plugins/haptic-feedback-mapper/.claude-plugin/plugin.json

{
  "name": "haptic-feedback-mapper",
  "version": "0.1.0",
  "description": "Eliminates context-switching: quantifies the cognitive load of checking a screen, maps status checks to a small haptic vocabulary, and builds the Deep-Work Protection case in billable hours.",
  "author": {
    "name": "Fars Saadeldin"
  },
  "license": "UNLICENSED",
  "keywords": [
    "haptics",
    "deep-work",
    "focus",
    "context-switching",
    "creative-tools",
    "notifications"
  ]
}

For maintainers

If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.

[haptic-feedback-mapper on Agent Plugins Marketplace](https://pluginsmp.com/plugins/haptic-feedback-mapper)