Solder Components

View saved version →

---
name: component-expert
description: Answer engineering questions about an exact electronic component using Solder's component expert, including pin connections, operating limits, supporting parts, and reference circuits. Use when component selection or integration needs datasheet and reference evidence.
---

Use this plugin's `component_expert` tool. Explicit user requirements take priority over the workflow below.

The expert requires an exact public LCSC `productCode` such as `C12345`; that example is a format, not a part recommendation. If the user supplies a manufacturer part number or a family name, resolve it through `component_search` first. Preserve variant and package identity. When multiple variants differ in a way that affects the answer, establish which one the user means.

Pass the exact product code and a focused `query` containing the user's relevant operating conditions. Calls are stateless: include the facts needed for a follow-up instead of inventing a conversation or session identifier. Do not send local paths, private-library IDs, arbitrary PDF URLs, or unrelated conversation history.

Explain the returned answer in the context of the user's question. Keep datasheet source links unchanged and immediately next to the claims they support. Distinguish absolute maximum ratings from recommended operating conditions, and distinguish verified facts from suggestions or unresolved limitations. Missing evidence is not proof of suitability.

Treat `isError`, cancellation, and timeout as unsuccessful work. Report the limitation instead of turning an error into an engineering answer. Do not silently substitute the legacy `datasheet_query` tool for the full component expert.

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: component-search
description: Find and compare electronic components from LCSC, JLCPCB, DigiKey, and Mouser, including available stock and pricing observations. Use for part selection or resolving a manufacturer part number to an exact Product Code.
---

Use this plugin's `component_search` tool. Explicit user requirements take priority over the workflow below.

Preserve all electrical requirements, units and their case, package constraints, and manufacturer variant suffixes in each query. Pass `requiredQuantity` when the user specifies a quantity; stock qualification otherwise defaults to one unit. Each call accepts up to ten `queries` with a shared quantity. Use separate calls for different quantities.

When the user names distributors, pass `sources` with their choices: `digikey`, `mouser`, `jlcpcb`, or `lcsc`. More than one source may be selected. Omit `sources` to preserve the default LCSC/JLCPCB search. Use at most 16 query/source combinations per call, splitting larger requests into separate calls. Report each source's results and failures separately; never substitute another source for one that failed.

LCSC and JLCPCB share candidate discovery, so source-specific results may be incomplete. DigiKey and Mouser return `supplier_keyword` candidates, not verified engineering matches. Check the exact manufacturer part number, manufacturer, package, and electrical specifications against returned evidence or the datasheet before recommending a part. Product Codes cannot be searched directly at DigiKey or Mouser. First resolve the exact manufacturer part number using LCSC/JLCPCB, then search those distributors with that part number.

Compare returned manufacturer part numbers, Product Codes, packages, relevant specifications, quantity price breaks, supplier destinations, and availability observations. Use only prices and currencies present in the response. Distinguish completed matches from partial results and failed, cancelled, or timed-out searches. Unknown availability does not mean zero stock; observations are not stock reservations.

DigiKey keyword search reports standard pricing and stock data that can be up to 24 hours old. Distinguish this from a live stock check. Supplier-specific part numbers are not Product Codes. For `component_expert`, first resolve the exact manufacturer and manufacturer part number to a matching Product Code in the LCSC/JLCPCB catalog; do not guess an identity or merge different manufacturers.

An exact Product Code lookup can return an unavailable part so the user can inspect its identity. Do not describe it as in stock unless the returned availability supports that claim. Never invent a replacement code, missing price, supplier stock, or an electrical match.

For integration questions or constraints the returned catalog data does not establish, call `component_expert` with a returned `productCode` and the user's specific question. Keep any source links next to the facts they support. Ordinary passive value/package questions can usually be answered from catalog fields without expert research.

If these tools are unavailable, report the missing plugin connection. This plugin searches and researches parts; it does not order parts or change a design.

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: request-help
description: Send a user-approved request to Solder when the user wants a human to follow up about component questions, board design, or review services.
---

Use `request_help` only when the user wants Solder to contact them. Ask for their email address if they have not provided it. Draft a concise, accurate description of the issue or requested service using only relevant details the user has chosen to share. Show the exact email address and message to the user, explain that both will be sent to Solder so the team can follow up, and let them edit the message. Ask the user to explicitly confirm sending those exact details before calling the tool. If the user has already expressly authorized sending the same email and message, that confirmation is sufficient.

After confirmation, create a distinct UUID `requestId` for the approved submission. Call `request_help` with that `requestId`, the confirmed `email` and `issue`, and `consent: true`. Reuse the same `requestId` for retries of the same submission; create a new UUID for a new approved submission. Never ask the user for this ID. If the user changes either field, obtain confirmation of the changed details before sending. Do not send unrelated conversation history, secrets, or confidential details the user has not approved. Do not solicit a request merely because the user asked a technical question.

When the tool reports `accepted`, explain that the email provider accepted the request for delivery; do not guarantee receipt. If the tool fails, explain that acceptance was not confirmed and let the user decide whether to retry. Do not promise a response time or claim Solder has reviewed the request.

Referenced files: 1 — file references are metadata, not package contents.