科研 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.

发布者 Codar安全审核通过v0.1.0更新于 2026-11-18

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's CONVENTIONS.md §4), hw/state.json, and the final presentation in hw/presentation/.

Start

  1. Run toolchain-setup in check mode (doctor). Report what is missing. Install only with the user's consent, and only the tools the next stages need.
  2. Create hw/ and copy templates/state.json from this skill to hw/state.json.
  3. If hw/ already exists, read hw/state.json and resume from the first stage that is not done. Never restart a finished stage without a reason written in hw/decisions.md.
  4. 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]
#StageSkillGate to leave the stage
1Discoveryproduct-discoveryThe user approved hw/brief.md
2Architecture and partsspecs-engineerrequirements.md, architecture.md and draft bom.csv exist; bom_check.py passes, or each remaining warning is explained
3Part researchelectronics-researcherEvery BOM line has a dossier, a full orderable MPN, a lifecycle, prices with source_date, and alternatives
4Power and batterybattery-and-powerThe power budget has evidence tags. The battery is a cell a vendor can make. A measurement plan exists
5Paper reviewdoability-reviewNo open NO-GO. Each GO-WITH-CHANGES has an owner stage
6Enclosure and PCBenclosure-engineer, pcb-engineerThe 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
7Assembly validationenclosure-engineer (validator)0 interpenetrations and 0 broken meshes. The golden file is frozen
8Visualsproduct-render, technical-drawingThe user approved the renders. The blueprint has every BOM item
9Businesscost-and-sourcing, compliance-planner, prototype-roadmapCosts at 1/10/100/1k/10k with NRE separated; certifications per market; roadmap with a critical path
10Final review and fix loopdoability-review, then the owner skillsEvery 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
11Build packagebuild-packagerelease_check.py passes on hw/release/<rev>/
12Presentationproduct-presentationhw/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-review verdict (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's release_check.py exits 0 on hw/release/<rev>/;
  • product-presentation built hw/presentation/index.html with 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

  1. Ask what changes the product; decide the rest. Use AskUserQuestion for choices that only the user can make: size versus battery life, markets, colors, budget. Put the recommended option first. Log every decision in hw/decisions.md.
  2. 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.
  3. Evidence on every number (CONVENTIONS.md §6). When a stage reports a number without a tag, send it back.
  4. One owner per file. Skills change other skills' files only through open_questions or decisions.md.
  5. Validate before you show. Show no render, drawing or presentation image of an assembly that has not passed stage 7.
  6. 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.
  7. Freeze the golden state. After stage 7, geometry changes only through a new validated build. Appearance changes go on the frozen file.
  8. 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.
  9. 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.
  10. 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.md so 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.

示例提示词

我想做一款可穿戴设备,帮我把从需求到定型的全流程协调起来。

所属插件

电子电气与信息工程面向电气与电子工程研究:电力系统仿真(PSS/E、PSLF、PowerWorld、pandapower、PyPSA、OpenDSS、ANDES)与越限/稳定/短路处置,FPGA 时序收敛与跨时钟域检查,电路与 PCB 设计评审,硬件产品开发流程。

安装该插件会一并获得同领域的 63 个 Skill / MCP。

同插件的其他科研 Skill

常见问题

硬件产品全流程总协调能做什么?

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 收录的每个版本都会记录内容摘要与权限声明,当前版本已通过安全审核。