# Pair Programming

> Pair program effectively — driver-navigator roles, switching frequency, and communication patterns.

- Skill: `rahulrachhoya/pair-programming` (Agent Skill)
- Install (CLI): `npx skillmds@latest add rahulrachhoya/pair-programming`
- Raw SKILL.md: https://api.skillmd.com/api/skills/rahulrachhoya/pair-programming/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: RahulRachhoya (https://skillmd.com/u/rahulrachhoya)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/rahulrachhoya/pair-programming

---


# Pair Programming

## Roles
- **Driver**: writes the code. Focused on the tactical: syntax, API calls, current line
- **Navigator**: thinks ahead. Focused on the strategic: design, edge cases, test coverage, what comes next
- Switch roles every 15-30 minutes (use a timer)

## Communication
- Navigator speaks first: "next we need to handle the error case"
- Driver confirms: "ok, I'll add a try-catch"
- Both ask questions: "why this approach?" "what about X?"
- No silent coding — narrate your thinking

## Benefits
- Fewer bugs (real-time code review)
- Knowledge sharing across the team
- Better design decisions (two perspectives)
- Fewer distractions (accountability)
- Faster onboarding for new team members

## Rules
- Both are equally responsible for the code
- Navigator is not a backseat driver — give high-level guidance, not keystroke-level commands
- Take breaks — pairing is mentally intense (Pomodoro: 25min on, 5min off)
- Switch pairs regularly to spread knowledge
- Not every task needs pairing — use it for complex or critical work