component-spec-audit
Audit exact electronic-component identities and evidence, and run the end-to-end workflow for adding or replacing a component. Use whenever circuit, schematic, PCB, BOM, firmware, bring-up, substitution or documentation work could depend on a component rating, pin, package, source, CAD asset, publication or interaction.
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- component-spec-audit
- description
- Audit exact electronic-component identities and evidence, and run the end-to-end workflow for adding or replacing a component. Use whenever circuit, schematic, PCB, BOM, firmware, bring-up, substitution or documentation work could depend on a component rating, pin, package, source, CAD asset, publication or interaction.
02 资源文件 5
- 参考文档references/contract.md3.8 KB
- 参考文档references/direct-routing.json392 B
- 参考文档references/external-vendor-qualifiers.json48 B
- 参考文档references/inventory.json772 B
- 参考文档references/new-component-workflow.md9.6 KB
03 SKILL.md 正文
Component spec audit
Protect the design from plausible-looking but wrong component claims. Manufacturer documents are the authority for component behavior; the inventory is the list of orderable identities; each owner bundle is the evidence for one exact component. The canonical workflow is circuit/WORKFLOW.md; this skill is its entry for component work.
Audit existing components
-
Run the validator before relying on any record:
pnpm exec zudo-circuit-doc validate(
pnpm circuit:checkruns the same command.) Note pre-existing failures before editing, and read theSCOPE:line: with the manual inventory provider, placements are declared, not bound to a schematic. -
Resolve the component through
references/inventory.jsonby exact manufacturer and complete MPN, supplier order code, function or placement, then load the owner bundle named by the line'sowner_skill. A bare base name is not an identity. Load subordinate records directly; never answer a subordinate query from its parent. -
Read the owner's
manifest.json,sources.json,facts.json,coverage.json,routing.json,interactions.jsonandpin-map.json. Standalone and subordinate records get the same rigor. -
Keep the contract's distinctions: source authority versus availability, fact class, provenance, conditions, calculation dependencies and the six verdicts, spelled exactly. The frozen prose is the package's contract.md.
-
Cross-check claims against the pin map and the current design state. For effects that span components, also load circuit-spec-integration.
-
If an authoritative source cannot be retrieved, or its retained extract does not support the claim, report
SOURCE UNAVAILABLEandUNSOURCED. Never reconstruct a fact from memory or from a same-name or family part. -
Report exact fact IDs, source IDs, locators, conditions, calculations and one allowed verdict. Keep proposed design changes separate from the audit result.
Add or replace a component
Follow the new-component workflow in order. It covers identity, the owner bundle, the manual inventory profile, optional CAD, the publication selection, regeneration and checks, and it is the only onboarding procedure; do not create a separate catalog-update skill.
Start a new owner bundle with:
pnpm exec zudo-circuit-doc new-component SUFFIX
Replace every placeholder value the template contains; the validator fails on any that remain. Keep downloads in the ignored .circuit-cache/sources/ directory, retain short normalized extracts in sources.json, and use pnpm exec zudo-circuit-doc validate --online or --refresh-source SOURCE_ID only for an explicit source refresh.
04 同仓库更多 Skills
component-spec-audit
暂无简介
component-spec-audit
Audit exact electronic-component identities and evidence, and run the end-to-end workflow for adding or replacing a component. Use whenever circuit, schematic, PCB, BOM, firmware, bring-up, substitution or documentation work could depend on a component rating, pin, package, source, CAD asset, publication or interaction.
circuit-spec-integration
Audit behavior that spans more than one exact component, such as shared supplies, signal boundaries, startup and reset states, protection, sensing, thermal coupling, firmware assumptions and as-built state. Use whenever a question, substitution or design change involves several component records or a stage beyond a single datasheet.
component-example
Resolve exact EXAMPLE-MPN component limits and application constraints. Use whenever EXAMPLE-MPN, its LCSC ID, manufacturer, function, pins, package, substitution, bring-up, or firmware behavior is relevant.
component-xfcn-board-headers
Audit the exact XFCN PZ254V-11-06P C492405 male and PM254V-11-06-H85 C2832269 female six-position 2.54 mm board-to-board headers. Use for Boards P/L pin order, orientation, footprint, ratings, mating, stock, alignment, or substitution.
component-umw-ao3401a-c347476
Audit the exact UMW (Youtai Semiconductor) AO3401A C347476 P-channel load-switch MOSFET. Use for Board P Q1 identity, gate polarity, pinout, ratings, SOA, thermal behavior, bring-up, or substitution decisions.