Keitark/pcba-design-skills / .agents/skills/schematic-humanizer
schematic-humanizer
VerifiedReorganize label-heavy or netlist-like electronic schematics into human-readable functional diagrams with visible local wiring while preserving proven connectivity. Use for schematic readability correction, overlapping wires or symbols, visually floating connectors or support logic, functional-sheet restructuring, bus presentation, layout annotations, or multi-EDA handoff across KiCad, Altium, EasyEDA, EAGLE/Fusion, gEDA/Lepton, SPICE/netlist, and PDF/image sources.
| File | Kind | Size |
|---|---|---|
| LICENSE | other | 1.0 KB |
| SKILL.md | skill md | 5.6 KB |
| agents/openai.yaml | config | 306 B |
| references/adapters.md | markdown | 5.0 KB |
| references/layout-handoff-annotations.md | markdown | 4.4 KB |
| references/prompt-template.md | markdown | 4.6 KB |
| references/visual-audit-checklist.md | markdown | 4.2 KB |
| references/visual-audit-record.md | markdown | 812 B |
| scripts/compare_connectivity.py | script | 13.4 KB |
references/layout-handoff-annotations.md
View on GitHub# Layout handoff annotations / レイアウト引き継ぎ注記
Add layout annotations when the user explicitly requests them or when the source
clearly exposes placement-sensitive interfaces. Do not guess hidden electrical
requirements. Ask the user only when the missing choice would materially change
the design; otherwise mark it for measurement or engineering review.
ユーザーの明示要求、または回路から配置・配線制約を明確に判断できる場合に
注記を追加する。不明な電気条件を推測しない。設計を大きく変える選択だけを
質問し、それ以外は要実測・要レビューとして明記する。
## Evidence classes / 根拠区分
- `[SPEC]`: manufacturer datasheet, interface standard, approved project
requirement, or verified measured value. Include the source in the companion
document.
- `[TARGET]`: conservative project routing allocation chosen for this revision,
such as loose group skew, firmware-rate ceiling, current capacity, or layer
preference. Explain that it is not certified timing or measured current.
- `[TBD-MEASURE]`: source capability, thermal rise, real current, unknown clock,
enclosure RF performance, or another item that cannot be proven from the
schematic.
- `[SPEC]`: データシート、規格、承認済み要件、確認済み実測値。
- `[TARGET]`: この版の保守的な設計目標。タイミング保証や実測値ではない。
- `[TBD-MEASURE]`: 電流、温度、電源能力、未知クロック、筐体 RF など要確認項目。
## What to capture / 記載項目
For each meaningful interface or rail, capture only applicable items:
1. Clock, data rate, or access cadence, plus the warning that edge rate can set
signal-integrity risk even when the clock is slow.
2. Required topology and stub rule: source → buffer/termination → receiver,
point-to-point, daisy chain, star, or explicitly forbidden branches.
3. Reference plane, layer preference, controlled impedance, spacing, and return
transition guidance.
4. Group skew or pair mismatch target. Avoid meanders when the timing budget
does not require them.
5. Provisional current allocation, shared-trunk capacity, trace/pour and via
intent, voltage-drop/thermal signoff, and measurement state.
6. Component placement: decoupling escape path, regulator loop, crystal, antenna
keepout, connector ESD, exposed-interface protection, and mechanical keepouts.
7. Authoritative manufacturer or standards URL in a companion layout guide.
クロック/データレート、エッジレート、トポロジ、スタブ、基準面、層、
インピーダンス、長さ差、暫定電流、配線幅・ビア、配置、メーカー資料を、
該当する範囲だけ記載する。
## Presentation / 表示方法
- Put short, local callouts near the relevant functional region, but outside
wires, buses, symbols, labels, and the dominant visual flow.
- Keep full calculations, current-budget tables, URLs, assumptions, and signoff
checklists in a companion Markdown/PDF document. Link it with a short on-sheet
note.
- Do not label an entire design with one clock when domains differ. Separate CPU,
memory, loader, RF, USB, and other interfaces.
- Do not add a generic impedance width/gap before the final fabricator stackup is
known. State the impedance and reference plane, then require stackup-derived
geometry.
- Treat a vendor module with an integrated antenna as a placement/keepout problem;
do not invent an RF feed trace that is not in the circuit.
注記は関連機能の近くに短く置き、配線や信号の流れを隠さない。計算、表、
完全な URL、前提、承認項目は別文書へ移す。異なるクロック領域を一つの速度
で表現せず、最終スタックアップ前に汎用線幅を固定しない。
## Required final gate / 必須最終確認
Annotations can introduce new overlaps. After adding them, follow the complete
[visual audit checklist](visual-audit-checklist.md), including every full page
and dense crops around the annotated regions. Then repeat connectivity comparison
and ERC/lint. A clean netlist does not excuse a visually obscured schematic.
注記追加後は全ページと高密度部分を再レンダリングし、目視監査、接続比較、
ERC を繰り返す。ネットリストが正しくても、注記が回路を隠す場合は不合格。
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| canvas-designanthropics/skillsCreate beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| docxanthropics/skillsUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| pdfanthropics/skillsUse this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| pptxanthropics/skillsUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |