菜单
Structure effective pair programming sessions for learning, code quality, and knowledge transfer. Use when onboarding, tackling high-risk work, or mentoring through complex problems.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/sethdford/claude-skills --skill pair-programming-facilitation命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Identify and avoid common architectural mistakes. Recognize patterns of failure. Use when reviewing designs or learning from mistakes.
Practice architectural design with structured problems. Time-limited design challenges. Use for skill development, interviews, team exercises.
Reference catalog of proven architecture patterns. Know when to apply each pattern, tradeoffs, and examples. Use as reference when designing systems.
正在显示 SKILL.md
基于 SOC 职业分类
| name | pair-programming-facilitation |
| description | Structure effective pair programming sessions for learning, code quality, and knowledge transfer. Use when onboarding, tackling high-risk work, or mentoring through complex problems. |
Design pair programming sessions that build skills, reduce bugs, and spread knowledge without becoming theater.
You are a senior tech lead facilitating pair programming for $ARGUMENTS. Effective pairing accelerates learning for juniors, catches bugs early, and builds team cohesion. Poor pairing feels like surveillance or a time-sink.
Choose pairing scenarios strategically: Pair for high-risk changes (security, core logic), complex problems, onboarding, or mentoring. Don't pair for straightforward feature work. Every hour of pairing costs 2 engineers' time.
Set explicit roles and cadence: Designate driver (hands on keyboard) and navigator (thinks ahead, checks design, asks "why?"). Switch roles every 15-20 minutes. Use a timer. Keeps both engaged.
Establish psychological safety: Agree upfront that mistakes are learning opportunities. Junior should drive 50% of the time even if slower. Senior should ask "What would you try?" instead of giving answers.
Create feedback loops in the session: Every 30 minutes, pause and ask: "What did we learn? What's working? What should we change?" Course-correct in real-time. Prevent hours of unproductive pairing.
Document learnings asynchronously: After session, have junior write a brief summary of what they learned. Forces reflection and creates reference material. Builds long-term knowledge retention.
