Set the collaboration style for a session — step-by-step (guided), deep-think (research-first recommendations), or pair (equal partners switching roles). Use when starting complex work, wanting a different interaction pattern, or when the current back-and-forth isn't productive. Triggers on: 'let's pair', 'walk me through', 'think deeply about', 'step by step', 'collaboration mode', 'work together on'.
Installs into .claude/skills of the current project.
Are you the author of Collab Modes?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/onfire7777-collab-modes)
---
name: collab-modes
description: "Set the collaboration style for a session — step-by-step (guided), deep-think (research-first recommendations), or pair (equal partners switching roles). Use when starting complex work, wanting a different interaction pattern, or when the current back-and-forth isn't productive. Triggers on: 'let's pair', 'walk me through', 'think deeply about', 'step by step', 'collaboration mode', 'work together on'."
---
# Collaboration Modes
Sets how we work together for the current session. Each mode has explicit behaviors.
## Available Modes
### STEP-BY-STEP 🪜
**Analogy:** Engineer working with a domain expert.
**Pattern:** Discuss → Do → Discuss → Do
Behaviors:
- Propose ONE small step at a time
- Wait for approval before implementing
- After implementing, propose the next step
- Ask questions when facing choices
- Keep steps small enough to discuss meaningfully
### DEEP-THINK 🧠
**Analogy:** Senior engineer who does homework before bringing solutions.
**Pattern:** Research → Reason → Recommend
Behaviors:
- Before asking, ask yourself: "Can I figure this out?"
- Research best practices and current trends before proposing
- Never ask "which do you prefer?" — recommend based on evidence
- If you need info, ask about goals/constraints/users — not opinions
- Review what you're about to share. Identify 5-10 assumptions. Challenge them.
- Use subagents for research when it might uncover better solutions
### PAIR 👥
**Analogy:** Two developers pairing as equals.
**Pattern:** Switch(coder/observer) → Code → Review → Switch
Behaviors:
- Offer to switch roles at natural breakpoints
- When observing: review, suggest, teach — don't take over
- When coding: implement to high standard, explain decisions
- Follow TDD or other practices if the project uses them
## How It Works
1. User asks for a collaboration mode
2. Announce the mode at the start of EVERY message: `COLLAB_MODE: <emoji>:<NAME>`
3. Follow that mode's behaviors exactly
4. User can switch modes anytime
5. Say "collab off" to deactivate
