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.
Molecule boards go onto a kind board page with a self-made GLB: the flow never hands off to molecule-publish
Molecule boards go onto a kind board page with a self-made GLB: the flow never hands off to molecule-publish
What happened. AM32 ESC 2S-6S run, adom-aiflow 0.2.47, 2026-11-03. The spec has a molecule block, and the board is a 40 x 40 mm large-pin molecule with MP1 to MP4 and 11 machine contacts. finish, export and deliver passed, and finish-guard said complete. The board was then published following the AI Flow skills, and came out as a plain project page:
- kind
board; - a GLB the AI converted with step2glb and bound to
component.parts.model_3d; model statusreportsbuildsThisPage: false, so the wiki's model registry never built the model, footprint or symbol;- the molecule cannot be imported into Hydrogen with wire attach points.
Where the flow leads the AI the wrong way
tools/project-page.py(make_page) always creates the page withadom-wiki page create ... --kind board, even when the spec declares a molecule.The
aiflow-project-pageskill, step 2: "Explicitly setcomponent.parts.model_3dto the reviewed complete board/assembly GLB". On a molecule page the registry serves its own model, and molecule-publish refuses a pushed GLB (REGISTRY_MODEL_FILE_REFUSED).The
aiflow-moleculeskill, section 5: "hand the bundle (STEP, board, every schematic sheet,.kicad_pro, custom 3D models, the GLB and the footprint and symbol JSON) to the molecule-publish skill". molecule-publish 3.0.0 refuses the GLB and the footprint and symbol JSON. What it needs is the STEP, the board, the schematic,<slug>-fab.zipandexport.json, whichkicad-export-moleculebuilds with molecule-publish'sfab_bundle.py.Nothing tells the AI that molecule-publish is a separate package or how to install it:
package.jsondepends only on adom/adom-lbr and adom/adom-fields;- no
NEXT:orHint:line fromexport,finishordelivernames it; finish-guardreports complete while the molecule is unpublished.
The skill was not installed in this workspace (45 packages); bootstrap issue adom/hydrogen-bootstrap#9.
Suggested change
- When the spec has
molecule, create the page with--kind molecule. Do not push a GLB or bindmodel_3dfor it, and say why in the aiflow-project-page skill. - Make the molecule publish a step after
exportfor molecule specs. Its proof would be a passed registry build:model statusshowing themodelslot with originpipelineandmetadataComplete: true.finish-guardshould not report complete before that step. - Have
exportwrite the molecule bundle (<slug>-fab.zipandexport.jsonthroughfab_bundle.py create) from the same saved board as the Gerbers, or call kicad-export-molecule's steps. - Correct the bundle list in aiflow-molecule section 5. Add
adom/molecule-publish(andadom/kicad-export-molecule) todependencies.
Related: the contact naming issue filed alongside this one (contacts named J<n> pass molecule check, while the registry counts only MC<n>).