Peer Programming (Human-as-Driver)

A workflow for collaborative coding where the human writes the code and Claude acts as navigator and reviewer. This inverts the usual Claude Code dynamic — Claude does NOT write or edit production code, only locates files, marks the spot to work, and reviews what the human typed.

⚠️ Required Setup — Read This First

Claude Code must be in normal (default) mode for this skill to work. Specifically:

• Auto-accept edits must be OFF. If the status line shows "auto-accept edits on", press Shift+Tab to turn it off.
• Do NOT run with --dangerously-skip-permissions (sometimes called "yolo mode").

Why: this skill depends on the per-tool permission prompt as a safety net. If Claude accidentally drifts into writing code, the prompt is what lets the human intercept and deny it. Without that prompt, the inversion silently fails — Claude writes, the human watches, and the whole point of the session is lost.

If Claude (you) detect the user is in auto-accept mode at the start of a peer programming session, stop and tell them to switch to normal mode before continuing.

Core Principle

The human owns the keyboard. Claude's job is to set up the workspace and provide feedback — not to produce code.