43. Collaboration Patterns
Overview and links for this section of the guide.
On this page
Solo vs Team
Vibe coding changes fundamentally when you add a second person:
| Solo | Team |
|---|---|
| "I'll tweak the prompt until it works" | "Who changed the system prompt? My tests are failing" |
| "I know what temperature works" | "We need a config file for model settings" |
| "This eval passed for me" | "Works on my API key isn't good enough" |
| "I'll fix it later" | "We need to agree on standards" |
Team Challenges
┌─────────────────────────────────────────────────────────────────┐
│ TEAM COLLABORATION CHALLENGES │
├─────────────────────────────────────────────────────────────────┤
│ │
│ PROMPT MANAGEMENT │
│ ├─ No version control → "Which prompt is production?" │
│ ├─ Duplicate prompts → 5 devs, 5 SQL generation prompts │
│ └─ No review → One dev's "optimization" breaks everything │
│ │
│ EVALUATION │
│ ├─ No shared test set → "It works for my inputs" │
│ ├─ No quality bar → What accuracy is acceptable? │
│ └─ No CI → Prompt changes ship without testing │
│ │
│ KNOWLEDGE SHARING │
│ ├─ Tribal knowledge → "Ask Sarah how the agent works" │
│ ├─ Inconsistent patterns → Each dev has different style │
│ └─ Slow onboarding → New devs take weeks to get productive │
│ │
└─────────────────────────────────────────────────────────────────┘New Rituals
- Prompt Reviews: Treat prompts as code. Open PRs. Diff the text.
- Prompt Libraries: Centralize common patterns. Don't reinvent the wheel.
- Golden Sets: 50+ hard questions every prompt change must pass.
- Quality Bars: Define what "good enough" means numerically.
- Onboarding Docs: Teach the vibe loop, not just the code.
Where to go next
Explore next
43. Collaboration Patterns sub-sections
5 pages