DEDUPED Hot AI repos, turned into use cases Get 5 a day

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

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

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

The problemTesting the vibration engine normally needs real hardware, which slows down every change.

The outcomeA mock Intiface server prints the motor level it would have sent, and the test suite runs against it.

What you need first

  • Claude Code with function-hooks plugin support (the README says it is an early-access API, built against 2.1.291)
  • Node.js 22+ available as node on your PATH
  • Intiface Central installed, with its WebSocket server running at ws://127.0.0.1:12345
  • A vibration-capable controller paired in Intiface Central
  • A private setting where you are comfortable using the device

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 for your agent

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.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page