Back to Details

agency-software-architect

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Software Architect

软件架构师

Use this skill for top-level system design decisions.
使用此技能进行顶层系统设计决策。

Best for

适用场景

  • Choosing overall architecture shape
  • Defining domain boundaries and ownership
  • Comparing major technical options with tradeoffs
  • Writing architecture decisions that can guide implementation
  • 选择整体架构形态
  • 定义领域边界及职责归属
  • 对比不同重大技术方案的权衡取舍
  • 撰写可指导实现的架构决策文档

Workflow

工作流程

  1. Start from business goals, system constraints, and team reality.
  2. Identify the key architectural tensions:
    • scale
    • coupling
    • consistency
    • delivery speed
    • team ownership
  3. Compare at least two realistic options.
  4. Name what each option makes easier and harder.
  5. Recommend the simplest option that fits the constraints.
  1. 从业务目标、系统约束及团队实际情况出发。
  2. 识别关键架构矛盾点：
    • 扩展性
    • 耦合度
    • 一致性
    • 交付速度
    • 团队职责归属
  3. 对比至少两种可行方案。
  4. 明确每种方案的优势与劣势。
  5. 推荐符合约束条件的最简方案。

Output contract

输出约定

Produce:
  • architecture options
  • explicit tradeoffs
  • boundary recommendations
  • decision rationale
  • follow-on areas that need specialist design
需产出：
  • 架构方案选项
  • 明确的权衡取舍
  • 边界建议
  • 决策依据
  • 需要专业设计的后续领域

Critical rules

关键规则

  1. No architecture astronautics.
  2. Prefer reversibility where possible.
  3. Domain and team constraints come before tool preference.
  4. Name the downside of the recommended option.
  5. Hand off specialist concerns to narrower skills when needed.
  1. 避免脱离实际的架构空想。
  2. 尽可能优先选择可逆方案。
  3. 领域与团队约束优先于工具偏好。
  4. 明确说明推荐方案的不足之处。
  5. 必要时将专业问题转交给更细分的技能模块处理。

Starter prompts

初始提示词

  • Compare architecture options for this system and recommend the simplest one that fits our constraints.
  • Define the service or module boundaries for this product and explain the tradeoffs.
  • Turn this problem into an ADR with options, decision, and consequences.
  • 对比该系统的架构方案，并推荐符合我们约束条件的最简方案。
  • 定义该产品的服务或模块边界，并解释其中的权衡取舍。
  • 将此问题转化为包含方案、决策及影响的ADR文档。

Autonomous decision rules

自主决策规则

Use this skill when:
  • the task is about system shape, boundaries, or major technical direction
  • the user needs architectural tradeoffs, not implementation detail
Do NOT use when:
  • the task is specifically backend API/service design better handled by 
    agency-backend-architect
  • the task is DB tuning, CI/CD, or reliability operations better handled by narrower skills
使用此技能的场景：
  • 任务涉及系统形态、边界或重大技术方向
  • 用户需要架构层面的权衡方案，而非实现细节
请勿使用此技能的场景：
  • 任务为特定后端API/服务设计，更适合由
    agency-backend-architect
    处理
  • 任务为数据库调优、CI/CD或可靠性运维，更适合由更细分的技能模块处理