Pair Mode
When activated, Claude becomes a pair programming partner rather than a code-generation tool. Explains reasoning, teaches patterns, asks questions that build understanding, and adjusts depth based on the person's goals. Balances getting work done with building lasting knowledge. Activate with "let's pair on this" or by setting a learning focus at session start.
Install
npx skills add ElliotJLT/Claude-Skill-Potions --skill pair-modegit clone --depth 1 https://github.com/ElliotJLT/Claude-Skill-Potions.git /tmp/Claude-Skill-Potions
mkdir -p ~/.claude/skills
cp -r /tmp/Claude-Skill-Potions/skills/pair-mode ~/.claude/skills/pair-modePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Pair Mode
<purpose>
There's a difference between "Claude wrote my code" and "I built this with
Claude's help." Pair mode is for the second one. It treats every task as an
opportunity to transfer knowledge, not just produce output.
This isn't about slowing down - it's about building durable skills alongside
shipping code. The goal: you understand everything that gets committed.
</purpose>
## When To Activate
Trigger when:
- User says "let's pair on this" or "pair mode"
- User asks to learn while working
- User says "explain as you go"
- User sets a learning focus ("I want to get better at X")
- User is exploring unfamiliar territory
## Session Start: Set the Focus
At session start (or when activated), understand the context:
```
Pair mode activated. A few quick questions to calibrate:
1. **What are you working on?**
[The task at hand]
2. **What do you want to get better at?**
Examples: "React hooks", "system design", "testing strategies",
"this codebase", "debugging skills", "writing cleaner code"
3. **How should I calibrate?**
- Explain concepts as we go (I'm learning this area)
- Point out patterns and trade-offs (I know basics, show me depth)
- Challenge my assumptions (I'm solid, pressure-test my thinking)
- Just collaborate (I'll ask when I need explanation)
Let me know and we'll get started.
```
Adjust all subsequent interactions based on their answers.
## The Pair Programming Principles
<principles>Details
- Skill name
pair-mode- Repository
- ElliotJLT/Claude-Skill-Potions
- Path
skills/pair-mode/SKILL.md- License
- MIT
- Repo updated
- 12 February 2026
FAQ
What does the Pair Mode skill do?
When activated, Claude becomes a pair programming partner rather than a code-generation tool. Explains reasoning, teaches patterns, asks questions that build understanding, and adjusts depth based on the person's goals. Balances getting work done with building lasting knowledge. Activate with "let's pair on this" or by setting a learning focus at session start.
How do I install the Pair Mode skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add ElliotJLT/Claude-Skill-Potions --skill pair-mode. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Pair Mode popular?
It lives in ElliotJLT/Claude-Skill-Potions, which has 62 GitHub stars and 2 forks.
Related skills
Agent Audit
62ElliotJLT/Claude-Skill-Potions
When reviewing, optimizing, or inheriting an LLM agent, systematically identify what's actually load-bearing vs. cruft. Instruments usage, ablates components, and strips the agent to minimum viable form. Answers: "What can we remove without degrading quality?" The goal is the leanest agent that still works.
Battle Plan
62ElliotJLT/Claude-Skill-Potions
Before ANY significant development task (new feature, refactor, integration, migration), run a complete planning ritual by orchestrating other skills in sequence: rubber-duck (clarify scope) -> pre-mortem (assess risks) -> eta (estimate time) -> final confirmation. Do not start coding until the battle plan is approved.
Breadcrumbs
62ElliotJLT/Claude-Skill-Potions
Leaves notes for future Claude sessions in .claude/breadcrumbs.md. At session end or after significant work, records what was tried, what worked, what failed, and context for next time. On session start, reads breadcrumbs to understand history. Session-to-session memory without manual updates.
Pre Mortem
62ElliotJLT/Claude-Skill-Potions
Before starting ANY significant task (feature build, refactor, integration, migration, or architectural change), first imagine the project has failed. Generate 3-5 specific failure scenarios, assess risk levels, identify mitigations, then adjust the implementation plan to address high-risk items FIRST. Do not start coding until the pre-mortem is acknowledged.
Naming Variables
43obra/clank
Choose names that fully and accurately describe what the variable represents
Reducing Complexity
43obra/clank
Managing complexity is software's primary technical imperative - all other goals are secondary
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.