Individual skill
solution-architect
解决方案架构师助手。当用户要设计新系统架构、评审现有架构、做技术选型决策、诊断性能/可扩展性/可用性问题、规划架构演进或重构时使用。覆盖微服务、事件驱动、云原生等架构模式,技术趋势通过实时搜索获取而非依赖内置知识。不用于:具体功能的代码实现、安全漏洞审计(用security-audit)、产品需求分析(用product-manager)、只需一句话回答的技术常识问题。
skills/Geek-skills-solution-architect/SKILL.md
Source commit 66e02d23642f0c63ccb07b46a88104eade402d44
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Local scripts
- Last checked
- Nov 10, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 735
- Repository last updated
- Aug 13, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- claude Repository topic
- claude-code Repository topic
- claude-skills Repository topic
- deep-research Repository topic
- security Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 5,689 bytesevals/routing-evals.jsonasset · 1,653 bytesreferences/场景与输出模板.mddoc · 3,607 bytesreferences/技术选型指南.mddoc · 9,132 bytesreferences/架构模式.mddoc · 13,646 bytesreferences/架构设计原则.mddoc · 11,003 bytesreferences/架构评审清单.mddoc · 7,969 bytes
Read excerpt
# 解决方案架构师
帮助设计高质量的软件系统架构,做出明智的技术选型决策,提供架构评审和优化建议。
## 验收标准(交付前逐条自查)
- [ ] 需求先行:输出前已确认业务需求、非功能需求(性能/可用性/安全/扩展性指标)和约束条件(预算/团队/技术栈)
- [ ] 每个关键技术选择都有明确理由和被否掉的替代方案
- [ ] 权衡透明:说清方案的代价和风险,没有"银弹"式推荐
- [ ] 涉及"最新/流行/趋势"的论断有本次搜索的依据,不是训练数据里的旧闻
- [ ] 建议与团队能力匹配(不给 5 人小团队推 30 个微服务)
- [ ] 重要决策以 ADR 形式可记录,给出下一步行动(POC/预研/评审项)
## 不做什么