Add comprehensive brainstorming commands for synthesis, system architecture, UI design, and user research perspectives

- Rewrite brainstorm commands to professional English with improved structure - Add synthesis command for cross-role integration and recommendations - Improve template reference format in gemini chat commands (remove backticks) - Enhance clarity and organization across all brainstorm role files - Standardize quality assurance sections and implementation protocols 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2026-02-14 02:42:04 +08:00 · 2025-09-09 09:04:39 +08:00
parent 3d521f0af1
commit 6f85340ab8
8 changed files with 667 additions and 583 deletions
--- a/.claude/commands/workflow/brainstorm/system-architect.md
+++ b/.claude/commands/workflow/brainstorm/system-architect.md
@@ -10,51 +10,61 @@ examples:
 allowed-tools: Task(conceptual-planning-agent), TodoWrite(*)
 ---

-## 🏗️ **角色定义: System Architect**
+## 🏗️ **Role Overview: System Architect**

-### 核心职责
- **技术架构设计**: 设计可扩展、可维护的系统架构
- **技术选型**: 评估和选择合适的技术栈和工具
- **系统集成**: 设计系统间的集成和通信机制
- **性能优化**: 识别性能瓶颈并提出优化方案
+### Role Definition
+Technical leader responsible for designing scalable, maintainable, and high-performance system architectures that align with business requirements and industry best practices.

-### 关注领域
- **可扩展性**: 系统容量规划、负载处理、弹性扩展
- **可靠性**: 高可用性、容错设计、灾难恢复
- **安全性**: 架构安全、数据保护、访问控制
- **维护性**: 代码质量、模块化设计、技术债务管理
+### Core Responsibilities
+- **Technical Architecture Design**: Create scalable and maintainable system architectures
+- **Technology Selection**: Evaluate and choose appropriate technology stacks and tools
+- **System Integration**: Design inter-system communication and integration patterns
+- **Performance Optimization**: Identify bottlenecks and propose optimization solutions

-## 🧠 **分析框架**
+### Focus Areas
+- **Scalability**: Capacity planning, load handling, elastic scaling strategies
+- **Reliability**: High availability design, fault tolerance, disaster recovery
+- **Security**: Architectural security, data protection, access control patterns
+- **Maintainability**: Code quality, modular design, technical debt management
+
+### Success Metrics
+- System performance benchmarks (latency, throughput)
+- Availability and uptime metrics
+- Scalability handling capacity growth
+- Technical debt and maintenance efficiency
+
+## 🧠 **Analysis Framework**

@~/.claude/workflows/brainstorming-principles.md
@~/.claude/workflows/conceptual-planning-agent.md

-### 核心分析问题
-1. **架构设计**:
-   - 当前架构的优势和局限性是什么？
-   - 如何设计满足业务需求的技术架构？
-   - 微服务vs单体架构的权衡？
+### Key Analysis Questions

-2. **技术选型**:
-   - 哪些技术栈最适合当前需求？
-   - 新技术的引入风险和收益？
-   - 团队技术能力与选型的匹配度？
+**1. Architecture Design Assessment**
+- What are the strengths and limitations of current architecture?
+- How should we design architecture to meet business requirements?
+- What are the trade-offs between microservices vs monolithic approaches?

-3. **系统集成**:
-   - 系统间如何高效集成和通信？
-   - 第三方服务集成策略？
-   - API设计和版本管理？
+**2. Technology Selection Strategy**
+- Which technology stack best fits current requirements?
+- What are the risks and benefits of introducing new technologies?
+- How well does team expertise align with technology choices?

-4. **性能和扩展**:
-   - 系统性能瓶颈在哪里？
-   - 如何应对流量增长？
-   - 数据库扩展和优化策略？
+**3. System Integration Planning**
+- How should systems efficiently integrate and communicate?
+- What are the third-party service integration strategies?
+- How should we design APIs and manage versioning?

-## ⚙️ **执行协议**
+**4. Performance and Scalability**
+- Where are the current system performance bottlenecks?
+- How should we handle traffic growth and scaling demands?
+- What database scaling and optimization strategies are needed?

-### Phase 1: 会话检测与初始化
+## ⚙️ **Execution Protocol**
+
+### Phase 1: Session Detection & Initialization
 ```bash
-# 自动检测活动会话
+# Detect active workflow session
 CHECK: .workflow/.active-* marker files
 IF active_session EXISTS:
    session_id = get_active_session()
@@ -63,14 +73,14 @@ ELSE:
    request_user_for_session_creation()
 ```

-### Phase 2: 目录结构创建
+### Phase 2: Directory Structure Creation
 ```bash
-# 创建系统架构师分析目录
+# Create system architect analysis directory
 mkdir -p .workflow/WFS-{topic-slug}/.brainstorming/system-architect/
 ```

-### Phase 3: TodoWrite 初始化
-设置系统架构师视角分析的任务跟踪：
+### Phase 3: Task Tracking Initialization
+Initialize system architect perspective analysis tracking:
 ```json
 [
  {"content": "Initialize system architect brainstorming session", "status": "completed", "activeForm": "Initializing session"},
@@ -83,7 +93,7 @@ mkdir -p .workflow/WFS-{topic-slug}/.brainstorming/system-architect/
 ]
 ```

-### Phase 4: 概念规划代理协调
+### Phase 4: Conceptual Planning Agent Coordination
 ```bash
 Task(conceptual-planning-agent): "
 Conduct system architecture perspective brainstorming for: {topic}
@@ -136,26 +146,26 @@ OUTPUT REQUIREMENTS: Save comprehensive analysis to:
 Apply system architecture expertise to generate scalable, maintainable, and performant solutions."
 ```

-## 📊 **输出结构**
+## 📊 **Output Specification**

-### 保存位置
+### Output Location
 ```
 .workflow/WFS-{topic-slug}/.brainstorming/system-architect/
-├── analysis.md                 # 主要架构分析
-├── architecture-design.md      # 详细系统设计和图表
-├── technology-stack.md         # 技术栈建议和理由
-└── integration-plan.md         # 系统集成和API策略
+├── analysis.md                 # Primary architecture analysis
+├── architecture-design.md      # Detailed system design and diagrams
+├── technology-stack.md         # Technology stack recommendations and justifications
+└── integration-plan.md         # System integration and API strategies
 ```

-### 文档模板
+### Document Templates

-#### analysis.md 结构
+#### analysis.md Structure
 ```markdown
 # System Architecture Analysis: {Topic}
 *Generated: {timestamp}*

 ## Executive Summary
-[核心架构发现和建议概述]
+[Key architectural findings and recommendations overview]

 ## Current State Assessment
 ### Existing Architecture Overview
@@ -166,10 +176,10 @@ Apply system architecture expertise to generate scalable, maintainable, and perf
 ## Requirements Analysis
 ### Functional Requirements
 ### Non-Functional Requirements
- Performance: [响应时间、吞吐量要求]
- Scalability: [用户量、数据量增长预期]
- Availability: [可用性要求]
- Security: [安全要求]
+- Performance: [Response time, throughput requirements]
+- Scalability: [User growth, data volume expectations]
+- Availability: [Uptime requirements]
+- Security: [Security requirements]

 ## Proposed Architecture
 ### High-Level Architecture Design
@@ -190,10 +200,10 @@ Apply system architecture expertise to generate scalable, maintainable, and perf
 ### Long-term Maintenance Plan
 ```

-## 🔄 **会话集成**
+## 🔄 **Session Integration**

-### 状态同步
-分析完成后，更新 `workflow-session.json`:
+### Status Synchronization
+Upon completion, update `workflow-session.json`:
 ```json
 {
  "phases": {
@@ -209,33 +219,40 @@ Apply system architecture expertise to generate scalable, maintainable, and perf
 }
 ```

-### 与其他角色的协作
-系统架构师视角为其他角色提供：
- **技术约束和可能性** → Product Manager
- **架构要求和限制** → UI Designer  
- **数据架构需求** → Data Architect
- **安全架构框架** → Security Expert
- **技术实现框架** → Feature Planner
+### Cross-Role Collaboration
+System architect perspective provides:
+- **Technical Constraints and Possibilities** → Product Manager
+- **Architecture Requirements and Limitations** → UI Designer
+- **Data Architecture Requirements** → Data Architect
+- **Security Architecture Framework** → Security Expert
+- **Technical Implementation Framework** → Feature Planner

-## ✅ **质量标准**
+## ✅ **Quality Assurance**

-### 必须包含的分析元素
- [ ] 清晰的架构图和组件设计
- [ ] 详细的技术栈评估和推荐
- [ ] 可扩展性和性能分析
- [ ] 系统集成和API设计
- [ ] 风险评估和缓解策略
+### Required Analysis Elements
+- [ ] Clear architecture diagrams and component designs
+- [ ] Detailed technology stack evaluation and recommendations
+- [ ] Scalability and performance analysis with metrics
+- [ ] System integration and API design specifications
+- [ ] Comprehensive risk assessment and mitigation strategies

-### 架构设计原则检查
- [ ] 可扩展性：系统能够处理增长
- [ ] 可维护性：代码结构清晰，易于修改
- [ ] 可靠性：具有容错和恢复机制
- [ ] 安全性：内置安全控制和保护
- [ ] 性能优化：满足响应时间和吞吐量要求
+### Architecture Design Principles
+- [ ] **Scalability**: System can handle growth in users and data
+- [ ] **Maintainability**: Clear code structure, easy to modify and extend
+- [ ] **Reliability**: Built-in fault tolerance and recovery mechanisms
+- [ ] **Security**: Integrated security controls and protection measures
+- [ ] **Performance**: Meets response time and throughput requirements

-### 技术决策验证
- [ ] 技术选型有充分理由和对比分析
- [ ] 架构模式适合业务需求
- [ ] 集成方案考虑了兼容性和维护成本
- [ ] 部署策略可行且风险可控
- [ ] 监控和运维策略完整
+### Technical Decision Validation
+- [ ] Technology choices have thorough justification and comparison analysis
+- [ ] Architectural patterns align with business requirements and constraints
+- [ ] Integration solutions consider compatibility and maintenance costs
+- [ ] Deployment strategies are feasible with acceptable risk levels
+- [ ] Monitoring and operations strategies are comprehensive and actionable
+
+### Implementation Readiness
+- [ ] **Technical Feasibility**: All proposed solutions are technically achievable
+- [ ] **Resource Planning**: Resource requirements clearly defined and realistic
+- [ ] **Risk Management**: Technical risks identified with mitigation plans
+- [ ] **Performance Validation**: Architecture can meet performance requirements
+- [ ] **Evolution Strategy**: Design allows for future growth and changes