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
- 参考文档fixtures/direct-routing.json3.3 KB
- 参考文档fixtures/golden/critical-fact-review.json19.5 KB
- 参考文档fixtures/golden/critical-facts.json2.8 KB
- 参考文档fixtures/golden/real-pin-maps.json36.8 KB
- 参考文档fixtures/invalid/contract-cases.json1.4 KB
- 参考文档fixtures/mutations/condition.json160 B
- 参考文档fixtures/mutations/default-state.json136 B
- 参考文档fixtures/mutations/locator.json187 B
- 参考文档fixtures/mutations/pin.json121 B
- 参考文档fixtures/mutations/unit.json120 B
- 参考文档fixtures/mutations/value.json122 B
- 参考文档fixtures/refresh-evidence.json774 B
- 参考文档fixtures/valid/subordinate-record.json4.6 KB
- 参考文档references/contract.md3.8 KB
- 参考文档references/external-vendor-qualifiers.json139 B
- 参考文档references/inventory.json21.4 KB
- 参考文档references/new-component-workflow.md9.3 KB
- 参考文档references/schema.json3.0 KB
- 参考文档review-artifacts/circuit-recheck-decisions.md32.9 KB
- 参考文档review-artifacts/issue-21.md3.9 KB
- 参考文档review-artifacts/issue-23.md4.0 KB
- 参考文档review-artifacts/issue-24-independent-audit.md12.5 KB
- 参考文档review-artifacts/issue-25.md7.7 KB
- 脚本scripts/test_validate.py34.2 KB
- 脚本scripts/validate.py74.7 KB
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
- Run
python3 .claude/skills/component-spec-audit/scripts/validate.pybefore relying on the registry. - Resolve every relevant line through
references/inventory.jsonby exact MPN, LCSC ID, manufacturer alias, function alias, board, or refdes. Load itsowner_skilldirectly. Do not answer a subordinate-record query only from the parent component. - Read the owner skill's local
manifest.json,sources.json,facts.json,coverage.json,routing.json,interactions.json, andpin-map.json. Apply the same standard to standalone and subordinate records. - Preserve the distinctions in contract.md: source authority and availability, fact class, provenance, conditions, derived dependencies, and verdict vocabulary.
- Cross-check claims against generated connectivity and symbol-to-footprint pin maps. For multi-component effects, also load the integration skill.
- 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 a generic/same-name part. - 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
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.