app

AI Flow

Public Made by Adom

by adom

Adom's AI Flow: a tool to help the AI follow all of the steps it takes to build a board.

kicadpcbedaroutingplacementcopper poursablationcurrent densitythermalkelvincomparison
Overview Files Skills Discover Packages Releases Dependencies Issues10 Breadcrumbs Pull Requests Activity
Open feature request

Molecule board pages ship without simulation figures, an interactive schematic or a parts table (no page step on the molecule-publish path)

noah ·

A molecule's board page has no simulation figures, no interactive schematic and no parts table

Version: adom-aiflow 0.2.55 with molecule-publish 3.0.0, kicad-new lane, full-ai profile. The run was an AM32 ESC molecule, page am32-esc-mol32 (private), 2026-11-06.

What happened. The run did everything the flow asks for a molecule:

  • export, then molecule-publish: sources only, registry build passed, hero set.
  • stage end molecule-publish.

The page that came out has the 3D viewer, the hero and a plain README. Noah's first questions were:

  • "Where are the pictures of the simulations?"
  • "Where is the interactive schematic?"
  • "Where is the cool BOM?"

The run had all three to give. It ran Adom Fields current and thermal solves with figures and a rating sweep (10 A per phase in moving air, U101 the still-air limit at 6S). It had a netlist-checked schematic and a sourced BOM with Mouser prices. None of it reached the page.

What good looks like. The hands-on page of the same ESC, adom/am32-esc-v1 (private), uses a readme.html (readme_order: ["html"]) with:

  • The board and its contacts: images, and a contact table with nets and wire gauge.
  • Circuit explorer: a block flowchart; click a block to see its circuit drawn the textbook way, netlist-checked (#131).
  • Simulation: the Fields current-density and temperature maps and a table of the numbers: copper loss, worst A/mm², peak rise in still and moving air, current for +60 °C per cell count. Each layout revision is compared (#147).
  • Components: one row per BOM line with the chip's image, MPN, manufacturer, quantity, references, role, unit and line price and a buy link, plus the board total.
  • Manufacturing, flashing and pin map, then the open items.

Why it slips through. The molecule path ends at molecule-publish. That skill packages the sources plus a README.md and says nothing about the page's content. project-page (the step that writes the README) is off the molecule path since #137. finish, deliver and finish-guard accept stage end molecule-publish as proof the page is done. #131 asks for the explorer and #147 for the analysis results, but neither has a home in the molecule path. The parts table is not asked for anywhere.

Ask.

  1. A page step after export for every board, molecule or not: project-page --molecule-bundle <folder> (or page build), which writes readme.html and docs/ into the molecule-publish package folder before Stage 3:
    • board renders and the contact table, from the board and spec.molecule
    • the explorer scaffold (#131): blocks from the netlist's block field, with the textbook drawing per block left to the AI, plus the netlist check
    • the Simulation section from the run's Fields, current and thermal outcomes: figures plus a numbers table (#147)
    • the Components table from the run's BOM: chip images from each part's wiki page hero or step2glb thumbnail, prices and stock from the sourcing outcome, buy links
  2. A check that finish and deliver run (project-page check): every section present, every figure newer than the board it shows, explorer coverage 100 % with 0 netlist diffs, a BOM row for every part.
  3. molecule-publish: name readme.html and docs/ as carried files in Stage 2, and keep readme_order when page.json is merged.

1 Reply

John Lauer ·

Thanks Noah, this is a fair catch: the run had the material and none of it reached the page.

What was wrong. The molecule path ends at molecule-publish, which packages the sources and a plain README. Since #137 project-page is off that path, and nothing in AI Flow wrote the analysis results or the parts table anywhere a reader of the page would see them. The hints never said so either.

What changed (in adom-aiflow 0.2.56).

  • New: adom-aiflow project-page --results. It writes a design review sub-README, design-review/README.md, for the current board:
    • the board and its contacts (a molecule): every MP/MC part with its net, footprint and position from MP1
    • Simulation: the Fields current table (net, amps, peak A/mm², layers), the heat table (part, watts, rise in still and in moving air, peak rise), the current and thermal screens' verdicts with any failing lines, the open Fields issues, and every analysis figure you registered with artifact --kind analysis-image
    • Components: one row per BOM line with MPN, manufacturer, role, quantity, references, unit and line price and a buy link (when the BOM has those columns), a wiki link, and the board total
    • a status line that says what finish said (for example "finish ran with 16 open items; not cleared for fabrication")
  • For a molecule: project-page --results --out <molecule-publish package folder> writes design-review/ into the package before its Stage 3, so the molecule page carries it. The molecule-publish hand-off hint after export and finish now says so, and the aiflow-molecule skill does too.
  • It records which board the review describes. analyze current, analyze thermal, tour fields and finish suggest it whenever the page's review is missing, older than the board, or older than the latest analysis.

What is still open. Two things you named are not built by the binary yet, and the command lists both as open every time it runs:

  • the interactive schematic (the circuit explorer, #131): a real feature of its own, still to be done. For now link the schematic by hand.
  • chip images on the parts table: each row links the part's wiki page, which carries its hero.

There is also no project-page check that judges the page. Instead, finish names a missing or stale design review as a suggestion, because AI Flow never refuses. On the molecule-publish side, naming design-review/ as a carried file belongs in that package. I have not changed it here; the hint tells the AI to carry the folder and link it from the package README.

How it was verified. Unit tests build a review from a run with Fields numbers, a figure, a molecule contact and a priced BOM, and check every table, the page-root-relative figure paths and the total. A new workflow suite (tests/page-results-workflow.py) runs the command end to end, both to the page staging folder and into a package folder. The full unit and workflow suites pass.

Upgrade: tell your AI "give me the latest adom-aiflow" (or adom-wiki pkg install adom/adom-aiflow); adom-aiflow --version says 0.2.56.

Log in to reply.