firstcontact (wongvin) errors

3 failures reported against firstcontact (wongvin), sorted by how they fail and ranked by impact.

#177 by errors trackedElectronics & PCBEmbedded & firmware

Recurring firstcontact (wongvin) errors, by impact

  1. 1An engineer uses a netlist script with Claude Code to settle facts about KiCad boards (nets, pin maps, DNP parts), but on every board the method around it had to be rediscovered: unzip into scratch, run --check-pcb before trusting a net, read DNP flags, tag each claim with its source. Getting that wrong has cost real corrections: one review presented PDF-text readings as netlist facts, and a pin-transform bug went unnoticed until a later pass checked the netlist against the PCB. His fix is to write the procedure into an agent skill so the next review starts from it rather than from memory, tagging every fact netlist, PCB, datasheet or PDF text.Electronics & PCB · Missing capability · 1 report74
  2. 2Follow-on to #386 from last hour. His KiCad netlist skills settle circuit facts from design source, but boards designed in Altium have no equivalent: the only fallback is the schematic PDF, which produced plausible, wrong answers on the XIAO boards more than once. He tested KiCad 10's Altium importer on a 4-sheet nRF52840 keyboard: 620 pads across 151 nets, 0 split, 0 merged, then five problems. A missing library leaves the imported sheets unsaved, only the schematic gets saved with no .kicad_pcb, Value holds the library part name while the real resistance lands in ALTIUM_VALUE, variants come through per instance so his script reports 0 not-fitted parts, and the importer marked CON303 not fitted when Altium's variation actually points at CON302 by unique ID, a false DNP. kicad-cli cannot import a .SchDoc at all, so the skill has to walk a person through the GUI.Electronics & PCB · Import, export & interop · 1 report74
  3. 3Before a firmware port can rely on a board's hardware facts, its netlist script has to learn hierarchical sheets, power symbol names (it reports #PWRnn instead of VSYS_3V3) and multi-unit symbols, which an earlier run attached to the wrong pins. Until then the XIAO header pin map comes from PDF text plus pinctrl.Embedded & firmware · Wrong design output · 1 report66

How it fails

  1. Wrong design output1
  2. Import, export & interop1
  3. Missing capability1

Sourced from public community reports. Costs and delays on individual entries are modeled estimates, not measurements.