# AI use cases for Vibeclaude (transkatgirl/vibeclaude)

Repo: [transkatgirl/vibeclaude](https://github.com/transkatgirl/vibeclaude) | Use cases: 3 | Page: https://dedupedai.com/use-cases/transkatgirl-vibeclaude/

VibeClaude is a Claude Code plugin that sends vibration patterns to a connected Intiface Central device for each Claude Code event, such as streamed output, tool calls, permission prompts and the end of a turn.

This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL.

- Feel Claude Code turn events through a vibration device: https://dedupedai.com/use-cases/transkatgirl-vibeclaude/feel-claude-code-events-on-device/
- Get a physical cue when Claude Code needs approval: https://dedupedai.com/use-cases/transkatgirl-vibeclaude/signal-permission-prompts-by-feel/
- Test the vibration engine with a mock controller: https://dedupedai.com/use-cases/transkatgirl-vibeclaude/test-vibration-engine-without-hardware/

## How to feel Claude Code turn events through a vibration device with Vibeclaude

Repo: [transkatgirl/vibeclaude](https://github.com/transkatgirl/vibeclaude) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Install the plugin, pick a device in Intiface Central, and feel Claude Code's activity as it runs.

**Who it is for:** A Claude Code user with a vibration-capable Intiface device who wants physical feedback while a long coding session runs.

**The problem:** Watching the screen for every turn end, tool result or error is tedious, and a silent session gives no sign of what Claude is doing.

**The outcome:** Claude Code events play on the selected device, with intensity set to a level you choose.

### Steps

1. Run `git clone https://github.com/transkatgirl/vibeclaude.git ~/.claude/vibeclaude` and then `cd ~/.claude/vibeclaude && npm install`.
2. Start Intiface Central and press the server start button.
3. Start Claude Code with `claude --plugin-dir ~/.claude/vibeclaude`, then run `/intiface` and select a vibration-capable device from the scan results.
4. Run `/intiface-intensity 0.5` to halve every pattern, or leave it at the default of 1.0.
5. Start a coding task and check that the device pulses when Claude streams text and when the turn ends.

### Prompt to paste into your agent

```text
Install the plugin from the transkatgirl/vibeclaude repo into ~/.claude/vibeclaude, run npm install there, and load it with claude --plugin-dir. Report the output of /intiface-intensity with no argument and confirm that the selected device is <device name> in the /intiface list. Verify that the daemon answers after running node daemon/daemon.mjs status.
```

### Caveat

Thinking is only felt where Claude Code shows it, and tool output is not felt as it prints, so some events will not produce a pulse.

Risk, reverse engineering: The device is body-worn and output can be intense, so set the intensity low before the first run and stop with /intiface-disconnect if anything is uncomfortable.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/transkatgirl-vibeclaude/feel-claude-code-events-on-device/

## How to get a physical cue when Claude Code needs approval with Vibeclaude

Repo: [transkatgirl/vibeclaude](https://github.com/transkatgirl/vibeclaude) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Feel a repeating pattern while a permission prompt waits, so you can step away from the screen.

**Who it is for:** A developer who lets Claude Code work in the background and needs to know when it is waiting for a permission answer.

**The problem:** A permission prompt can sit unanswered for a long time while you are away from the screen, which stalls the whole task.

**The outcome:** A repeating three-pulse pattern plays on the device while a permission prompt waits, and stops when the tool finishes, fails, or you reject it.

### Steps

1. Complete the plugin install with `git clone https://github.com/transkatgirl/vibeclaude.git ~/.claude/vibeclaude` and `cd ~/.claude/vibeclaude && npm install`.
2. Start Intiface Central, press the server start button, then run `claude --plugin-dir ~/.claude/vibeclaude`.
3. In Claude Code run `/intiface` and select your device.
4. Start a task that uses tools that need permission, and step away from the screen.
5. When the prompt appears, feel for the three 90ms pulses and return to approve or reject the call.

### Prompt to paste into your agent

```text
Use the transkatgirl/vibeclaude plugin in Claude Code with <device name> selected in Intiface Central. Start a task that needs a permission prompt and confirm that the device pulses three times at a steady pause until the prompt is answered. Report which tool asked for permission and whether the pattern stopped when the tool finished.
```

### Caveat

Claude Code does not report when you answer a prompt, so the pattern can keep going until the tool that asked finishes or fails.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/transkatgirl-vibeclaude/signal-permission-prompts-by-feel/

## How to test the vibration engine with a mock controller with Vibeclaude

Repo: [transkatgirl/vibeclaude](https://github.com/transkatgirl/vibeclaude) | Difficulty: Advanced | Time: 45 minutes | Basis: From the README

Run a fake Intiface Central server and the test suite to check the daemon without any device.

**Who it is for:** A developer who wants to change or debug the plugin's daemon but has no vibration device on hand.

**The problem:** Testing the vibration engine normally needs real hardware, which slows down every change.

**The outcome:** A mock Intiface server prints the motor level it would have sent, and the test suite runs against it.

### Steps

1. Run `git clone https://github.com/transkatgirl/vibeclaude.git ~/.claude/vibeclaude` and then `cd ~/.claude/vibeclaude && npm install`.
2. In one terminal, run `node test/mock-intiface.mjs 12345` to start the fake Intiface Central with one device.
3. In a second terminal, from the same directory, run `npm test`.
4. Read the motor levels the mock prints and compare them with the patterns in the README table.

### Prompt to paste into your agent

```text
In the transkatgirl/vibeclaude repo, start node test/mock-intiface.mjs 12345 in the background, then run npm test. Report the test result and the motor levels printed by the mock. Verify that the mock printed at least one motor level value.
```

### Caveat

The mock only prints what it would have felt, so it does not confirm how a real device feels.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/transkatgirl-vibeclaude/test-vibration-engine-without-hardware/