altium-local-library
暂无简介
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-08
- Stars
- ★ 0
- Forks
- 0
03 SKILL.md 正文
Goal
A local library component per MPN that the BOM can be built from directly, whose symbol and footprint have been checked against the datasheet by the agent before it is reported placed (LIB-14, LIB-17, LIB-18).
Inputs
- the MPN (or LCSC number) and the project's local library (
libs\or the project's LIB folder) - the part record (
parts.py get <MPN>), the database library (kit global library, or the user's DbLib)
Rules to load
rules/03_LIBRARY.md(LIB-04, LIB-10..18),rules/02_REQUIREMENTS_CALCS_PARTS.md(RQ-01, RQ-03, RQ-09)- playbook
rules/playbooks/P11_new_local_component.md(and P2, P4 for writing libraries)
Approach
- Record first (RQ-01): no record, no component. Datasheet from the maker first, LCSC second.
- Reuse before build (LIB-10): copy the symbol, footprint and 3D model from the database library; a similar part's item is only a starting point and is checked like a new one.
- Name = MPN exactly. Parameters from the record, all hidden except Comment (LIB-14). LCSC, Mouser, DigiKey confirmed on their pages or written UNCONFIRMED (RQ-09).
- The datasheet check is yours, every time, even under time pressure (LIB-18): pins, pads, holes, pin 1, package. Say what you checked and any mismatch in the report.
- Source order (LIB-17): the DbLib first, then the kit global library, then build. The DbLib is read-only: never
change it. Every copy is made consistent with the kit rules and its source recorded (
lib_audit.py source). - Mark it
checkedafter your datasheet check; only the user marksconfirmed(LIB-19). - Client work: the client's rules in
standards/local/clients/<client>/win for their parts (LIB-20). PLACEHOLDER: local file layout and parameter names until the user's or the client's rules settle them.
Exit checks
| Check | How | Pass when |
|---|---|---|
| LIB-01..03 | python tools\scripts\pin_match.py <SchLib> <PcbLib> --style |
PASS |
| LIB-18 | report lists pins, pads and package checked against datasheet pages | every new or copied item |
| RQ-01 | python tools\scripts\parts.py check <MPN> |
PASS |
| LIB-17, LIB-19 | python tools\scripts\lib_audit.py --only <id> |
only check: checked left (the user confirms) |
Write back
PROJECT.md: components added, their source (copied from / built), mismatches found and their decision
Escalate when
The datasheet and the copied footprint disagree (hole size, pitch, pin order); no record can be built (no datasheet); a DbLib is read-only and the user wants the change in the database itself.
04 同仓库更多 Skills
altium-rule-harvest
Turn the user's design feedback from a project into rule, guideline and user-standard proposals, plus upkeep that keeps the rules small; use at the end of every design stage, or when asked what the kit should learn from a design.
altium-orchestrator
Pick the next step in an Altium board project under projects/<name>/; use at the start of a design session or when unsure which phase, rules or playbook apply.
altium-jlc-quote
Get JLCPCB PCB + assembly quotes for one or more boards at several quantities through the browser, including the full cost when parts are short on stock, and deliver an Excel workbook and a screenshot document; use when the user asks for a JLC (PCBA) quotation or price.
altium-fab-package
Build and check the production package for the manufacturer (Gerber zip, BOM, CPL, README, optional assembly drawing) from an Altium or KiCad design, with BOM alternates and a CPL checked by numbers; use when the user asks for fab, production or assembly files.
altium-component-intake
Get a number about a part from the component database, or add a part met for the first time (datasheet download, extraction, check); use whenever a design needs a pin, rating, package or application value of a part.