科研 Skill

硬件产品认证合规规划

compliance-planner

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.

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

SKILL.md

Compliance planner

Find out what the product must pass before it can be sold in each market. Find out what it costs and how long it takes. Find out which design decisions make it cheaper. Write the result to hw/compliance.md.

Talk to the user in the user's language. Files are in English unless the user's project uses another language.

This is a planning aid, not legal advice. Say so once in the output, and do not repeat it in every paragraph. Never present a fee, date or rule as confirmed unless you read it in a primary source during this session.

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

FileWhat you take from it
hw/brief.mdtarget markets, launch order, quantities, who the users are (children?), where the product is used
hw/architecture.mdradios, frequencies, TX power, internet connectivity, firmware updates
hw/bom.csvradio module or chip-down, battery chemistry, membranes, plated parts that touch skin
hw/power/battery chemistry, capacity, Wh, removable or not, charger
hw/mech/IP claim, openings, how the enclosure is sealed, skin-contact materials

If a trait is missing, ask the user only when it changes the result: markets, radios, battery type, body-worn use, recording. Otherwise assume the stricter case and tag it [assumption].

Outputs

  • hw/compliance/traits.json: product traits (format in templates/traits.example.json).
  • hw/compliance/matrix.md: generated by scripts/compliance_matrix.py.
  • hw/compliance.md: the plan, built from templates/compliance.md.
  • Entries in hw/decisions.md for each design lever the user accepts.
  • Entries in hw/state.json → open_questions for items that other skills own. Examples: TX cap → firmware, battery door → enclosure-engineer, UN 38.3 in the cell contract → battery-and-power.

Procedure

  1. Collect the traits. Fill hw/compliance/traits.json from the inputs. Use the market codes US CA EU UK BR JP KR CN AU IN. List the radios as ble, bt_classic, wifi, nfc, gnss, lte, subghz, lora, zigbee, thread or uwb. Set product_category, for example item_finder or wearable: item finders trigger the unwanted-tracking (DULT) rule.

  2. Run the matrix:

    python3 scripts/compliance_matrix.py --traits hw/compliance/traits.json --out hw/compliance/matrix.md --show-skipped
    

    Test the script with python3 scripts/test_compliance_matrix.py.

    The rules live in references/rules.json. Each rule has conditions, a cost range, a lead time, an evidence level and design levers.

    • Project-local rules: if the product has a trait that no rule covers, research it and write the rule in hw/compliance/rules.local.json, with the same schema. The script loads that file automatically from next to the traits file, or from --local-rules <file>. It merges the rules by id: a known id replaces the toolkit rule, "disabled": true removes it, and a new id is added. The matrix names every local change. Propose generic rules upstream to references/rules.json.
    • Battery chemistry: battery.chemistry can be a list when a cell is two things at once, for example ["coin-cell", "li-primary"] for a CR2032.
    • Totals: a market's rows list everything that market requires, so shared requirements (RoHS, RF exposure, coin-cell clauses) appear in several markets. Budget with the bold Total, all target markets (each row once). Do not add the market rows together.
  3. Read the "Read first" block. It lists:

    • BLOCKING rows, for example no sale in Brazil before homologation;
    • CRITICAL PATH rows, for example UN 38.3 of a custom cell;
    • DESIGN RISK rows, for example EU battery removability with a glued enclosure.

    Report each of these to the user in plain words.

  4. Verify what matters most. Pick the three to five rows with the highest cost or schedule impact. Try to read the primary source:

    • the regulator's page or the official journal (eur-lex, fcc.gov/KDB, gov.br/anatel);
    • the program's fee page (bluetooth.com).

    Change a row's tag to [verified: …, date] only when you read it. If a portal blocks you (CAPTCHA, 403), write that down and leave the row as an estimate.

  5. Apply the design levers. For each lever in references/design-levers.md that fits the product, state the saving and the trade-off:

    • module or chip-down radio;
    • TX power cap;
    • number of openings;
    • battery door or exception;
    • no mains adapter;
    • catalogue or custom cell;
    • cybersecurity from day one;
    • hardware recording indicator.

    Recommend one option for each, and log the user's decision.

  6. Write hw/compliance.md. Use the template. The answer comes first: can it be sold, what blocks it, what to change, the budget and the longest path. Then give per-market detail, the levers, the schedule hooks for prototype-roadmap, what was verified, the RFQs to send and the open questions.

  7. Hand off.

    • cost-and-sourcing takes the certification NRE (low and high).
    • prototype-roadmap takes the schedule hooks.
    • doability-review takes the blocking items and design risks.

Gate

The compliance stage passes when:

  • every target market has a matrix section, and no market is "unknown";
  • every BLOCKING and DESIGN RISK item has an owner and a decision, or an open question in hw/state.json;
  • the certification budget (low and high) and its lead times are in hw/compliance.md, with evidence tags;
  • the RFQ list names at least two labs or certification bodies for the main market.

Taste and pitfalls

  • Launching "just a small batch" before certification. A launch batch of 100 units is still a sale. In markets like Brazil, radio products without homologation cannot be sold, and customs can hold them. Plan a pre-sale with delivery after certification.
  • A custom cell inherits nothing. The vendor's catalogue cells may have UN 38.3 and IEC 62133-2, but a new shape is a new model. Its reports sit on the critical path before air shipping and before certification samples travel.
  • The 3D model is not the certified product. Radio tests run on final hardware with final RF firmware settings. Antenna tuning inside the real enclosure, on a body, comes first.
  • "Uses a certified module" does not mean "no certification". The end product still needs EMC, a declaration, labels, often its own certificate (Brazil) and sometimes RF exposure.
  • A sealed, glued enclosure can be illegal in the EU from 2027-02-18 unless an exception applies. Settle this before tooling.
  • Plated parts on skin. Nickel-plated magnets, contacts or clasps that touch skin trigger nickel-release limits. Keep them inside, or choose another finish.
  • Membranes and PFAS. ePTFE vents and acoustic membranes are fluoropolymers. Qualify a PFAS-free alternative early.
  • Bluetooth costs USD 11.5–12k per product even with a qualified chip [verified: bluetooth.com, 2026-11-08]. First-time hardware teams often miss this.
  • Use only established labs and certification bodies. Never recommend unknown "certificate agents".
  • Write numbers once. The matrix holds the rows. hw/compliance.md holds the decisions and the summary, and refers to the matrix instead of copying it.

References

  • references/rules.json: the rule data used by the script. Update it when you verify a rule.
  • references/markets.md: how each market's process works (applicant, labs, labels, typical timing). Read it when you write the per-market section.
  • references/design-levers.md: decisions that remove tests or shorten the schedule. Read it in step 5.
  • templates/traits.example.json: traits for a fictional BLE fitness band.
  • templates/compliance.md: the output template.

示例提示词

这款硬件要卖到欧美和中国市场,帮我梳理需要做哪些认证。

所属插件

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

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

同插件的其他科研 Skill

常见问题

硬件产品认证合规规划能做什么?

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。

如何安装硬件产品认证合规规划?

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

硬件产品认证合规规划需要哪些权限?

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

硬件产品认证合规规划经过官方审核吗?

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