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.
main
John Lauer
0.1.38: clip posters, capture finds the reopened editor, large clips pulled in parts, KiCad 10 silkscreen application written down
be3c9c2
6d ago
AI Flow 0.1.38
- Clips show a still before they play. The wiki renders
<video>withpreload="none", so a clip with no poster is an empty black box until clicked, and a clips page full of them looks broken.clipsnow writes a poster for each 10x cut (a frame 40 percent in,<stem>-poster.jpg), pushes it with the media, and emitsposter="..." preload="metadata". The aiflow-live-clips skill says to do the same for any video embedded by hand. capture startfinds the editor that is open now. It used the run's stored window handle, which dies when the editor is closed and reopened for an offline edit, so the recorder did not start. It now asks the bridge for the live PCB editor first (the 3D tour does the same).- Large clips come across in parts. When the pulls of a clip fail (a 17-minute clip was 2.7 GB), aiflow splits it on the desktop into 200 MB parts with PowerShell, pulls each, joins them and keeps the result only when its size matches.
- Silkscreen application in KiCad 10 is written down in aiflow-silkscreen and aiflow-power-layout: the offline and live halves, the text verb's
rotationfield and its stroke cap (0.32 mm is the smallest legal text against a 0.08 mm minimum stroke), readback and native renders of both faces.
# AI Flow 0.1.38
- **Clips show a still before they play.** The wiki renders `<video>` with `preload="none"`, so a clip with no poster is an empty black box until clicked, and a clips page full of them looks broken. `clips` now writes a poster for each 10x cut (a frame 40 percent in, `<stem>-poster.jpg`), pushes it with the media, and emits `poster="..." preload="metadata"`. The aiflow-live-clips skill says to do the same for any video embedded by hand.
- **`capture start` finds the editor that is open now.** It used the run's stored window handle, which dies when the editor is closed and reopened for an offline edit, so the recorder did not start. It now asks the bridge for the live PCB editor first (the 3D tour does the same).
- **Large clips come across in parts.** When the pulls of a clip fail (a 17-minute clip was 2.7 GB), aiflow splits it on the desktop into 200 MB parts with PowerShell, pulls each, joins them and keeps the result only when its size matches.
- **Silkscreen application in KiCad 10** is written down in aiflow-silkscreen and aiflow-power-layout: the offline and live halves, the text verb's `rotation` field and its stroke cap (0.32 mm is the smallest legal text against a 0.08 mm minimum stroke), readback and native renders of both faces.