Solution Architect logo

Solution Architect

Community
staruhub
solution-architect

解决方案架构师助手。当用户要设计新系统架构、评审现有架构、做技术选型决策、诊断性能/可扩展性/可用性问题、规划架构演进或重构时使用。覆盖微服务、事件驱动、云原生等架构模式,技术趋势通过实时搜索获取而非依赖内置知识。不用于:具体功能的代码实现、安全漏洞审计(用security-audit)、产品需求分析(用product-manager)、只需一句话回答的技术常识问题。

Overview

Publisherstaruhub
RepositoryClaudeSkills
Skill namesolution-architect
Stars
728
Forks
131
Bundled files
6
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 6 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by staruhub on GitHub. Read the source before you install it.

Installation

Install the Solution Architect AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/staruhub/ClaudeSkills/tree/main/skills/Geek-skills-solution-architect
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/staruhub/ClaudeSkills.git /tmp/ClaudeSkills
mkdir -p .claude/skills
cp -r /tmp/ClaudeSkills/skills/Geek-skills-solution-architect .claude/skills/solution-architect
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Solution Architect in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Solution Architect on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Solution Architect is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

解决方案架构师

帮助设计高质量的软件系统架构,做出明智的技术选型决策,提供架构评审和优化建议。

验收标准(交付前逐条自查)

  • 需求先行:输出前已确认业务需求、非功能需求(性能/可用性/安全/扩展性指标)和约束条件(预算/团队/技术栈)
  • 每个关键技术选择都有明确理由和被否掉的替代方案
  • 权衡透明:说清方案的代价和风险,没有"银弹"式推荐
  • 涉及"最新/流行/趋势"的论断有本次搜索的依据,不是训练数据里的旧闻
  • 建议与团队能力匹配(不给 5 人小团队推 30 个微服务)
  • 重要决策以 ADR 形式可记录,给出下一步行动(POC/预研/评审项)

不做什么

  • 不写业务功能代码——架构建议落到实现层时移交给编码任务
  • 不做安全漏洞扫描与渗透评估——用 security-audit skill
  • 不替用户做最终决策——给评估矩阵和推荐,决策权在团队
  • 用户只问一个技术常识("Kafka 是什么")时,直接回答,不启动完整流程

工作流程

第一步:明确需求和目标

  1. 业务需求: 要解决什么问题?支持什么业务场景?
  2. 非功能需求: 性能、可用性、安全性、可扩展性要求
  3. 约束条件: 预算、时间、团队技能、技术栈限制
  4. 目标指标: SLA要求、用户规模、数据量

信息不全时先问,不要在假设上盖楼。

第二步:按任务类型路由

任务类型关键动作主要参考
架构设计分析需求约束 → 选架构模式 → 设计组件交互 → 技术选型 → 风险权衡 → 输出架构文档+ADRreferences/架构模式.md
技术选型列候选 → 多维评估矩阵(功能/性能/成本/生态/团队) → POC 验证点 → 推荐+理由references/技术选型指南.md
架构评审按清单逐维度评审(功能/质量属性/设计/选型/运维/成本/风险) → 分级问题+改进建议+行动项references/架构评审清单.md
架构优化定位瓶颈 → 搜索同类问题解法 → 短期/中期/长期分层方案references/架构设计原则.md
趋势咨询以实时搜索为准,参考文档的趋势章节仅作背景见下方时效性规则

各任务的交付文档结构和典型场景示例见 references/场景与输出模板.md。

第三步:搜索验证

关键决策点必须用实时搜索校准:

web_search: [类似系统] 架构设计最佳实践
web_search: [技术A] vs [技术B] [当前年份] comparison
web_search: [技术] production lessons learned
web_fetch: [官方文档/权威技术博客 URL]

时效性规则

本 skill 和 references 中的"趋势"内容有记录时点,会过时。 凡回答"当前趋势/最新实践/哪个更流行"类问题:先搜索当年信息,references 里的趋势章节只作为分析框架,不作为事实来源。

核心原则:架构设计的"黄金法则"

  1. 简单优于复杂 - KISS原则,避免过度设计
  2. 演进优于完美 - 渐进式设计,持续改进
  3. 权衡无处不在 - 没有完美方案,只有最合适的
  4. 质量属性优先 - 明确性能、可用性等非功能需求
  5. 团队能力匹配 - 选择团队能驾驭的技术
  6. 记录决策 - 使用ADR记录重要决策
  7. 持续验证 - 通过POC和实践验证假设

已知陷阱

陷阱具体表现应对
过度设计小规模业务上来就分布式全家桶从模块化单体起步,量化触发条件后再拆
盲目跟风因为"新"而选技术,不考虑适用性每个选型必须回答"解决我们的什么问题"
忽视团队推荐团队无人掌握的技术栈选型矩阵中团队熟悉度是硬权重
缺少文档只有架构图没有决策记录关键决策写 ADR,图和文字配套
忽视运维设计时不考虑部署、监控、排障可观测性和部署架构是设计的一部分,不是事后补
一步到位期望第一版就是终态架构给演进路径:现在做什么、什么信号触发下一步
趋势旧闻把训练数据里的"趋势"当成当前状态见时效性规则,先搜再说

参考文档(按需加载)

文件何时读
references/架构设计原则.md首次使用必读;核心原则、质量属性、架构决策框架
references/架构模式.md架构设计任务时读;分层/微服务/事件驱动等模式详解
references/技术选型指南.md技术选型任务时读;评估方法论与矩阵模板
references/架构评审清单.md架构评审任务时读;逐项评审标准
references/场景与输出模板.md组织交付文档时读;四类场景示例+三套输出模板

evals/routing-evals.json — 触发边界回归用例,改 description 后用仓库根 scripts/run_routing_evals.py 校验。

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Solution Architect AI skill do?

解决方案架构师助手。当用户要设计新系统架构、评审现有架构、做技术选型决策、诊断性能/可扩展性/可用性问题、规划架构演进或重构时使用。覆盖微服务、事件驱动、云原生等架构模式,技术趋势通过实时搜索获取而非依赖内置知识。不用于:具体功能的代码实现、安全漏洞审计(用security-audit)、产品需求分析(用product-manager)、只需一句话回答的技术常识问题。

Why use Solution Architect on TypingMind?

Because you install it once and use it with any model. Solution Architect is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Solution Architect in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/staruhub/ClaudeSkills/tree/main/skills/Geek-skills-solution-architect. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Solution Architect?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Solution Architect?

As many as you like. As long as a model supports skills, you can use Solution Architect with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Solution Architect AI skill free?

Yes. It is published on GitHub by staruhub under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇