← ClaudeAtlas

verify-vibebuddylisted

Drive VibeBuddy (Mac menu-bar companion, headless vibebuddyd on the LAN HTTP surface, iPhone, Watch) the way a user does. Use to launch an isolated daemon, prove dashboard sessions, phone pairing, remote approval, question reply, or iPhone Demo, and capture evidence without touching the installed app on :9876.
semantic-craft/iOS-vibebuddy · ★ 92 · AI & Automation · score 80
Install: claude install-skill semantic-craft/iOS-vibebuddy
# Verify VibeBuddy VibeBuddy is a personal-use **Mac, iPhone, and Apple Watch** companion for Claude Code, Codex, Grok Build/Bot, and Cursor usage. Users touch native apps, not a website. The Mac is the hub: the menu-bar app embeds the same HTTP + WebSocket server as the headless `vibebuddyd` (`docs/getting-started.md`). Phones and hooks talk to that server with a bearer token (ADR-0009). This skill drives an **isolated** `vibebuddyd` (the repo's documented headless path) and, on a Mac with simulators, the iPhone Demo. It does **not** replace `/Applications`, bind **:9876**, or write the login `~/Library/Application Support/vibebuddy/` token. `features/README.md` maps each feature to its recipe; drive the mapped feature file, not a convenient substitute. Helper (executable; invoke only via these paths): ```bash ctrl="docs/agents/skills/verify-vibebuddy/helpers/control-vibebuddy" ``` ## Launch Documented user/dev start for the hub: ```bash swift run --package-path VibeBuddyMac vibebuddyd --pair # production-shaped; defaults to :9876 ``` Verification start — isolated port, disposable HOME, never :9876: ```bash export VERIFY_RUN_ID="${VERIFY_RUN_ID:-vb-$(date +%Y%m%dT%H%M%S)}" export VIBEBUDDY_QA_PORT="${VIBEBUDDY_QA_PORT:-18765}" # must not be 9876 export VERIFY_EVIDENCE_DIR="${VERIFY_EVIDENCE_DIR:-$PWD/.scratch/verify-vibebuddy/$VERIFY_RUN_ID}" "$ctrl" launch # or: "$ctrl" launch --pair ``` Ready when **both** are true: - `GET http://127.0.0.1:$VIBEB