cooperative-vibe-coding

Coordinate real-time collaborative development across humans and AI agents.

2|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/curiositech/port-daddy --skill cooperative-vibe-coding
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cooperative-vibe-coding
Source: https://github.com/curiositech/port-daddy/tree/main/skills/cooperative-vibe-coding
Command: npx skills add https://github.com/curiositech/port-daddy --skill cooperative-vibe-coding

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents conflicting edits, lost session state, and coordination breakdowns when multiple humans and AI agents work on the same codebase by prescribing collaboration modes, ownership rules, and recovery protocols.

Core Features & Use Cases

  • Sync vs Async Decision Matrix: Guidance on when to use real-time editors, hybrid sessions, or fully async workflows based on team size and timezone overlap.
  • Agent Coordination Patterns: File-level claiming, dedicated agent scopes, and handoff conventions to avoid agents clobbering each other's changes.
  • Failure Recovery & Quality Gates: Detect and recover from merge conflicts, agent deadlocks, and context fragmentation with prescribed steps and integration checks.
  • Use Case: Run mixed human/AI development for a feature branch across timezones with clear file ownership, 25-minute sync cadence, and agent boundaries to minimize conflicts.

Quick Start

Start a cooperative vibe coding session for feature/auth-system with roles assigned, file ownership mapped, a 25-minute sync cadence, and agent boundaries defined.

Frequently Asked Questions about cooperative-vibe-coding

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent conflicting edits when pair programming with AI agents on the same codebase?

Prevent conflicting edits during collaborative coding by applying file-level claiming and dedicated agent scopes to enforce clear ownership boundaries. This coordination stops humans and AI agents from overwriting each other's changes across sync or async sessions.

What is the best way to manage async handoffs for mixed human and AI development across timezones?

Manage async handoffs across timezones using a sync vs async decision matrix and prescribed handoff conventions. This approach defines agent boundaries and sync cadences to prevent context fragmentation and lost session state during multi-agent feature development.

How do I recover from merge conflicts and agent deadlocks during multi-agent feature development?

Recover from merge conflicts and agent deadlocks using prescribed failure recovery procedures and integration quality gates. These protocols detect coordination breakdowns and execute recovery steps to restore session state and codebase integrity.

Can I use live-share sessions for mob programming with both humans and AI agents?

Yes, you can use live-share sessions for mob programming with humans and AI by enforcing a defined sync cadence and agent boundary definitions. A sync vs async decision matrix guides when real-time editors fit your team size and timezone overlap.

When should I not use real-time collaborative coding workflows for AI agents?

Avoid real-time collaborative coding workflows when timezone overlap is minimal or team size exceeds effective live-share limits. In these cases, the sync vs async decision matrix directs you to fully async workflows with strict file ownership to prevent coordination breakdowns.