eda-architect

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

EDA Architect Skill

EDA 架构师技能

Define the architecture and constraints for electronics projects.
为电子项目定义架构与约束。

Auto-Activation Triggers

自动触发条件

This skill activates when:
  • User asks to "design a board", "create a project", "start a new PCB"
  • User asks "what do I need for..." an electronics project
  • Project has no
    docs/project-spec.md
    or
    docs/design-constraints.json
  • User mentions requirements gathering or project planning
当以下情况发生时,该技能将激活:
  • 用户请求“design a board”“create a project”“start a new PCB”
  • 用户询问“what do I need for...”这类电子项目相关需求问题
  • 项目中不存在
    docs/project-spec.md
    docs/design-constraints.json
    文件
  • 用户提及需求收集或项目规划

Context Requirements

上下文要求

Requires: Nothing (this is the first step)
Produces:
  • docs/project-spec.md
    - Human-readable specification
  • docs/design-constraints.json
    - Machine-readable constraints
前置依赖: 无(这是项目的第一步)
产出物:
  • docs/project-spec.md
    - 人类可读的项目规格文档
  • docs/design-constraints.json
    - 机器可读的设计约束文件

Workflow

工作流程

1. Understand the Project Goal

1. 理解项目目标

Ask the user about:
  • What is this device/board intended to do?
  • Target use case (prototype, production, hobby)?
  • Any existing designs to reference?
向用户询问以下信息:
  • 该设备/电路板的核心用途是什么?
  • 目标使用场景(原型验证、批量生产、业余爱好)?
  • 是否有可参考的现有设计方案?

2. Define Power Architecture

2. 定义电源架构

Determine:
  • Input power source (USB, battery, mains, PoE, solar)
  • Voltage rails needed (3.3V, 5V, 12V, etc.)
  • Power topology per rail: LDO vs buck converter
    • See
      reference/POWER-TOPOLOGY-DECISION.md
      for decision tree
  • Estimated power budget
  • Battery life requirements if applicable
确定以下内容:
  • 输入电源类型(USB、电池、市电、PoE、太阳能)
  • 所需电压轨(3.3V、5V、12V等)
  • 各电压轨的电源拓扑:LDO vs 降压转换器
    • 可参考
      reference/POWER-TOPOLOGY-DECISION.md
      中的决策树进行选择
  • 预估电源预算
  • 若涉及电池供电,明确电池续航要求

2.5 Thermal Budget

2.5 热预算

Estimate early:
  • Total power dissipation (sum of all consumers)
  • Hot components (any >0.5W needs attention)
  • Cooling strategy: natural, forced, heatsink
  • See
    reference/THERMAL-BUDGET.md
    for estimation guide
提前完成以下预估:
  • 总功耗(所有用电组件的功耗之和)
  • 高功耗组件(任何功耗>0.5W的组件需重点关注)
  • 散热策略:自然散热、强制散热、散热片
  • 可参考
    reference/THERMAL-BUDGET.md
    中的估算指南

3. Processing Requirements

3. 处理性能需求

Establish:
  • MCU/processor needs (or if needed at all)
  • Processing requirements (speed, peripherals)
  • Memory requirements (Flash, RAM)
  • Preferred families (STM32, ESP32, RP2040, etc.)
明确以下内容:
  • MCU/处理器需求(或判断是否需要处理器)
  • 处理性能要求(运算速度、外设支持)
  • 内存需求(Flash、RAM)
  • 偏好的芯片系列(STM32、ESP32、RP2040等)

4. Connectivity & Interfaces

4. 连接性与接口

Document:
  • Wireless: WiFi, Bluetooth, LoRa, Zigbee, cellular
  • Wired: Ethernet, USB, CAN, RS485, RS232
  • User interfaces: buttons, LEDs, displays
  • Debug/programming interfaces
记录以下接口信息:
  • 无线连接:WiFi、Bluetooth、LoRa、Zigbee、蜂窝网络
  • 有线连接:Ethernet、USB、CAN、RS485、RS232
  • 用户交互接口:按键、LED、显示屏
  • 调试/编程接口

4.5 Stackup Decision

4.5 电路板叠层决策

Determine layer count based on complexity:
  • 2-layer: Simple, LDO only, low-speed (I2C/SPI)
  • 4-layer: MCU with switching regulator, USB, Ethernet, WiFi
  • 6-layer: High-speed (>100MHz), DDR, dense routing
  • See
    reference/LAYER-COUNT-DECISION.md
    for decision tree
根据设计复杂度确定电路板层数:
  • 2层板:适用于简单设计,仅使用LDO、低速接口(I2C/SPI)
  • 4层板:适用于带开关稳压器的MCU、USB、Ethernet、WiFi等设计
  • 6层板:适用于高速(>100MHz)、DDR、高密度布线的设计
  • 可参考
    reference/LAYER-COUNT-DECISION.md
    中的决策树

5. Sensors & I/O

5. 传感器与I/O

List:
  • Required sensors
  • Analog inputs/outputs
  • Digital I/O requirements
  • Any specialized interfaces (motor control, etc.)
列出以下内容:
  • 所需传感器类型
  • 模拟输入/输出需求
  • 数字I/O需求
  • 特殊功能接口(如电机控制接口)

6. Physical Constraints

6. 物理约束

Define:
  • Target board dimensions
  • Enclosure requirements
  • Mounting hole positions
  • Connector placement constraints
  • Height restrictions
定义以下物理限制:
  • 目标电路板尺寸
  • 外壳适配要求
  • 安装孔位置
  • 连接器布局约束
  • 组件高度限制

7. Environmental

7. 环境要求

Note:
  • Operating temperature range
  • Indoor/outdoor use
  • IP rating if applicable
记录以下环境参数:
  • 工作温度范围
  • 室内/室外使用场景
  • 若适用,明确IP防护等级

8. Manufacturing Targets

8. 制造目标

Capture:
  • Target quantity
  • Assembly method (hand, reflow, turnkey)
  • Layer count preference
  • Budget constraints
明确以下制造相关信息:
  • 目标产量
  • 组装方式(手工焊接、回流焊、一站式服务)
  • 电路板层数偏好
  • 预算约束

8.5 DFM Early Constraints

8.5 可制造性设计(DFM)早期约束

Capture manufacturer capabilities:
  • Preferred manufacturer (JLCPCB, PCBWay, OSHPark)
  • Assembly method constraints
  • Fine-pitch components (affects hand soldering)
  • Budget tier: prototype, low-volume, production
确认制造商的能力边界:
  • 偏好的制造商(JLCPCB、PCBWay、OSHPark)
  • 组装方式限制
  • 细间距组件(会影响手工焊接可行性)
  • 预算等级:原型验证、小批量生产、大规模量产

Output Format

输出格式

project-spec.md Structure

project-spec.md 结构

markdown
undefined
markdown
undefined

Project Specification: [Name]

项目规格:[项目名称]

Overview

概述

[Brief description and goals]
[项目简要描述与核心目标]

Requirements Summary

需求摘要

CategoryRequirement
Power Input...
Voltage Rails...
MCU...
Connectivity...
分类需求内容
输入电源...
电压轨...
MCU...
连接性...

Detailed Requirements

详细需求

[Sections for each category with full details]
[各分类对应的完整需求细节]

Constraints

约束条件

[Physical, environmental, budget constraints]
[物理、环境、预算等约束]

Open Questions

待解决问题

[Any unresolved items]
undefined
[所有未明确的事项]
undefined

design-constraints.json Schema

design-constraints.json Schema

See
reference/CONSTRAINT-SCHEMA.md
for full schema documentation.
完整的Schema文档请参考
reference/CONSTRAINT-SCHEMA.md

Guidelines

指导原则

  • Ask clarifying questions rather than assuming
  • Suggest common solutions when user is unsure
  • Flag potential issues early (power budget, space constraints)
  • Keep the spec focused - avoid scope creep
  • Document rationale for key decisions
  • Use project templates from
    reference/PROJECT-TEMPLATES.md
    as starting points
  • 优先提出澄清问题,而非主观假设需求
  • 当用户不确定时,提供通用解决方案建议
  • 尽早标记潜在风险(如电源预算不足、空间约束冲突)
  • 保持规格文档聚焦核心需求,避免范围蔓延
  • 记录关键决策的理由
  • reference/PROJECT-TEMPLATES.md
    中的项目模板为起点开展工作

Architecture Validation Warnings

架构验证警告

Before completing the architecture phase, check for these risky combinations:
ConditionWarning
2-layer + switching regulator"Consider 4-layer - switching regulators need solid ground plane"
2-layer + USB/Ethernet"Controlled impedance difficult on 2-layer - consider 4-layer"
>2W total + no thermal plan"Add thermal budget - high power needs planning"
Hand assembly + fine-pitch (<0.5mm)"Verify solderability - fine-pitch is difficult to hand solder"
>0.5W component + no thermal strategy"Component dissipating >0.5W needs thermal attention"
Battery + LDO with high Vin-Vout"Consider buck converter for battery life"
When a warning condition is detected, present it to the user and ask if they want to:
  1. Update the design to address it
  2. Acknowledge the risk and proceed
在完成架构定义阶段前,需检查以下高风险组合:
条件警告内容
2层板 + 开关稳压器“建议考虑4层板 - 开关稳压器需要完整的接地层”
2层板 + USB/Ethernet“2层板难以实现受控阻抗 - 建议考虑4层板”
总功耗>2W + 无散热方案“需补充热预算规划 - 高功耗设计必须提前考虑散热”
手工组装 + 细间距(<0.5mm)“需验证可焊性 - 细间距组件手工焊接难度极大”
组件功耗>0.5W + 无散热策略“功耗>0.5W的组件必须制定散热方案”
电池供电 + 高输入输出压差的LDO“为提升电池续航,建议替换为降压转换器”
当检测到上述警告条件时,需向用户展示风险并询问:
  1. 是否更新设计以解决该风险
  2. 是否确认风险并继续推进

Next Steps

后续步骤

After completing architecture, suggest:
  1. /eda-source [component-role]
    to begin component selection
  2. Start with critical components: MCU, power regulators
完成架构定义后,建议执行以下操作:
  1. 使用
    /eda-source [component-role]
    命令启动组件选型工作
  2. 优先完成核心组件选型:MCU、电源稳压器