by adom
Create a wiki component page the RIGHT way. Pages are keyed manufacturer-mpn and scoped to ONE DATASHEET, so a datasheet covering six voltages and three packages is ONE page covering all of them, never six pages. Two manufacturers publishing the same MPN are two pages, because their limits genuinely differ. Renders through a hand-built readme.html on the Adom theme tokens with a fixed ten-section shape (identity, at a glance, specifications, symbol+footprint viewers, pin map, variants, assets, i
§4: solder paste jet layer — what the embed already bakes, and the two rules around it #2
Adds a "Solder paste jet layer (300 µm dots)" paragraph to §4 Build the CAD.
Why: John's AI built ~40 component pages and the question came up whether the skill tells the AI to produce the jet-dot layer. It does, implicitly: adom-footprint embed bakes the dispensing positions (0.30 mm dots on a fixed pitch, 0.06 mm inset, 0.55 mm keep-out around exposed-pad thermal vias, cap 600) as the viewer's "Solder paste jet" layer. This makes that explicit so nobody asks a model to invent a dot pattern or hand-places dots, and adds two rules: record the datasheet's exposed-pad paste coverage in Provenance when it exists, and ship the machine-readable plan (adom-footprint paste --file part.kicad_mod --out part.paste.json, adom-footprint PR #1) once the installed version has the subcommand.
No other text changed.
🤖 Generated with Claude Code
Diff Skip to comments
@@ -1,317 +1,337 @@⋯ 154 unchanged lines ⋯ > **`adom-footprint` 1.0.20 ships the fab, silk and courtyard layer groups EMPTY** (both `embed` and `render`), so the component outline is invisible and you get floating pads with no body. `scripts/inject_layers.py` parses the `.kicad_mod` graphics and fills them, and widens the viewBox (which is computed from copper only, so courtyards clip). Tracked as adom/adom-footprint#2. Drop the workaround once that lands. +**Solder paste jet layer (300 µm dots).** Adom jets paste dot by dot (Essemtec Puma, VDST-1560+valve), so a component page carries the dispensing positions, not just the F.Paste stencil+aperture. `adom-footprint embed` computes and bakes them for you: a grid of 0.30 mm dots on a+fixed pitch, inset 0.06 mm from every SMD paste aperture, dropped where a dot would sit over+an exposed-pad thermal via (0.55 mm keep-out), capped at 600. They appear in the viewer's+Layers panel as **"Solder paste jet"** (off by default; the "Paste apertures" layer is the+stencil view). Nothing to draw or decide: do not ask the AI to invent a dot pattern, and do+not hand-place dots. Two rules:++- **Exposed pads:** the dots land in the via gaps by design; if the datasheet's stencil+ recommendation gives a paste coverage (%) for the thermal pad, put that number in the+ Provenance section so the placer can window it. No number in the datasheet: say so.+- **Machine data:** the embed is a picture. `adom-footprint paste --file part.kicad_mod+ --out part.paste.json` exports the same positions as data (footprint-local mm, KiCad +y+ down, with the constants and the via keep-outs) for a placer to turn into board+ coordinates (`adom-footprint` PR #1, 2026-09-17; ship the JSON beside the `.kicad_mod`+ once your installed version has the subcommand). Until then the overlay is the reference+ and the board tool derives its program from the board's paste layer.+ **Do NOT ship generated Fusion `.lbr` or Altium `.IntLib`/`.SchLib`/`.PcbLib`.** They are generated rather than hand-verified and the Altium symbol encoder has produced wrong geometry before. Ship the placeholder from §6 instead. Generated-but-unchecked CAD on a public page is worse than a gap, because a reader assumes it was verified. ---⋯ 154 unchanged lines ⋯ | `scripts/inject_layers.py` | Fills the empty fab/silk/courtyard groups in an adom-footprint embed | | `scripts/build_switcher.py` | Wraps N footprint embeds into one package switcher | | `reference/worked-example.md` | The AMS1117 build end to end, every command in order |+
Comments
Log in to comment.
No comments yet.