agentleFS
ignatovvignatovv/VibePad/CLAUDE.md

VibePad

CLAUDE.md67 starsChanged 9 months agoMITView on GitHub

The file

We found no rules to list in this file: it reads as prose or reference rather than instructions.

Files
CLAUDE.md

VibePad — Ship code from your couch

Overview

VibePad is a macOS menu bar app that lets you control your AI coding assistant with a gamepad. Maps controller inputs to keyboard shortcuts for Claude Code and Codex CLI. Uses GameController framework for input and CGEvent for keyboard injection.

CRITICAL RULES

  1. NEVER commit/stage without explicit user request
  2. NEVER run destructive git operations without explicit approval (--amend, reset --hard, push --force, clean -fd)
  3. Read before edit — always read the full file before making changes
  4. Minimize diffs — prefer the smallest change that solves the problem
  5. No speculative fallbacks — don't add error handling for scenarios that can't happen
  6. This is macOS, not iOS — use AppKit/Cocoa patterns, not UIKit

Tech Stack

  • Language: Swift 5+
  • Platform: macOS 14+ (Sonoma)
  • UI: SwiftUI MenuBarExtra + AppKit (NSStatusItem, NSWindow for HUD)
  • Gamepad: GameController framework (GCController, GCExtendedGamepad)
  • Keyboard injection: CGEvent / CGEventPost (Quartz Event Services)
  • Config: JSON (Codable), stored at ~/.vibepad/config.json
  • Build: Xcode (no SPM dependencies currently)

Architecture

VibePad/
├── VibePadApp.swift         — @main entry, MenuBarExtra
├── AppDelegate.swift        — NSApplicationDelegate, GameController setup
├── GamepadManager           — GCController monitoring, connect/disconnect
├── InputMapper              — Config loading, maps inputs → actions
├── KeyboardEmitter          — CGEvent keystroke injection
├── OverlayHUD               — Transparent feedback window
├── StatusBarController      — Menu bar UI, enable/disable toggle
└── Config                   — JSON mapping model (Codable)

Key Technical Notes

  • Accessibility required — CGEvent injection needs System Settings → Privacy → Accessibility
  • App Sandbox disabled — required for CGEvent access
  • Menu bar only — no Dock icon (LSUIElement = true)
  • Analog sticks — deadzone handling (0.2–0.3), threshold-based for arrow keys, continuous for scroll
  • Triggers (L2/R2) — analog 0.0–1.0, treated as button when > 0.5

Build & Test

# Build
xcodebuild -scheme VibePad -destination 'platform=macOS' build

# Test
xcodebuild -scheme VibePad -destination 'platform=macOS' test

Project Spec

Full specification: .claude/Docs/Gamepad Coding Interface Spec.md

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.