AGENT SKILL

component-spec-audit

Audit exact electronic-component identities and run the end-to-end workflow for adding or replacing a BOM part. Use whenever circuit, schematic, PCB, BOM, firmware, bring-up, substitution, or related documentation could depend on a component rating, pin, package, source, preview, 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 run the end-to-end workflow for adding or replacing a BOM part. Use whenever circuit, schematic, PCB, BOM, firmware, bring-up, substitution, or related documentation could depend on a component rating, pin, package, source, preview, publication, or interaction.

02 资源文件 25

03 SKILL.md 正文

Component spec audit

Protect the design from plausible-looking but wrong component claims. Treat the generator specs as the placement identity lock and manufacturer documents as the authority for component behavior.

Audit existing components

  1. Run python3 .claude/skills/component-spec-audit/scripts/validate.py before relying on the registry.
  2. Resolve every relevant line through references/inventory.json by exact MPN, LCSC ID, manufacturer alias, function alias, board, or refdes. Load its owner_skill directly. Do not answer a subordinate-record query only from the parent component.
  3. Read the owner skill's local manifest.json, sources.json, facts.json, coverage.json, routing.json, interactions.json, and pin-map.json. Apply the same standard to standalone and subordinate records.
  4. Preserve the distinctions in contract.md: source authority and availability, fact class, provenance, conditions, derived dependencies, and verdict vocabulary.
  5. Cross-check claims against generated connectivity and symbol-to-footprint pin maps. For multi-component effects, also load the integration skill.
  6. If an authoritative source cannot be retrieved or its retained extract does not support the claim, report SOURCE UNAVAILABLE and UNSOURCED; never reconstruct a fact from memory or a generic/same-name part.
  7. Report exact fact IDs, source IDs, locators, conditions, calculations, and one allowed verdict. Keep design changes separate from the audit result.

Add or replace a BOM component

This is the sole end-to-end owner for onboarding. Follow the new-component workflow in order; do not create a separate catalog-update or onboarding skill. It covers the schematic identity lock, evidence bundle, KiCad assets, explicit public selection, previews, generated documentation, and deployment checks.

For a record-only update, copy assets/component-skill-template/, retain every required file, and follow references/schema.json. Give subordinate records independent IDs, sources, facts, locators, routing cases, and pin maps. Store normalized short evidence extracts, not vendor PDFs. Put temporary downloads only in ignored tmp/pdfs/ and remove them after extraction.

Run the validator and unit tests after edits:

python3 .claude/skills/component-spec-audit/scripts/validate.py
python3 -m unittest discover -s .claude/skills/component-spec-audit/scripts -p 'test_*.py'

Use --online only for an explicit source refresh; it downloads into tmp/pdfs/, rejects stale hashes, and does not alter retained evidence.

04 同仓库更多 Skills

Takazudo
Takazudo/zudo-circuit-doc

component-spec-audit

暂无简介

★ 0
Takazudo
Takazudo/zudo-circuit-doc

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.

★ 0
Takazudo
Takazudo/zudo-circuit-doc

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.

★ 0
Takazudo
Takazudo/zudo-circuit-doc

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.

★ 0
Takazudo
Takazudo/zudo-circuit-doc

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.

★ 0
Takazudo
Takazudo/zudo-circuit-doc

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.

★ 0