app
AI Flow
Public Made by Adomby adom
Adom's AI Flow: a tool to help the AI follow all of the steps it takes to build a board.
thermal-vias --ack still lands; heatsink vias ignore silkscreen; stitchVias size defaults
Version: adom-aiflow 0.2.17, KiCad 10.0.5, KiCad Bridge 1.0.58 (Windows desktop).
Three things from one live KiCad run (a 60 x 84 mm 2-layer sensor board, readout landed live through the bridge):
thermal-vias land --ack REF --whystill lands the plan. The ack only clears the shortfall check (main.rs ThermalVias land: it runsland vias --plan <plan>whenever the plan has nets). Expected:--ack U3leaves U3's planned vias out of the landing. Workaround used: empty the plan file, thenland --ack.- The heatsink via planner ignores silkscreen. For U3 (SOT-23-5, 0.085 W) it placed six 0.6 mm vias under the part's own reference and value labels. They pass KiCad's DRC (the vias are tented), but the labels become unreadable, and
silkscreen-audit --recordthen fails for missing via boxes. Expected: existing silk text and graphics are obstacles for planned vias, as they are for the silkscreen placer. stitchViasdefault to 0.8 / 0.4 mm. Each entry can carrysizeanddrill, but nothing says so in the hint or docs/spec-example.json. The default refused a stitch via 0.15 mm from an LED pad that the board's real 0.4 mm via clears. Suggest: default to the spec's or board's via size, and name the keys in the refusal hint.
Also seen: aiflow's landing check defaulted to 0.2 mm via-to-via copper clearance, while the board's 3rd party fab pack allows 0.1 mm, and refused vias KiCad's DRC passes until clearance was set in the spec. Reading the clearance from the project's .kicad_dru would avoid that.