--- id: daily-component-search name: "component-search" url: https://skills.yangsir.net/skill/daily-component-search author: diodeinc domain: hardware tags: ["hardware-development", "pcb-design", "automation", "documentation"] install_count: 788 rating: 4.20 (3 reviews) github: https://github.com/diodeinc/pcb --- # component-search > 在 Zener 项目中搜索和添加电子元件、模块和参考设计，避免手动创建不兼容的组件 **Stats**: 788 installs · 4.2/5 (3 reviews) ## Before / After 对比 ### 元件选型与集成 **Before**: 手动查阅数据手册、绘制元件封装、验证兼容性，一个新元件需要 2-4 小时，常因参数不匹配返工 **After**: 搜索预验证的元件库，自动匹配参数和封装，一键添加到项目，兼容性自动校验，10 分钟完成 | Metric | Before | After | Change | |---|---|---|---| | 集成时间 | 180分钟 | 10分钟 | -94% | ## Readme # component-search # Component Search Find and add components, modules, and reference designs to a Zener project. Use this workflow any time you need a part or subcircuit that isn't already in the workspace or covered by stdlib generics. ## Hard Stop Before Manual Creation If `pcb search` and `pcb new component` do not produce a usable part, do not manually create the component, symbol, or footprint by default. Briefly say what failed, say you can try making it manually, and get explicit user confirmation first. In interactive mode, prefer `ask`. ## Search Priority Always search in this order. Move down only when the higher tier doesn't have what fits. - **`pcb search -m registry:modules -f json`** — Pre-designed, validated subcircuits (modules and reference designs). Best option: the design work is already done, with passives, layout, and validation included. - **`pcb search -m registry:components -f json`** — Pre-packaged component definitions in the registry. Good: symbol, footprint, and `.zen` file already exist and are ready to use. - **`pcb search -m web:components -f json`** — Diode's web component database (CSE, LCSC sources). Fallback: returns a `component_id` that must be imported with `pcb new component`. If the user asks for a specific MPN, still try registry first before falling back to web. ## Search Tips - **Registry search** is richly indexed — it supports MPN search, manufacturer name search, semantic/functional queries, and lexical keyword matching. Use descriptive queries freely: `"buck converter 3.3V"`, `"Texas Instruments LDO"`, `"USB-C connector"`. - **Web components search is strict MPN-only.** Only use exact or partial manufacturer part numbers: `"TPS54331"`, `"STM32F103C8T6"`. Do NOT include descriptions, keywords, or functional terms in the query — they will cause the search to fail or return irrelevant results. Strip everything except the MPN. - All commands output JSON with `-f json`. Parse results programmatically to evaluate options. - Registry results include `dependencies` (what they use) and `dependents` (who uses them) for context. - Web results include `model_availability` showing whether ECAD and STEP models are available. The same MPN may appear from multiple sources (DigiKey, CSE, LCSC) with different model availability; check all returned results before concluding models are unavailable. - **Try multiple queries.** Parts go by different names — full MPN, base family, orderable variant, manufacturer alias. If the first search doesn't find what you need, try alternative names before giving up. - Use `pcb doc --package @` to inspect a registry module's io/config interface before using it. ## Choosing Between Results Pick when there's a clear winner. Present tradeoffs and ask only when genuinely ambiguous. Selection heuristics in priority order: - **Functional fit** — does it meet the electrical requirements? - **ECAD + STEP availability** — strongly prefer results with both models available. - **Package** — prefer leadless packages (QFN, DFN, LGA, WLCSP) over leaded alternatives (SOIC, TSSOP, QFP) when multiple package options exist. - **Sourcing** — prefer in-stock parts. Check `availability` fields for stock counts and pricing. - **Source quality** — for web:components, prefer CSE source over LCSC. - **Registry adoption** — more `dependents` in registry results means more battle-tested. ## Using Registry Results Registry modules and components (Flows 1 and 2) are used directly via `Module()` with the registry URL. Auto-dep handles `pcb.toml` updates automatically — just use the URL and build. ``` # Reference design from registry:modules search LDO = Module("github.com/diodeinc/registry/reference/AP2112Kx/AP2112Kx.zen") LDO( name="LDO_3V3", VIN=vbus_5v0, VOUT=vdd_3v3, GND=gnd, ) ``` ``` # Component from registry:components search TPS54331 = Module("github.com/diodeinc/registry/components/TPS54331D/TPS54331D.zen") ``` Use `pcb doc --package @` to check available io/config before wiring into a design. ## Importing Web Components Web component results (Flow 3) require an import step before use. - Search: `pcb search -m web:components -f json` - Pick a result and extract its `component_id`, `part_number`, and `manufacturer`. - Import: ``` pcb new component --component-id --part-number --manufacturer ``` This downloads the symbol, footprint, and STEP model, scans the datasheet, and generates a `.zen` file into `components///`. If the component already exists in the workspace, it skips and reports the existing path. - Use the imported component via `Module()` with the local workspace path: ``` ESP32 = Module("./components/Espressif_Systems/ESP32-S3-WROOM-1-N16R8/ESP32-S3-WROOM-1-N16R8.zen") ``` ## Command Reference ### Search ``` # Modules and reference designs (fast, local index) pcb search -m registry:modules -f json # Pre-packaged components (fast, local index) pcb search -m registry:components -f json # Web component database (network, slower, MPN-ONLY queries) pcb search -m web:components -f json ``` ### Import ``` # Import a web component into the workspace pcb new component --component-id [--part-number ] [--manufacturer ] ``` ### Inspect ``` # Read a registry package's io/config interface pcb doc --package @ ``` ## Verifying Sourcing with `pcb bom` After adding components to a design, use `pcb bom` to check sourcing and availability: ``` pcb bom boards/MyBoard/MyBoard.zen -f json ``` The JSON output is a list of BOM entries, each with: - `designator`, `mpn`, `manufacturer`, `package`, `value`, `description` - `availability` — per-entry sourcing data: `us` / `global` — regional summary with `price`, `stock`, `alt_stock` - `offers` — individual distributor offers with `region`, `distributor`, `stock`, `price` ### Fixing BOM issues - **"No house cap/resistor found"** warnings during build mean no pre-qualified generic part matches the spec. Adjust the value, package, or voltage rating, or specify an explicit `part=Part(mpn=..., manufacturer=...)` where appropriate. - **Low stock or no offers** — search for alternative parts using the component search flows above, then update the design. - **Checking availability** — look at `stock` counts across regions. Parts with zero stock and only `alt_stock` may have long lead times. Weekly Installs501Repository[diodeinc/pcb](https://github.com/diodeinc/pcb)GitHub Stars212First SeenMar 17, 2026Security Audits[Gen Agent Trust HubPass](/diodeinc/pcb/component-search/security/agent-trust-hub)[SocketPass](/diodeinc/pcb/component-search/security/socket)[SnykWarn](/diodeinc/pcb/component-search/security/snyk)Installed onclaude-code498opencode56gemini-cli56amp56cline56github-copilot56 --- *Source: https://skills.yangsir.net/skill/daily-component-search* *Markdown mirror: https://skills.yangsir.net/api/skill/daily-component-search/markdown*