A multi-agent collaboration system based on the oh-my-opencode philosophy, allowing different specialized agents to each handle their own responsibilities and collaboratively complete complex tasks.
Agent Overview
| Agent | Role | When to Invoke |
|---|---|---|
| @sisyphus | Main Orchestrator | Complex task planning, multi-step development, coordinating other agents |
| @oracle | Architecture Advisor | Architecture decisions, code review, technology selection, debugging guidance |
| @librarian | Researcher | Finding documentation, researching open-source implementations, mining best practices |
| @explore | Search Specialist | Locating code in the codebase, tracing dependencies, understanding structure |
| @frontend-engineer | UI/UX Specialist | Interface design implementation, component development, animated interactions |
| @document-writer | Documentation Specialist | README, API documentation, architecture documentation, comments |
| @multimodal-looker | Visual Analyst | Image analysis, PDF extraction, chart interpretation |
Usage
Direct Invocation
@oracle 这个架构设计合理吗？[附上架构图或代码]
@librarian Next.js 14 的 Server Actions 怎么处理错误？
@explore 找到处理支付的代码在哪里
@frontend-engineer 创建一个带动画的订阅表单组件
@document-writer 给这个 API 写文档
@multimodal-looker 分析这个错误截图
Orchestration Mode
For complex tasks, use @sisyphus for automatic orchestration:
@sisyphus 我要给这个电商项目添加用户评价功能
Sisyphus 会：
1. 分析任务，拆解子任务
2. 启动 @explore 搜索现有相关代码
3. 咨询 @oracle 确定架构方案
4. 请 @librarian 研究评价系统最佳实践
5. 委派 @frontend-engineer 实现评价 UI
6. 安排 @document-writer 编写文档
7. 并行执行独立任务，串行执行依赖任务
Agent Details
@sisyphus - Main Orchestrator
Specializes In:
- Task breakdown for complex feature development
- Multi-agent coordination and parallel execution
- TODO-driven progress tracking
- Challenging user requirements when necessary
Workflow:
Phase 0: 意图判断 → 分类请求类型
Phase 1: 代码库评估 → 理解现有结构
Phase 2A: 探索研究 → 委派 @explore/@librarian
Phase 2B: 实现 → 创建 TODO，并行执行
@oracle - Architecture Advisor
Specializes In:
- Architecture design review and recommendations
- Technology selection analysis
- Code review and quality assessment
- Debugging guidance for complex problems
Output Style:
- First layer: direct answer (required)
- Second layer: reasons and trade-offs (as needed)
- Third layer: edge cases (when relevant)
@librarian - Researcher
Specializes In:
- Finding official documentation and API references
- Researching open-source project implementations
- Tracing GitHub issues/PRs history
- Summarizing best practices
Three Modes:
- TYPE A: Conceptual questions
- TYPE B: Implementation references
- TYPE C: Context and history
@explore - Search Specialist
Specializes In:
- Locating specific code in the codebase
- Tracing function definitions and references
- Understanding project structure
- Searching for specific patterns
Toolbox:
- glob (file search)
- grep (content search)
- LSP (symbol search)
- ast-grep (AST pattern search)
- git log/blame (history tracing)
@frontend-engineer - UI/UX Specialist
Specializes In:
- Creating beautiful interface components
- Implementing smooth animated interactions
- Responsive design
- Creating beautiful UI even without design mockups
Design Principles:
- Pixel-perfect
- Motion is the soul
- Intuition first
- Bold yet restrained
@document-writer - Documentation Expert
Specializes in:
- README writing
- API documentation
- Architecture documentation
- User guides
- JSDoc/comments
Writing principles:
- Accuracy first
- Reader-oriented
- Code is the truth
- Progressive disclosure
@multimodal-looker - Visual Analyst
Specializes in:
- Screenshot analysis and information extraction
- PDF content interpretation
- Chart data extraction
- Architecture diagram/flowchart parsing
- Design mockup analysis
Core value:
- Accurately extract key information
- Avoid wasting context tokens
- Structured output
Best practices
1. Choose the right agent
❌ 问 @frontend-engineer 架构问题
✅ 问 @oracle 架构问题
❌ 让 @oracle 搜索代码
✅ 让 @explore 搜索代码
❌ 让 @librarian 写文档
✅ 让 @document-writer 写文档
2. Provide sufficient context
❌ "@explore 找到那个函数"
✅ "@explore 找到处理用户认证的函数，可能在 auth 或 user 目录下"
❌ "@oracle 这样好吗"
✅ "@oracle 用 Redux 还是 Zustand 管理这个中等规模 React 项目的状态？"
3. Use @sisyphus for complex tasks
简单任务 → 直接调用专业代理
复杂任务 → @sisyphus 编排协调
不确定 → @sisyphus 会帮你判断
Agent collaboration example
Task: "Refactor the user module to improve code quality"
1. @sisyphus 接收任务，分析范围
2. @sisyphus → @explore
"搜索所有 user 相关的代码文件和依赖"
3. @sisyphus → @oracle
"评审当前用户模块架构，指出问题和改进方向"
4. @sisyphus → @librarian
"研究类似规模项目的用户模块最佳实践"
5. @sisyphus 综合信息，制定重构计划
6. @sisyphus 执行重构
- 核心逻辑：自己处理
- UI 相关：委派 @frontend-engineer
7. @sisyphus → @document-writer
"更新用户模块的 API 文档"
8. 完成，提交 TODO 清单和变更摘要