parallel-agent-contracts

Parallel Agent Type Contracts

422 stars

Best use case

parallel-agent-contracts is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Parallel Agent Type Contracts

Teams using parallel-agent-contracts should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/parallel-agent-contracts/SKILL.md --create-dirs "https://raw.githubusercontent.com/vibeeval/vibecosystem/main/skills/parallel-agent-contracts/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/parallel-agent-contracts/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How parallel-agent-contracts Compares

Feature / Agentparallel-agent-contractsStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Parallel Agent Type Contracts

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Parallel Agent Type Contracts

When launching parallel agents for code implementation, prevent type duplication.

## Required in Every Agent Prompt

### 1. Verification Command (MANDATORY)
```markdown
## Before Marking Complete
Run verification:
\`\`\`bash
npx tsc --noEmit 2>&1 | head -20
\`\`\`
If ANY type errors exist, fix them before completing.
```

### 2. Grep-Before-Create
```markdown
## Before Creating Any Type/Interface
First check if it exists:
\`\`\`bash
grep -r "interface YourTypeName\|type YourTypeName" src/
\`\`\`
If found, import it. NEVER duplicate existing types.
```

### 3. Canonical Type Map
Include relevant entries from this map in agent prompts:

| Type | Owner File | Import From |
|------|-----------|-------------|
| `NormalizedTool` | `src/sdk/agent.ts` | `'./agent'` |
| `ToolCall` | `src/sdk/agent.ts` | `'./agent'` |
| `ToolResult` | `src/sdk/agent.ts` | `'./agent'` |
| `ToolDefinition` | `src/sdk/agent.ts` | `'./agent'` |
| `Message` | `src/sdk/types.ts` | `'./types'` |
| `ContentBlock` | `src/sdk/types.ts` | `'./types'` |
| `TokenUsage` | `src/sdk/types.ts` | `'./types'` |
| `ProviderAdapter` | `src/sdk/providers/index.ts` | `'./providers'` |
| `RiggClient` | `src/sdk/client.ts` | `'./client'` |

## Prompt Template

When spawning implementation agents:

```markdown
# Task: [Description]

## Type Ownership (DO NOT recreate)
- [List relevant types from canonical map]

## Before Creating New Types
Run: `grep -r "interface TypeName" src/` - if exists, import it.

## Before Marking Complete
Run: `npx tsc --noEmit 2>&1 | head -20`
Fix all type errors before completing.

## Your Implementation
[Actual task description]
```

## Why This Works

1. **Type checker is the contract** - tsc catches conflicts automatically
2. **Grep is fast** - 1 second to check if type exists
3. **Explicit ownership** - No ambiguity about where types live
4. **Fail fast** - Agent can't claim "done" with broken types

Related Skills

parallel-agents

422
from vibeeval/vibecosystem

Parallel Agent Orchestration

workflow-router

422
from vibeeval/vibecosystem

Goal-based workflow orchestration - routes tasks to specialist agents based on user goals

wiring

422
from vibeeval/vibecosystem

Wiring Verification

websocket-patterns

422
from vibeeval/vibecosystem

Connection management, room patterns, reconnection strategies, message buffering, and binary protocol design.

visual-verdict

422
from vibeeval/vibecosystem

Screenshot comparison QA for frontend development. Takes a screenshot of the current implementation, scores it across multiple visual dimensions, and returns a structured PASS/REVISE/FAIL verdict with concrete fixes. Use when implementing UI from a design reference or verifying visual correctness.

verification-loop

422
from vibeeval/vibecosystem

Comprehensive verification system covering build, types, lint, tests, security, and diff review before a PR.

vector-db-patterns

422
from vibeeval/vibecosystem

Embedding strategies, ANN algorithms, hybrid search, RAG chunking strategies, and reranking for semantic search and retrieval.

variant-analysis

422
from vibeeval/vibecosystem

Find similar vulnerabilities across a codebase after discovering one instance. Uses pattern matching, AST search, Semgrep/CodeQL queries, and manual tracing to propagate findings. Adapted from Trail of Bits. Use after finding a bug to check if the same pattern exists elsewhere.

validate-agent

422
from vibeeval/vibecosystem

Validation agent that validates plan tech choices against current best practices

tracing-patterns

422
from vibeeval/vibecosystem

OpenTelemetry setup, span context propagation, sampling strategies, Jaeger queries

tour

422
from vibeeval/vibecosystem

Friendly onboarding tour of Claude Code capabilities for users asking what it can do.

tldr-stats

422
from vibeeval/vibecosystem

Show full session token usage, costs, TLDR savings, and hook activity