VIBE CODINGZERO HARDWARE REQUIRED

One prompt: "Write a Python WebSocket server on port 8765 that broadcasts OBD2 data at 10fps. Include a SimOBD class with realistic animated values for speed (0-120), RPM (800-5000), coolant (85-95°C), throttle, fuel and battery. Smooth the data so dials don't jump. Auto-detect if no OBD dongle and use SimOBD. Real OBD uses python-obd library."

pip install obd websockets --break-system-packages · python3 obd_bridge.py · Should print "OBD bridge running on ws://localhost:8765 [SIMULATOR MODE]"

Ask Claude: "Write a minimal HTML page that connects to ws://localhost:8765 and displays the live JSON data on screen." Open it in Chrome while the bridge runs. You should see live numbers updating every 100ms.

"The RPM jumps too fast" → Claude rewrites the smoothing. "Speed acceleration feels unrealistic" → Claude adjusts the curve. You are the art director here. The feel of the simulator is what makes the dashboard look alive.

Ask Claude to add a NightRunMode — speed climbs to 100+, RPM hits 4000+, then eases, like you're actually on the Shutoko. Makes demos dramatically more impressive than flat numbers.

Open DevTools → Toggle device toolbar → Add custom device → 800×480. Keep this open the entire session. Everything you build should be tested at this exact resolution before copy to Pi.

"Build a Blade Runner-style car dashboard HTML artifact at exactly 800×480px. Amber #ff8c00 on near-black. Orbitron font. Large speed dial (SVG arc), RPM dial, coolant, throttle, fuel. Six views: Speed, Shutoko, Engine, Joe terminal, Arcade, Kanji. Arrow key navigation. Grain overlay and scanlines. Connect to WebSocket at ws://localhost:8765."

WSL2: python3 obd_bridge.py · Chrome: open dashboard at 800×480. The dials should move with simulator data. Speed needle sweeps. RPM climbs. This is the moment where it stops being a webpage and becomes KITT.

Tell Claude things like: "Speed dial needs to be bigger and fill the left half." "The amber glow on the speed number isn't strong enough." "Add rain particles in the background." "The gear indicator should flash when simulating gear changes." Claude rewrites, you see it instantly.

Go through each view. Nothing should overflow or clip. Fonts readable at arm's length in a dark car. Shutoko view should show route status cards. Joe view should look like a terminal. Arcade view should show game cards. Kanji view should show big legible characters.

Switch bridge to night run mode. Watch the speed climb to 100+, RPM hit 4k, coolant creep up. The dashboard should look genuinely alive. This is what you demo at meets. If it looks spectacular here, it'll look spectacular on the 7" screen.

"Write three systemd service files for a Raspberry Pi: 1) kitt-obd.service — runs /home/pi/kitt/obd_bridge.py on boot, restarts on crash. 2) kitt-display.service — starts Chromium kiosk mode pointing at /home/pi/kitt/kitt_dashboard.html after kitt-obd starts. 3) kitt-ignition.service — runs /home/pi/kitt/ignition_monitor.py, depends on network."

"Write a bash setup script for a fresh Raspberry Pi OS install that: installs python3-pip, python-obd, websockets, flask, espeak, chromium-browser, enables I2C via raspi-config noninteractive, creates /home/pi/kitt directory, copies service files, enables all three systemd services, sets up auto-boot on power restore." Review it yourself — you should understand every line.

Run the script in WSL2 (not on actual Pi) to catch obvious errors. It won't run perfectly since WSL2 isn't a Pi, but you'll catch typos, wrong paths, missing commands. Ask Claude to fix any errors that come up.

Ask Claude: "Write a deploy.sh for my Surface Pro WSL2 that SSHes into raspberrypi.local and rsync-copies the /kitt folder, then runs setup.sh remotely." When Pi arrives: plug it in, find IP, run ./deploy.sh — done.

Ask Claude: "Help me write a system prompt for an AI driving copilot called Joe. He lives in my Honda CRZ. He gets live data: speed, RPM, coolant, fuel. He knows the Shutoko expressway. He speaks in 1-2 sentences max. He's calm, precise, slightly cinematic. Not a chatbot. Think KITT from Knight Rider crossed with a Tokyo taxi dispatcher."

Paste the system prompt + fake data and fire questions: "C1 is jammed what route?" / "Coolant is 97°C should I be worried?" / "How far to Daikoku PA?" / "Engine warning light just came on" / "Good run tonight?" Test until every answer sounds like KITT, not ChatGPT.

Ask Claude: "Write 5 variants of Joe's engine-off shutdown speech. Each should be 1-2 sentences, cinematic, reference the run quality or conditions. Examples: 'Clean run tonight. Coolant held steady. Shutdown in 60.' or 'C1 was smooth. See you next time, Kris.'"

Save joe_system_prompt.txt into the kitt/ folder. This gets loaded by the Python voice service in Phase 5. Version-control it — you'll keep tweaking it over time as you drive more.

retroarch.com — free. Install on Surface Pro. Load any ROM. Verify it runs. You're testing the software on real hardware (your Surface) before the Pi arrives — same principle as the OBD bridge approach.

"Write a RetroArch config file for two players on one keyboard. Player 1: WASD + Space/V/C/X. Player 2: Arrow keys + numpad Enter/0. Include hotkeys for menu (Escape), quit combo, and fast-forward (Tab). Format for Pi 4 RetroArch 1.9+."

"Write a Flask server on port 8766 that accepts GET /launch/[game] and opens RetroArch with a specific ROM using subprocess. Games: retroarch (SNES core), pico8 (runs .p8 file). Return JSON status."

Put the cfg in RetroArch on your Surface Pro. Grab a game. Test that WASD works for player 1 and arrows for player 2 simultaneously. This is the exact layout that'll be in the CRZ. Better to find keyboard conflicts now.

lexaloffle.com. Download Windows version. Open PICO-8. Type HELP to see the basic commands. Run a demo cart (SPLORE has tons). Get a feel for the 128×128 canvas and 16-colour palette before asking Claude to write code for it.

"Write a PICO-8 Lua game called Wangan Night Racer. Top-down view. Night cityscape scrolling background. Two player cars — P1 WASD, P2 arrows. Cars dodge traffic. Score increments for distance. Amber/orange color palette only to match KITT aesthetic. Start simple — just the car, movement, and scrolling road."

"Add oncoming traffic cars that get faster over time." "Add a score display in the KITT font style." "When you crash, flash the screen red and show speed at time of crash." Iterate exactly like the dashboard — describe → see → adjust.

This is the test that matters. Can two people play comfortably on one keyboard? Does the pace feel right for a small 7" screen? If Hiro laughs while playing, it's ready for the Pi.