app
KiCad - the KiCad Bridge
Public Made by Adomby adom
Reference implementation of the KiCad bridge: multi-instance Python server, forward path via kicad-cli, reverse path via in-process plugin. Most complex of the three bundled bridges.
← Commit history
astra placement prompt: dollar cost and plan share in the reported numbers
1 file changed
+1−1
docs/esc-placement-astra-prompt.md+1−1@@ -21,7 +21,7 @@ Rules that are not optional: 5. Record before the first move: on arav-rog `desktop_record_start {"monitor": 0, "audio": false, "fps": 30, "reason": "Astra placing the ESC G431", "maxDurationMs": 1200000}` (foreground OpenGL path); on a user's box `desktop_record_window_start {"hwnd": H, ...}` with the fallback canvas. Then land the plan with `kicad_move_footprint` in batches (six to twelve parts per call is a good rhythm for a viewer; one undo step per call), passing the previous reply's revision as `expectedRevision`. Pause about a second between batches. Do not speed anything up; the video is cut to the action later. 6. Finish with `kicad_placement_validate`; report its ratsnest length, overlap count, outside count and placement DRC. Then `desktop_record_stop`, `pull_file` the MP4, check frames at the start, middle and end, transcode to 1920 wide H.264 (`ffmpeg -i in.mp4 -vf scale=1920:-2 -c:v libx264 -crf 22 -pix_fmt yuv420p -movflags +faststart -an out.mp4`), make a poster, and push both to the adom/codex page under docs/videos/ (`adom-wiki repo push adom/codex --files ...`), confirming the MP4 URL returns 200.-7. The numbers, all of them, in the issue: (a) planning time, from your first `kicad_placement_state` to your first `kicad_move_footprint`; (b) placement time, first commit to last commit, wall clock, and the number of commits; (c) the validate result; (d) your session's token usage (input, cached, output) for this task from Codex's own accounting, and the model name; (e) how many sub-agents or worker threads you spawned for this task (zero is a fine answer); (f) the list of calls with timestamps. Say what you rejected or retried.+7. The numbers, all of them, in the issue, because they go on a chart next to Claude Fable 5.1's: (a) planning time, from your first `kicad_placement_state` to your first `kicad_move_footprint`, wall clock; (b) placement time, first commit to last commit, wall clock, and the number of commits and parts moved; (c) the validate result: ratsnest mm, courtyard overlaps, parts outside the outline, parts still parked, placement DRC errors; (d) your session's token usage for this task from Codex's own accounting (input, cached input, output) and the model name; (e) the dollar cost of those tokens at OpenAI's published per-token API price for that model (state the price you used and where it is published) and that cost as a percentage of a $200 per month plan; (f) how many sub-agents or worker threads you spawned for this task (zero is a fine answer); (g) the list of bridge calls with timestamps; (h) what you rejected or retried, including any take you discarded. Claude's numbers for comparison are in https://wiki.adom.inc/api/pages/adom/kicad-bridge/files/demo/placement/fable/fable-stats.json: report yours in the same shape. 8. File the issue: `adom-wiki issue create adom/kicad-bridge --category show-and-tell --title "Astra placement video: ESC G431, 149 parts through kicad_move_footprint" --body "<video URL, poster URL, the numbers in 7, the exact commands>"`. No em dashes. 9. Close KiCad with `kicad_close {"discardChanges": true}` and tell John the issue URL and the video URL.