科研 Skill

硬件项目发布包组装

build-package

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.

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

SKILL.md

Build package

The toolkit delivers a design that someone can order and build without further design work. This skill collects the outputs of all stages into one release folder. It also runs the gate that decides whether the release is READY TO BUILD. If the gate fails, the release is not ready. Send each failure back to the skill that owns it, fix it there, and run the gate again. Do not patch files inside the release by hand.

Talk to the user in their language. Release files are in English unless the user chose another language.

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

PathFromUsed for
hw/release/release.jsonthis skill (you write it)revision, target level, boards, assembler, build size, enclosure parts, battery, order steps (format: templates/release.example.json, fields in references/release-config.md)
hw/pcb/<board>/ drc.json, erc.json, .kicad_pcb, .netpcb-engineerDRC/ERC = 0, routed board, pin map
hw/pcb/fab/<board>/ Gerber zip, BOM, CPLpcb-engineerfab and assembly files
hw/bom.csvspecs-engineer, electronics-researcherorderable MPNs, LCSC numbers, stock dates
hw/mech/cad/ STEP/STL, hw/mech/dfm.mdenclosure-engineerenclosure parts
hw/validation/assembly.jsonenclosure-engineerassembly passes, newer than the CAD
hw/drawings/technical-drawingthe 2D drawing PDF and exploded images
hw/power/battery-and-powerbattery spec, power-measurement thresholds
hw/cost/cost-and-sourcingcost and lead time per order step
hw/doability/doability-reviewthe overall verdict, and the "Verify on the prototype" list

Outputs: hw/release/<rev>/

README.md            what this release is, its level, how to use it
ORDER.md             numbered order steps: where, what to upload, options, cost, lead time, receiver
MANIFEST.json        every file with sha256, size and source stage
fab/<board>/         Gerber+drill zip, IPC netlist (if exported), fab-notes.md (stack-up, finish, mask, min features, stiffeners, panel)
assembly/<board>/    BOM and CPL in the assembler's format, stock.md (stock per line with date), consigned.csv, options.md
purchasing/          digikey.csv, mouser.csv (BOM-upload format), mechanical.csv, purchasing.md (quantities with attrition)
mech/                <part>.step, <part>.stl, print-settings.md, drawing PDF, mech-bom.csv
battery/             battery.md (catalog cell + holder, or the custom-cell spec for the vendor)
assembly-guide/      assembly-guide.md and its images
test/                test-plan.md (bring-up, test points, power plan with thresholds, functional tests), verify-on-prototype.md
firmware/            pins.json and pins.h for the MCU (from the netlist), when configured
checks/              copies of the reports the gate used (DRC, ERC, validator, doability) and release-check.json

Procedure

  1. Write hw/release/release.json. Copy templates/release.example.json, and set the revision (A, B…) and the target level (prototype or production). Fill in the boards, the assembler (JLCPCB first), the build size, the enclosure parts, the battery and the order steps. Take each step's cost and lead time from hw/cost/, and cite it.

  2. Write the documents that only this skill owns. Use the templates:

    • assembly-guide.md (templates/assembly-guide.md): numbered steps, exploded images from technical-drawing, adhesive and cure time, torque, and a QC check after each step;
    • test-plan.md (templates/test-plan.md): bring-up order, test points, the power-measurement plan with pass thresholds from battery-and-power, and the functional tests;
    • battery.md (templates/battery-spec.md);
    • print-settings.md (templates/print-settings.md).

    Put them in hw/release/src/. Every value comes from a stage file, and you cite its ID or path. Leave no <placeholder>, TBD or TODO.

  3. Assemble.

    python3 scripts/assemble_release.py hw/ --config hw/release/release.json
    
    • It copies the stage outputs into hw/release/<rev>/.
    • If pcb-engineer did not export them, it builds the assembler BOM and CPL from the KiCad position file and hw/bom.csv, applying the rotation offsets in the config.
    • It writes the purchase carts with attrition, the pin map, ORDER.md, README.md and MANIFEST.json.
  4. Gate.

    python3 scripts/release_check.py hw/release/<rev>/ --hw hw/
    

    It prints each failure with the owner skill and exits non-zero if the release is not READY TO BUILD (checks in references/ready-to-build.md §3). Send each failure to its owner. Re-run steps 3–4 until the gate passes. After 3 rounds, stop and show the user the remaining blockers with the exact actions.

  5. Pre-order review. Go through references/ready-to-build.md §4 with the release open. Pay attention to rotation and polarity in the assembler's preview, basic vs extended part fees, the panel, clear-part finishing and cell shipping. Record the result in hw/release/<rev>/checks/pre-order.md.

  6. Hand over. Tell the user the level, the total cost and lead time for the build size, and the first step of ORDER.md. Ordering spends money: never place an order or upload files for the user without their explicit go-ahead.

Gate

release_check.py exits 0 and the doability verdict is READY TO BUILD (prototype) or READY TO BUILD (production), matching release.json → target. A release that fails the gate is labelled NOT READY in its README, with the failure list.

Taste and pitfalls

  • "Unrouted" is not "almost done". A board with zero tracks or with unconnected items fails the gate, however good the 3D looks.
  • Stock goes stale fast. Re-check the assembler stock and distributor stock within 14 days of ordering. The gate fails older dates.
  • Rotation offsets are per footprint and per assembler. Check every polarized part (diodes, LEDs, ICs, connectors) in the assembler's 3D preview before you pay. A mirrored LED or a rotated QFN costs a whole batch.
  • One source of truth. The release copies files and never edits them. Fix a wrong value in its stage file, then assemble again.
  • The validator must be newer than the CAD. A passing report from before the last CAD change proves nothing.
  • Prototype measurements are not blockers, but they need thresholds. "Measure the current" is not a test. "Average current in mode X ≤ 1.5 mA over 10 min, measured on a PPK2 at 3.0 V" is a test.
  • Clear parts need a finishing plan. An SLA print is not clear until it is wet-sanded and coated or polished. Write the steps, otherwise the prototype looks foggy.
  • Lithium cells ship as dangerous goods. Order them to the assembly location, never in the same box as the boards from a fab that does not ship cells.

Bundled files

  • scripts/assemble_release.py, scripts/release_check.py, scripts/release_lib.py (standard library only, --help). scripts/selftest.py runs both on the fixture: 1 pass case and 11 failure cases.
  • templates/release.example.json, templates/assembly-guide.md, templates/test-plan.md, templates/battery-spec.md, templates/print-settings.md.
  • templates/example/: a test fixture (a fictional board), used only to test the two scripts.
  • references/ready-to-build.md: definitions, the gate checks and the pre-order checklist.
  • references/release-config.md: every field of release.json.

示例提示词

设计定稿了,帮我整理出可以下单生产的完整发布包。

所属插件

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

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

同插件的其他科研 Skill

常见问题

硬件项目发布包组装能做什么?

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。

如何安装硬件项目发布包组装?

在科搭 Codar 左侧点击「插件」,在「组件」页签搜索「硬件项目发布包组装」并安装;在 Claude Code 或 Codex 中可以发送本页的安装提示词,或下载 Skill 包后解压到 ~/.claude/skills 或 ~/.codex/skills。

硬件项目发布包组装需要哪些权限?

该科研 Skill没有声明额外权限;执行具体操作时仍由 Agent 按自身规则请求确认。

硬件项目发布包组装经过官方审核吗?

是。SpeedSkills 收录的每个版本都会记录内容摘要与权限声明,当前版本已通过安全审核。