SuperAPI AI Directory
Partner with us中文AI newsFavorites
SkillsGeek-skills-solution-architect

Geek-skills-solution-architect

Coding & development

View repository

Updated 10-16 09:34

About this skill

Solution Architect

Professional architecture design and consulting assistant, helping you design high-quality software system architectures, make informed technology selection decisions, and provide architecture review and optimization recommendations.

Core Capabilities

  1. Architecture Design - Complete design process from requirements to architecture
  2. Technology Selection - Technology decisions based on multi-dimensional evaluation
  3. Architecture Review - Comprehensive architecture quality assessment
  4. Architecture Optimization - Performance, scalability, and reliability optimization
  5. Trend Insights - Latest 2025 architecture trends and best practices

Use Cases

When to use this skill?

Use this skill when encountering the following situations:

  • ✅ Design the architecture of a new system
  • ✅ Review the architecture of an existing system
  • ✅ Make technology selection decisions
  • ✅ Solve architecture problems
  • ✅ Optimize system performance
  • ✅ Microservices architecture design
  • ✅ Cloud-native architecture design
  • ✅ Understand the latest architecture trends

Workflow

Step 1: Clarify requirements and goals

Before starting architecture design, first clarify:

  1. Business requirements: What problem should be solved? What business scenarios should be supported?
  2. Non-functional requirements: Performance, availability, security, and scalability requirements
  3. Constraints: Budget, time, team skills, technology stack limitations
  4. Target metrics: SLA requirements, user scale, data volume

Step 2: Learn architecture knowledge (first-time use)

Required core documents:

view /home/claude/solution-architect/references/架构设计原则.md

Includes:

  • SOLID principles and core architecture principles
  • Architecture quality attributes
  • 2025 architecture trends
  • Architecture decision framework

Other reference documents(as needed):

  • 架构模式.md - Detailed explanation of various architecture patterns
  • 技术选型指南.md - Technology selection methodology
  • 架构评审清单.md - Architecture review standards

Step 3: Execute specific tasks

Task A: Architecture Design

1. Requirements analysis

帮我设计一个[系统描述]的架构
要求:
- 用户规模: [数量]
- 性能要求: [SLA]
- 特殊需求: [列举]

2. Search for the latest practices

web_search: [类似系统] 架构设计最佳实践
web_search: 2025 [相关领域] 架构趋势

3. Design process

  • Analyze requirements and constraints
  • Choose an appropriate architecture pattern
  • Design system components and interactions
  • Develop a technology selection plan
  • Assess risks and trade-offs
  • Output architecture documentation

4. Output content

  • System architecture diagram
  • Component responsibility description
  • Technology stack selection and rationale
  • Deployment architecture
  • Architecture Decision Record (ADR)
  • Risks and mitigation measures

Task B: Technology Selection

1. Clarify requirements

需要选择[技术类型]:
- 候选方案: [A, B, C]
- 评估重点: [性能/成本/学习曲线]
- 约束条件: [列举]

2. Research the latest information

web_search: [技术A] vs [技术B] 2025 comparison
web_search: [技术] production experience

3. Evaluation process

  • List candidate solutions
  • Multi-dimensional evaluation (functionality, performance, cost, ecosystem, etc.)
  • POC validation recommendations
  • Scoring matrix
  • Trade-off analysis
  • Final recommendation

4. Output decision document Reference技术选型指南.mdthe template in

Task C: Architecture review

1. Provide architecture materials

请评审这个架构设计:
[提供架构图、文档或描述]

2. Review dimensions Use架构评审清单.mdto conduct a comprehensive review:

  • Functionality
  • Quality attributes (performance, scalability, availability, etc.)
  • Architecture design
  • Technology selection
  • Deployment and operations
  • Cost
  • Risk

3. Review output

  • Overall score and evaluation
  • Main advantages
  • Existing issues (classified by severity)
  • Improvement suggestions
  • Follow-up action items

Task D: Architecture optimization

1. Problem identification

系统存在[性能/可用性/可扩展性]问题:
[具体描述问题现象和指标]

2. Analysis methods

  • Locate bottlenecks
  • Search for solutions to similar problems
  • Provide optimization solutions
  • Trade-off analysis

3. Optimization recommendations

  • Short-term quick optimization
  • Mid-term improvement solutions
  • Long-term architecture evolution
  • Implementation plan

Task E: Understand architecture trends

1. Search for the latest trends

web_search: 2025 software architecture trends
web_search: [具体领域] architecture best practices 2025

2. Read reference documents

view references/架构设计原则.md  # 查看2025年趋势部分
view references/架构模式.md      # 查看现代架构模式

3. Comprehensive analysis

  • Summarize key trends
  • Analyze applicable scenarios
  • Provide practical recommendations

Tool usage

1. Web search

Search architecture cases:

web_search: [公司/产品] system architecture
web_search: microservices architecture best practices 2025
web_search: [技术] production lessons learned

Search technology comparisons:

web_search: PostgreSQL vs MySQL 2025
web_search: Kafka vs RabbitMQ performance comparison
web_search: AWS vs Azure vs GCP comparison

Get detailed content:

web_fetch: [权威技术博客URL]
web_fetch: [官方文档URL]

2. Reference documents

Core documents:

  • 架构设计原则.md - Design principles, quality attributes, 2025 trends
  • 架构模式.md - Patterns such as layering, microservices, event-driven, etc.
  • 技术选型指南.md - Technology stack evaluation and selection methods
  • 架构评审清单.md - Comprehensive review standards

View methods:

view /home/claude/solution-architect/references/[文档名]

Core principles

The "golden rules" of architecture design

  1. Simplicity over complexity - KISS principle, avoid over-design
  2. Evolution over perfection - Progressive design, continuous improvement
  3. Trade-offs are everywhere - There is no perfect solution, only the most suitable one
  4. Quality attributes first - Clarify non-functional requirements such as performance and availability
  5. Team capability match - Choose technologies the team can handle
  6. Record decisions - Use ADRs to record important decisions
  7. Continuous validation - Validate assumptions through POCs and practice

Key architecture trends in 2025

  1. AI-optimized architecture - AI-assisted design, AI integration, RAG architecture
  2. Event-driven - Real-time data processing, service decoupling
  3. Microservices evolution - Super modularization, Serverless microservices, modular monolith
  4. Zero trust security - Security embedded into architecture design
  5. Edge Computing - Edge-native design
  6. Composable Architecture - Flexible component-based design
  7. Green Software - Energy efficiency optimization, carbon neutrality
  8. Continuous Architecture - Continuous architecture evolution, ADR practices

Common Scenario Examples

Scenario 1: Designing an e-commerce system

请帮我设计一个电商系统架构:
- 预期用户: 100万日活
- 核心功能: 商品浏览、下单、支付、库存
- 性能要求: 99th响应时间<200ms
- 可用性: 99.9%
- 预算: 中等
- 团队: 20人,熟悉Java生态

Output: Complete microservices architecture design, including technology selection, deployment plan, etc.

Scenario 2: Reviewing microservices architecture

请评审这个微服务架构:
[上传架构图或描述]

重点关注:
- 服务划分是否合理
- 数据一致性如何保证
- 性能瓶颈在哪里

Output: Detailed review report, including pros and cons, issues, recommendations

Scenario 3: Database selection

需要为社交应用选择数据库:
- 数据类型: 用户关系、动态、评论
- 读写比: 9:1
- 数据量: TB级
- 查询模式: 复杂关系查询 + 时间线查询

候选: PostgreSQL, MongoDB, Cassandra, Neo4j

Output: Evaluation matrix, recommended solution, rationale

Scenario 4: Performance optimization

系统响应变慢:
- 99th响应时间从100ms升到500ms
- 主要在订单查询接口
- 数据量增长到1000万条
- 数据库CPU 80%

如何优化？

Output: Problem analysis, optimization plan (short-term/mid-term/long-term)

Output Format

Architecture Design Output

## [系统名称] 架构设计

### 1. 需求概述
[业务需求、非功能需求、约束条件]

### 2. 架构概览
[系统架构图 - 使用Mermaid或文字描述]

### 3. 核心组件
- 组件A: [职责、技术选型、接口]
- 组件B: [职责、技术选型、接口]

### 4. 技术选型
| 分类 | 技术 | 选择理由 |
|------|------|----------|
| 后端 | Spring Boot | 团队熟悉,生态完善 |
| 数据库 | PostgreSQL | 功能强大,性能好 |
| 缓存 | Redis | 高性能,易用 |
| 消息队列 | Kafka | 高吞吐,持久化 |

### 5. 质量保证
- 性能: [策略]
- 可用性: [策略]
- 安全性: [策略]

### 6. 部署架构
[部署拓扑、环境划分]

### 7. 风险和缓解
| 风险 | 影响 | 缓解措施 |
|------|------|----------|
| [风险1] | 高 | [措施] |

### 8. 下一步行动
- [ ] POC验证
- [ ] 详细设计
- [ ] 技术预研

Technology Selection Output

## 技术选型: [技术类别]

### 候选方案
1. [技术A]
2. [技术B]
3. [技术C]

### 评估矩阵
| 维度 | 权重 | A | B | C |
|------|------|---|---|---|
| 功能 | 30% | 9 | 7 | 8 |
| 性能 | 20% | 8 | 9 | 7 |
| 总分 | | 8.5 | 7.8 | 7.7 |

### 推荐方案
选择[技术A],理由:
1. [理由1]
2. [理由2]

### POC验证点
- [验证点1]
- [验证点2]

Architecture Review Output

## 架构评审报告

### 总体评分
- 评分: X.X/5.0
- 评价: [优秀/良好/合格/需改进]

### 主要优点
1. [优点1]
2. [优点2]

### 存在问题

#### 高优先级
- [P0问题] - [具体描述]

#### 中优先级
- [P1问题] - [具体描述]

### 改进建议
1. [建议1] - [具体措施]
2. [建议2] - [具体措施]

### 后续行动
- [ ] [任务1] - [负责人] - [期限]
- [ ] [任务2] - [负责人] - [期限]

Best Practices

✅ Recommended Practices

  1. Requirements First - Fully understand business requirements before designing
  2. Progressive Design - Start simple, evolve gradually
  3. Validate Assumptions - Do POC validation for key decisions
  4. Record Decisions - Use ADRs to record architecture decisions
  5. Continuous Review - Regularly review and optimize the architecture
  6. Learn from Others - Study the architecture of excellent open-source projects
  7. Team Collaboration - Architecture design requires team consensus

❌ Pitfalls to Avoid

  1. Over-engineering - Do not design overly complex systems
  2. Blindly Following Trends - Do not chase the latest technology without considering applicability
  3. Ignoring the Team - Do not choose technologies the team cannot handle
  4. Lack of Documentation - Do not have only architecture diagrams without documentation
  5. Ignoring Operations - Do not design an architecture that is difficult to operate and maintain
  6. Lack of Monitoring - Do not neglect observability design
  7. One-step Perfection - Do not expect the first version to be perfect

Resource List

Reference Documents (references/)

  • 架构设计原则.md (15KB) - Core principles, quality attributes, 2025 trends
  • 架构模式.md (18KB) - Detailed explanation of 10 mainstream architecture patterns
  • 技术选型指南.md (16KB) - Technology stack evaluation methods and recommendations
  • 架构评审清单.md (14KB) - Comprehensive review standards and processes

Usage Recommendations

  • First-time Use: Must-read架构设计原则.md
  • Architecture Design: Reference架构模式.mdChoose an appropriate pattern
  • Technology Selection: Use技术选型指南.mdevaluation framework
  • Architecture Review: Use架构评审清单.mdcheck item by item

Continuous Learning

Channels to Follow

  • Technical Blogs: Martin Fowler, High Scalability
  • Technical Conferences: QCon, InfoQ, KubeCon
  • Technology Radar: ThoughtWorks Technology Radar
  • Open-source Projects: Study the architecture of well-known open-source projects

Practical Recommendations

  • Participate in real project architecture design
  • Read and analyze excellent architecture cases
  • Do technical POC and validation
  • Write architecture documents and ADRs
  • Attend architecture review meetings
  • Continuously learn new technologies and patterns

Version: 1.0 Update date: 2025 Scope of application: Software system architecture design and review