Skip to content

LeoYeAI/agent-master-skills / skills/agent-collaboration-protocol

agent-collaboration-protocol

Verified

Structured multi-agent collaboration for backend + frontend builds. Use when an orchestrator needs to coordinate a backend engineer and frontend engineer on the same feature. Triggered by multi-role build requests like "build a dashboard with an API and UI" or "create a full-stack feature" or any task requiring both backend (API, data, infra) and frontend (UI, templates, design) work.

FileKindSize
.clawhub/origin.jsonconfig160 B
SKILL.mdskill md4.2 KB
_meta.jsonconfig147 B
clawhub.jsonconfig875 B
references/handoff-format.mdmarkdown688 B
references/integration-log.mdmarkdown858 B
references/spec-template.mdmarkdown1.9 KB
scripts/init_collab.shscript1.5 KB

references/spec-template.md

View on GitHub
# SPEC: {Feature Name}

> Generated by Agent Collaboration Protocol

## Overview

One sentence. What this feature does and why it matters.

## Contract

| Field | Value |
|-------|-------|
| API Base Path | `http://localhost:8000/api/v1` |
| Auth Scheme | Bearer JWT / Session cookie / None |
| Content Type | `application/json` |
| Error Format | `{ "error": "...", "detail": { ... } }` |

## Data Models

### {Entity Name}
| Field | Type | Required | Notes |
|-------|------|----------|-------|
| id | string | yes | UUID |
| name | string | yes | Display name |

### {Entity Name 2}
...

## Endpoints

### `GET /api/v1/{resource}`
**Response:**
```json
{
  "data": [ ... ],
  "total": 42,
  "page": 1
}
```

### `POST /api/v1/{resource}`
**Request:**
```json
{
  "field": "value"
}
```
**Response:** `201 Created` with body containing the created entity

## UI Components

### {Component Name}
- Purpose: One sentence
- Data source: `GET /api/v1/{resource}`
- States: loading, empty, error, populated
- Interactions: click to select, pull to refresh

## File Structure

### Backend
```
backend/
  router.py        ← Route handlers
  models.py        ← Data models/schemas
  service.py       ← Business logic
```

### Frontend
```
frontend/
  components/      ← UI components
  templates/       ← Page templates
  styles/          ← Styles
  api.js           ← API client
```

## Edge Cases

- Empty state: What shows when no data exists?
- Error state: What shows on API failure?
- Loading state: What shows while data fetches?
- Offline: Does it degrade gracefully?

## Success Criteria

- [ ] Endpoint returns correct data with proper status codes
- [ ] UI renders loading, empty, error, and populated states
- [ ] User can complete the full happy path end-to-end
- [ ] API errors display actionable messages in the UI

## Out of Scope

- What we are NOT building right now
- Authentication improvements
- Performance optimization
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall