科研 Skill
产品需求转电子架构设计
specs-engineer
Turns a product brief into numbered requirements, an electronic architecture with power rails and pin budget, and a first BOM with a real part per function. Use to choose chips.
SKILL.md
Specs engineer
You decide what is inside the product: the architecture and one real part per function, with two alternatives each. You do not research every part in depth. electronics-researcher does that. You make the choices that the research then confirms or overturns.
Talk to the user in the user's language. Files are in English.
Prerequisites
Run commands from inside this skill's own directory (the folder containing this SKILL.md), since script and reference paths below (such as scripts/foo.py) are written relative to it, not to the project root.
Inputs
hw/brief.md(fromproduct-discovery). Required. If it is missing, runproduct-discoveryfirst.hw/power/(frombattery-and-power), when it exists: battery volume and the current budget.hw/mech/(fromenclosure-engineer), when it exists: board outline, height available per zone.hw/decisions.md: earlier decisions. Do not reopen a logged decision without a new fact.
Outputs
hw/requirements.md: numbered requirements. Template:references/requirements-template.md.hw/architecture.md: Mermaid block diagram, rails table, bus table, pin budget, and the architecture comparison.hw/bom.csv: canonical BOM, columns exactly as in CONVENTIONS §5. Starter:templates/bom.example.csv.hw/power/rails.json: rail definitions used byscripts/bom_check.py. Starter:templates/rails.example.json. Ifbattery-and-powerowns this file already, add rails throughhw/state.jsonopen_questionsinstead.hw/decisions.md: one entry per architecture or part choice (D-NNN).
Method
Work in this order. Each step writes to a file, so the next step and the other skills can read it.
1. Requirements
Read the brief and write hw/requirements.md. Each requirement has an ID, a measurable target, a hard limit, a priority and its source in the brief.
- Convert experience language into numbers. "Lasts a working day" becomes
REQ-0xx: autonomy ≥ 12 h of continuous recording, target 16 h. "Fits in a pocket" becomes an envelope in mm. - Write the environment as requirements: sweat, rain, drops, temperature, UV, skin contact.
- Write the regulatory markets as requirements. They decide radios, battery shipping and labeling. See
compliance-planner. - Mark each requirement
must,shouldorcould. If twomusts conflict, for example size against autonomy, stop and ask the user which one gives. Show the numbers.
2. Functions
List the functions the hardware must perform: sense, compute, store, connect, power, charge, indicate, actuate, protect. List one row per function with its requirement IDs. A function with no requirement is scope creep. Ask before keeping it.
3. Candidate architectures
Sketch two or three architectures. Examples:
- single SoC versus SoC plus a radio companion;
- on-board storage versus streaming only;
- one board versus a main board plus a flex.
Pattern shapes and typical part families are in references/architecture-patterns.md. Compare the candidates in a table:
| Criterion | What to estimate |
|---|---|
| Area and height | silicon and passive area in mm², tallest part in mm |
| Power | average and peak current per mode, from datasheet typicals × 2 until measured |
| Cost | silicon at 1k units |
| Lifecycle and supply | in mass production, second source |
| SDK | maturity, drivers for every peripheral |
| Risk | the riskiest part and why |
| Certification | radios and markets |
Recommend one candidate, say why in two sentences, and log it in hw/decisions.md. Ask the user only when the choice changes what the product does, for example dropping Wi-Fi to reach the size. Otherwise decide and tell them.
4. Component per function
For each function, pick a primary part and two alternatives. Run every candidate through references/selection-checklist.md. The checklist is not optional: it covers the traps that kill designs late.
Fill hw/bom.csv:
mpnis the full orderable number, with the packaging suffix.size_max_mmcomes from the datasheet's maximum dimensions.supply_rail_vis the rail name fromrails.json.key_specsholdskey=valuetokens separated by;.scripts/bom_check.pyreads these:vdd=1.7-3.6,i2c=0x2C,bus=I2C0,vio=1.8.evidenceisassumptionuntilelectronics-researcherverifies the row.- Leave price columns empty rather than guessing. If you must estimate, tag the row
estimateand state the basis innotes.
Include the parts people forget:
- passives that set height or area (inductors, bulk capacitors, crystal);
- antenna and matching network;
- test points or a programming connector;
- ESD protection on every external contact;
- battery protection;
- connectors, springs and contacts;
- the LED window or light pipe, membranes and the label.
5. Rails, buses and pins
In hw/architecture.md:
- Rails table. For each rail, give the source, nominal voltage, tolerance, average and peak load, and every part on it. The rail must sit inside every part's supply range. One low-voltage part, such as a 1.8 V-only memory or mic, can force a rail, and that rail can exclude another part, such as an LED driver that needs at least 2.5 V.
- Peak path. Put the largest simultaneous peak (radio TX plus flash program plus LED) against the battery C-rate, the protection IC, the PMIC discharge limit and the regulator limits.
- Bus table. For each bus, list every device, its address, speed and voltage. Address conflicts and level mismatches show up here, and an address can change with the part's variant.
- Pin budget. List every signal against the SoC package's GPIO count and special functions (PDM, I2S, QSPI, ADC, NFC, wake). The smaller package of the same SoC often has fewer GPIO.
6. Check and hand off
-
Run the linter:
python3 scripts/bom_check.py hw/bom.csv --rails hw/power/rails.jsonFix every error. Explain or fix every warning. The rail checks come from
battery-and-power'scheck_rails.py, imported bybom_check.py; both scripts give the same verdict. -
Ask
electronics-researcherfor a dossier per part (hw/parts/<MPN>.md), primaries first, the riskiest first. -
Send the battery, PMIC and power budget to
battery-and-power. -
Ask
doability-reviewto challenge the architecture before the PCB starts.
When research overturns a part, update the BOM row, log the decision, and rerun the linter.
Gate
The PCB and enclosure work starts only when all of these hold:
- Every
mustrequirement maps to at least one BOM row, or is marked infeasible with the user's agreement. bom_check.pyexits 0.- Every IC row has
evidence = verified, with its dossier inhw/parts/. - No primary part is "early sampling", "preview", NRND, EOL or special-order only, unless the user accepted it as a logged risk with a fallback part.
- The rails table and the peak path show margin. "It might work" is not margin.
- The pin budget fits the chosen package, with at least 2 spare GPIO.
Taste and pitfalls
These mistakes have been made on real projects:
- Assuming the mic port. A MEMS mic can be bottom-port, with the sound hole on the pad side, which needs a hole through the board. The design assumed top-port. The port direction decides the board hole, the gasket and the enclosure opening. Read it in the datasheet title and drawing.
- Truncated MPN. "BM23FR0.6-16DS" is a family, not an orderable part. The suffix sets height, plating and reel size. Distributors return the wrong part, or none, for a truncated number.
- Nominal heights. An LED listed at 0.25 mm can be 0.35 mm maximum. That 0.1 mm became a pocket in the enclosure. Stack-ups use maximums.
- Ignoring the rail. An RGB driver was planned on the 1.8 V rail, but it needs VCC of at least 2.5 V. Check
vddagainst the rail for every IC. - Over-sized parts for simple jobs. A 20-pin trackpad controller was chosen to sense one electrode. A single-channel touch controller is smaller, cheaper and has fewer lifecycle risks.
- Choosing from memory. Never place a part whose datasheet nobody has opened. Training memory gets packages, heights and lifecycle wrong. Mark such rows
assumptionand send them to research. - Lifecycle traps. "Active" at a distributor can be "early sampling" at the maker, and the smallest package of an SoC is often the last to reach mass production. Suffixes like "QN" can mean special order only.
- Silent peaks. Wi-Fi TX peaks of about 250–400 mA exceed small wearable PMICs, whose discharge limits are around 100–125 mA, and tiny cells. If a radio peak cannot be fed, drop the radio or change the power path.
- Stock-only planning. One distributor with 500 pieces is not a supply chain. A part with zero authorized stock and no date needs a fallback before layout.
- Cost blindness. A single part, such as a large NAND, can be most of the silicon cost. Show the top three cost drivers in the architecture comparison.
- Scope creep. Every extra sensor costs area, power, firmware and certification time. Keep only what a requirement needs.
References
references/requirements-template.md: structure ofhw/requirements.md, with examples. Read it at step 1.references/architecture-patterns.md: common product shapes and part families per function. Read it at step 3.references/selection-checklist.md: the per-part checklist. Read it at step 4, for every part.scripts/bom_check.py: BOM linter. Run--helpfor the options.templates/bom.example.csvandtemplates/rails.example.json: starter files for a fictional product.
示例提示词
帮我把这份产品简报转成具体的元器件选型和框图架构。
所属插件
安装该插件会一并获得同领域的 63 个 Skill / MCP。
同插件的其他科研 Skill
- ANDES电力系统动态仿真Runs ANDES power-system dynamic studies via PowerMCP: power flow, eigenvalue analysis, and time-domain simulation. Use for damping, stability, or oscillation-mode questions.
- 电池选型与电源预算Builds an evidence-tagged power budget and sizes a manufacturable battery with pouch outline, seals, and derating. Use when sizing runtime, mAh, charging, or supply rails.
- FPGA比特流生成与烧录Generates a Xilinx FPGA bitstream and programs it over JTAG, or burns an MCS image into flash for power-on boot. Use when flashing a board or diagnosing boot failures.
- 硬件项目发布包组装Assembles a hardware release package (fab files, BOM/CPL, carts, assembly guide, hashed manifest) and runs a ready-to-build gate. Use before ordering prototypes.
- 时钟域交叉风险审查Audits clock-domain-crossing risk on an FPGA design and applies the smallest safe synchronizer or constraint fix. Use to resolve CDC violations before sign-off.
- 硬件产品认证合规规划Plans certifications a hardware product needs per target market (FCC, CE/RED, UKCA, battery/radio rules), with cost and lead-time estimates. Use before PCB or enclosure tooling.
- Vivado XDC时序约束编写Authors a Vivado XDC timing constraint set from scratch: clocks, I/O delays, and timing exceptions. Use first, before timing closure, on a design with no or incomplete constraints.
- N-1/N-2应急违规处置Playbook for N-1/N-2 contingency violations: ranks contingencies and proposes preventive and corrective actions. Use after a study shows voltage or thermal problems.
- 潮流计算不收敛诊断Playbook for power-flow convergence failures in PSS/E, PSLF, PowerWorld, pandapower, PyPSA, surge, or OpenDSS. Use when a case diverges or fails to solve.
- 硬件成本核算与采购Prices a hardware product at multiple volumes with one-time vs per-unit cost, landed cost per country, and sourcing leads. Use to estimate unit cost before a pitch.
- RTL仿真覆盖率收敛Measures RTL simulation code coverage and iteratively closes it toward a target by adding testbench stimulus. Use for a sign-off-grade coverage report.
- 配电网DER接纳能力治理Playbook for distribution DER hosting-capacity limits: voltage rise, reverse flow, and thermal limits from PV and storage. Use to estimate how much DER a feeder can host.
- 电子电路设计与审查Designs, audits, or corrects an electronic circuit from a brief, schematic, or netlist, checking power domains, reset sequencing, and ratings. Use for circuit review.
- 硬件可制造性红队审查Red-team audit that fix-loops a hardware project to ready-to-build, re-deriving parts, rails, battery physics, and cost. Use for a reality check before committing to a design.
- 电力系统动态稳定处置Playbook for dynamic stability problems: poor damping, angle instability, or sustained oscillations from eigenvalue or time-domain studies. Use after an unstable study result.
- Egret电力市场调度优化Runs Egret market/operations optimization (DC-OPF, AC-OPF, unit commitment) via PowerMCP. Use for cheapest dispatch, unit commitment, or congestion checks.
- 电子元器件选型核查Researches electronic components against primary sources: part numbers, datasheet limits, lifecycle, stock, and price breaks, one dossier per part. Use to verify or source a BOM.
- EMC电磁兼容预测试Plans grounding, shielding, and filtering for EMC/EMI, and runs an emissions pre-scan with a root-cause fix sequence. Use before a lab test or after a failed EMI scan.
- 产品外壳参数化建模Designs a hardware enclosure as parametric CAD with STEP/STL/GLB output, a DFM check, and Blender assembly validation. Use when designing a case or checking fit.
- 电网频率响应问题处置Playbook for frequency problems: low inertia, high RoCoF, weak primary response, or UFLS risk after loss of the largest unit. Use when a study flags frequency issues.
- FPGA RTL到比特流全流程Drives a Xilinx FPGA design end to end through RTL, simulation, synthesis, implementation, and bitstream, gated at every stage. Use to run the complete build flow in one pass.
- 硬件产品全流程总协调Leads a physical electronic product from idea to a doable design, coordinating specs, parts, battery, PCB, enclosure, render, and cost sub-skills. Use starting a hardware product.
- 硬件原理图与BOM审查Reviews hardware projects: checks schematics against datasheets, pin connections, and firmware-to-hardware alignment across KiCad/Altium files. Use for a design alignment check.
- FPGA ILA在线逻辑调试Inserts an Integrated Logic Analyzer, programs the board, arms a trigger, and reads captured waveforms on real FPGA hardware. Use when sim passes but the board fails.
常见问题
产品需求转电子架构设计能做什么?
Turns a product brief into numbered requirements, an electronic architecture with power rails and pin budget, and a first BOM with a real part per function. Use to choose chips。
如何安装产品需求转电子架构设计?
在科搭 Codar 左侧点击「插件」,在「组件」页签搜索「产品需求转电子架构设计」并安装;在 Claude Code 或 Codex 中可以发送本页的安装提示词,或下载 Skill 包后解压到 ~/.claude/skills 或 ~/.codex/skills。
产品需求转电子架构设计需要哪些权限?
该科研 Skill没有声明额外权限;执行具体操作时仍由 Agent 按自身规则请求确认。
产品需求转电子架构设计经过官方审核吗?
是。SpeedSkills 收录的每个版本都会记录内容摘要与权限声明,当前版本已通过安全审核。