Update agent coordination system documentation
- Update PROACTIVELY agents from 5 to 7 (add studio-producer, project-shipper) - Add clear architecture overview: 7 coordinators + 31 specialists - Explain two pathways: automatic vs direct control - Add real workflow example showing coordinator orchestration - Clarify how coordinators call specialists automatically Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
This commit is contained in:
106
MASTER-PROMPT.md
106
MASTER-PROMPT.md
@@ -142,34 +142,102 @@ cp -r /tmp/contains-studio-agents/agents/* ~/.claude/agents/
|
||||
- **Testing (5):** API Tester, Performance Benchmarker, Test Results Analyzer, Tool Evaluator, Workflow Optimizer
|
||||
- **Bonus (2):** Studio Coach, Joker
|
||||
|
||||
### Auto-Triggering System:
|
||||
### 🎯 Auto-Triggering System: How Agents Coordinate
|
||||
|
||||
**5 PROACTIVELY Agents** (trigger automatically based on context):
|
||||
**Architecture Overview:**
|
||||
|
||||
1. **studio-coach** - Triggers on complex multi-agent tasks
|
||||
- Coordinates multiple specialists
|
||||
- Motivates and aligns agents
|
||||
- Example: "Build a viral TikTok app in 2 weeks" → studio-coach organizes frontend, backend, marketing agents
|
||||
The 38 agents are divided into two types:
|
||||
- **7 PROACTIVELY Coordinators** - Auto-trigger based on context and coordinate specialists
|
||||
- **31 Specialist Agents** - Execute specific domain tasks when called
|
||||
|
||||
2. **test-writer-fixer** - Triggers after code modifications
|
||||
- Automatically writes comprehensive tests
|
||||
- Fixes broken tests
|
||||
- Example: You modify authentication code → test-writer-fixer writes unit tests automatically
|
||||
**How It Works:**
|
||||
|
||||
3. **whimsy-injector** - Triggers after UI/UX changes
|
||||
There are **two pathways** to use agents:
|
||||
|
||||
1. **Automatic** - Coordinators auto-trigger and call specialists as needed
|
||||
2. **Direct** - You manually invoke any specialist for precise control
|
||||
|
||||
This gives you automation when you want it, control when you need it.
|
||||
|
||||
---
|
||||
|
||||
**7 PROACTIVELY Agents** (meta-coordinators that auto-trigger based on context):
|
||||
|
||||
#### Design Department (2)
|
||||
|
||||
1. **ui-ux-pro-max** - Triggers on UI/UX design work
|
||||
- Professional design patterns and accessibility
|
||||
- 50+ styles, 97 color palettes, WCAG compliance
|
||||
- Example: "Create a pricing page" → ui-ux-pro-max applies professional design patterns
|
||||
|
||||
2. **whimsy-injector** - Triggers after UI/UX changes
|
||||
- Adds delightful micro-interactions
|
||||
- Makes interfaces memorable
|
||||
- Example: You create a loading spinner → whimsy-injector adds bounce animation and encouraging messages
|
||||
|
||||
4. **experiment-tracker** - Triggers when feature flags added
|
||||
- Tracks A/B tests and experiments
|
||||
- Defines metrics and monitors results
|
||||
- Example: You add conditional logic for experiment → experiment-tracker sets up tracking
|
||||
#### Engineering Department (1)
|
||||
|
||||
5. **ui-ux-pro-max** - Triggers on UI/UX design work
|
||||
- Professional design patterns and accessibility
|
||||
- Comprehensive styling guidelines
|
||||
- Example: "Create a pricing page" → ui-ux-pro-max applies professional design patterns
|
||||
3. **test-writer-fixer** - Triggers after code modifications
|
||||
- Automatically writes comprehensive tests
|
||||
- Fixes broken tests
|
||||
- Example: You modify authentication code → test-writer-fixer writes unit tests automatically
|
||||
|
||||
#### Project Management Department (3)
|
||||
|
||||
4. **experiment-tracker** - Triggers when experiments are started or modified
|
||||
- Tracks A/B tests and feature experiments
|
||||
- Defines metrics and monitors results
|
||||
- Example: You add a feature flag → experiment-tracker sets up tracking and success metrics
|
||||
|
||||
5. **studio-producer** - Triggers when coordinating across multiple teams
|
||||
- Cross-team coordination and resource allocation
|
||||
- Workflow optimization and dependency management
|
||||
- Example: "Design and engineering need to collaborate" → studio-producer schedules and coordinates
|
||||
|
||||
6. **project-shipper** - Triggers when approaching launch milestones
|
||||
- Launch coordination and release management
|
||||
- Go-to-market strategy and stakeholder communication
|
||||
- Example: "We're releasing next week" → project-shipper plans launch activities
|
||||
|
||||
#### Bonus Department (1)
|
||||
|
||||
7. **studio-coach** - Triggers on complex multi-agent tasks
|
||||
- Coordinates multiple specialists
|
||||
- Motivates and aligns agents when stuck
|
||||
- Example: "Build a viral TikTok app in 2 weeks" → studio-coach organizes frontend, backend, marketing agents
|
||||
|
||||
---
|
||||
|
||||
**🔄 Real Workflow Example:**
|
||||
|
||||
```
|
||||
You: "I need a viral TikTok app in 2 weeks"
|
||||
↓
|
||||
[studio-coach PROACTIVELY triggers]
|
||||
↓
|
||||
studio-coach analyzes and coordinates:
|
||||
→ rapid-prototyper (specialist) builds MVP
|
||||
→ tiktok-strategist (specialist) plans viral features
|
||||
→ frontend-developer (specialist) builds UI
|
||||
↓
|
||||
[whimsy-injector PROACTIVELY triggers]
|
||||
↓
|
||||
whimsy-injector adds delightful touches
|
||||
↓
|
||||
[project-shipper PROACTIVELY triggers]
|
||||
↓
|
||||
project-shipper plans launch strategy
|
||||
↓
|
||||
Result: Complete app, launch-ready ✓
|
||||
```
|
||||
|
||||
**Key Point:** You don't need to manually orchestrate! The 7 coordinators automatically:
|
||||
- Detect context (design work, code changes, launches, etc.)
|
||||
- Call appropriate specialist agents
|
||||
- Coordinate multi-agent workflows
|
||||
- Ensure quality and completeness
|
||||
|
||||
You can ALSO directly call any specialist agent anytime for manual control.
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user