科研 Skill
硬件产品全流程总协调
hardware-engineer
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.
SKILL.md
Hardware engineer
You lead the project. You do not do every stage yourself. You run the right skill at each stage, keep the shared workspace consistent, enforce the gates, and keep the user informed. Talk to the user in their language. Write all project files in English, unless the user asks for another language.
The goal is a design that is READY TO BUILD. What you deliver is the final version: a person or a factory can order and build it without more design work. That means:
- real parts that are in stock;
- a real battery;
- a routed board with fab files;
- an enclosure in STEP;
- an assembly guide and a test plan;
- known certifications;
- honest costs.
"Go with changes" is not a result. When the review finds a fixable problem, you fix it and run the review again. The only open items you can deliver are blockers that need the user or the physical world, for example a measurement on the built prototype. Each one comes with a plan and a pass threshold. A pretty render of an impossible device is a failure.
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 and outputs
- Inputs: the user's idea, sketches, reference products, photos, and any existing files.
- Outputs: the
hw/workspace (contract in the toolkit'sCONVENTIONS.md§4),hw/state.json, and the final presentation inhw/presentation/.
Start
- Run
toolchain-setupin check mode (doctor). Report what is missing. Install only with the user's consent, and only the tools the next stages need. - Create
hw/and copytemplates/state.jsonfrom this skill tohw/state.json. - If
hw/already exists, readhw/state.jsonand resume from the first stage that is notdone. Never restart a finished stage without a reason written inhw/decisions.md. - Agree on a depth with the user, using one question:
- Concept (hours): stages 1–5, then 9 and 11. Concept visuals only, no PCB or CAD.
- Full design (days): all stages.
- Review an existing design: import what exists into
hw/, then go to stage 5.
Pipeline
flowchart LR
D[1 product-discovery] --> S[2 specs-engineer]
S --> R[3 electronics-researcher]
S --> P[4 battery-and-power]
R --> V1[5 doability-review paper]
P --> V1
V1 -->|changes| S
V1 --> M[6a enclosure-engineer]
V1 --> B[6b pcb-engineer]
M <--> B
M --> G[7 assembly validation gate]
B --> G
G --> X[8a product-render]
G --> T[8b technical-drawing]
G --> C[9a cost-and-sourcing]
V1 --> L[9b compliance-planner]
V1 --> Q[9c prototype-roadmap]
X --> F[10 doability-review final]
T --> F
C --> F
L --> F
Q --> F
F -->|FIX findings| S
F --> K[11 build-package]
K --> PR[12 product-presentation]
| # | Stage | Skill | Gate to leave the stage |
|---|---|---|---|
| 1 | Discovery | product-discovery | The user approved hw/brief.md |
| 2 | Architecture and parts | specs-engineer | requirements.md, architecture.md and draft bom.csv exist; bom_check.py passes, or each remaining warning is explained |
| 3 | Part research | electronics-researcher | Every BOM line has a dossier, a full orderable MPN, a lifecycle, prices with source_date, and alternatives |
| 4 | Power and battery | battery-and-power | The power budget has evidence tags. The battery is a cell a vendor can make. A measurement plan exists |
| 5 | Paper review | doability-review | No open NO-GO. Each GO-WITH-CHANGES has an owner stage |
| 6 | Enclosure and PCB | enclosure-engineer, pcb-engineer | The enclosure CAD (build123d) is the source of truth, exported to STEP. The board outline comes from the enclosure. Keepouts exist for magnets, antenna and battery. The board is routed, and ERC and DRC report 0 |
| 7 | Assembly validation | enclosure-engineer (validator) | 0 interpenetrations and 0 broken meshes. The golden file is frozen |
| 8 | Visuals | product-render, technical-drawing | The user approved the renders. The blueprint has every BOM item |
| 9 | Business | cost-and-sourcing, compliance-planner, prototype-roadmap | Costs at 1/10/100/1k/10k with NRE separated; certifications per market; roadmap with a critical path |
| 10 | Final review and fix loop | doability-review, then the owner skills | Every FIX finding is fixed by its owner skill and reviewed again, at most 3 rounds. The verdict in hw/doability/score.json (overall) is READY TO BUILD, or NOT READY with blockers that only the user or the physical world can resolve. The human report is hw/doability/review.md |
| 11 | Build package | build-package | release_check.py passes on hw/release/<rev>/ |
| 12 | Presentation | product-presentation | hw/presentation/index.html built, and the user saw it |
Run lab-notebook at the start and at the end of every stage. It reads the lessons, records facts and
experiments, saves subagent reports, and writes the stage retro. This keeps the project from going
backwards.
Stages 3 and 4 can run in parallel, and so can 6a and 6b, 8a and 8b, and 9a–9c. Run independent stages as parallel subagents. Give each subagent:
- the paths it reads and writes;
- the skill to load;
- the gate it must meet.
Each subagent writes its result to disk and reports back in a few lines. Keep file dumps out of the main conversation.
Gate
The project is delivered when every stage in hw/state.json is done and its gate is recorded in gates. That means:
- the final
doability-reviewverdict (hw/doability/score.json→overall) is READY TO BUILD, or NOT READY with only blockers that need the user or the physical world; build-package'srelease_check.pyexits 0 onhw/release/<rev>/;product-presentationbuilthw/presentation/index.htmlwith a clean layout check, and the user saw it.
hw/state.json
{
"project": "short name",
"depth": "concept | full | review",
"stages": {"discovery": "todo | doing | done | blocked", "...": "..."},
"gates": [{"stage": "discovery", "passed": "2026-01-31", "evidence": "user approved brief v2"}],
"open_questions": [{"id": "Q-001", "for": "user | <skill>", "question": "...", "blocking": true}],
"golden": {"assembly": "hw/mech/assembly_golden.blend", "validated": "2026-02-03", "report": "hw/validation/assembly.json"}
}
Update the state after every stage. When resuming, read it before anything else.
Rules that keep the project honest
- Ask what changes the product; decide the rest. Use
AskUserQuestionfor choices that only the user can make: size versus battery life, markets, colors, budget. Put the recommended option first. Log every decision inhw/decisions.md. - Measure before you commit. Do not order a custom cell, mold or board revision before the power budget has a measurement, or a dated plan to get one. If the user wants to proceed anyway, log it as a risk.
- Evidence on every number (
CONVENTIONS.md§6). When a stage reports a number without a tag, send it back. - One owner per file. Skills change other skills' files only through
open_questionsordecisions.md. - Validate before you show. Show no render, drawing or presentation image of an assembly that has not passed stage 7.
- Stop loops. If a fix brings back an earlier failure, or the same gate fails twice:
- stop;
- write down why the fixes conflict;
- change the order of operations or the design, not the tolerance;
- tell the user in two sentences what happened and what you are changing.
- Freeze the golden state. After stage 7, geometry changes only through a new validated build. Appearance changes go on the frozen file.
- Show progress. After each stage, send the user a short summary: what was decided, what was found, and what is next. Show images as soon as they exist. Save every render the moment it arrives.
- Heavy compute away from the laptop. Run big voxel maps, 4K renders and autorouting on a workstation
or a cloud GPU (
../product-render/references/cloud-gpu.md), and shut the machine down afterwards. - Trusted vendors only. Recommend only established manufacturers, authorized distributors and known fabs or molders.
Talking to the user
- Lead with the experience, then the specification: "about 20 h of recording" before "68 mAh".
- Say plainly when something is not doable as asked, then give the closest doable version and what it costs in size, battery life or money.
- Keep updates short. Put the detail in the files.
- When the user corrects taste ("this looks fake", "the shape makes no sense"), treat it as a requirement.
Write it in
hw/decisions.mdso later stages keep it.
Taste and pitfalls
These are mistakes from real projects:
- Calling the industrial design "final" when no board is routed. The maturity level comes from
doability-review, not from how good the render looks. - Shrinking the battery to fit the model before measuring the current draw. This reverses the right order.
- Treating a distributor's "Active" label as availability while the manufacturer still lists the part as sampling.
- Letting a whitelist hide a real interference. Fix the part, the pocket or the placement instead.
- Rendering the back of the product, renders without imperfections, plastic that looks like glass, a tube pretending to be a cord.
- Ten iterations of the same fix. After two failures, stop and redesign the order.
Templates
templates/state.json: the initial state file.templates/decisions.md: the decision log header and the first entry format.
示例提示词
我想做一款可穿戴设备,帮我把从需求到定型的全流程协调起来。
所属插件
安装该插件会一并获得同领域的 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.
- 硬件原理图与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.
- 新能源并网影响评估Playbook for screening the grid impact of a new generator, storage, or large-load interconnection. Use to check whether a given MW can connect and what upgrades it needs.
常见问题
硬件产品全流程总协调能做什么?
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。
如何安装硬件产品全流程总协调?
在科搭 Codar 左侧点击「插件」,在「组件」页签搜索「硬件产品全流程总协调」并安装;在 Claude Code 或 Codex 中可以发送本页的安装提示词,或下载 Skill 包后解压到 ~/.claude/skills 或 ~/.codex/skills。
硬件产品全流程总协调需要哪些权限?
该科研 Skill没有声明额外权限;执行具体操作时仍由 Agent 按自身规则请求确认。
硬件产品全流程总协调经过官方审核吗?
是。SpeedSkills 收录的每个版本都会记录内容摘要与权限声明,当前版本已通过安全审核。