fusion-export-molecule

@@ -183,9 +183,30 @@ After saving, exports may produce stale files. Workaround: 3. Switch to board view if needed: `adom-desktop fusion_electron_run '{"command":"EDIT .brd"}'` 4. Run the export steps above -## After Export — Publish+## After Export — Convert (OCCT molecule mode, recommended) -Once all files are in the user's local Downloads folder, **ask the user** whether they want to publish. Two destinations:+For a **molecule** (board with MP1-MP4 markers + machine pins), convert through+the OCCT molecule pipeline BEFORE publishing, so the package carries the+anchored GLB + footprint + symbol and downstream imports regenerate nothing:++```bash+curl -s -X POST "https://step2glb-gmdoncpxdwx0.adom.cloud/convert?molecule=true&pin=medium" \+  -H "X-Client: <agent-name>" -H "X-Job-Name: <name>" \+  -F "step=@<name>.step" -F "board=@<name>.brd" \+  # optional: -F "silk_top=@silk_top.png" -F "silk_bottom=@silk_bottom.png"+```++Poll `GET /jobs/{id}` until complete and **verify before proceeding**:+`anchored: true`, `footprint_applied: true`, sane `contact_z`, empty+`warnings[]`. Then download `/jobs/{id}/result` → `<name>.glb`,+`/jobs/{id}/footprint` → `<name>_footprint.json`, `/jobs/{id}/symbol` →+`<name>_symbol.json`, and include all three in the package below. (Plain+chips/PCBs without markers: skip this — the publish-time auto-conversion+below is enough.)++## After Convert — Publish++Once all files are staged, **ask the user** whether they want to publish. Two destinations:  ### Publish to the Adom Wiki — `adom-wiki pkg publish` (canonical; the wiki is wiki.adom.inc) @@ -240,18 +261,21 @@ adom-wiki page visibility <owner>/<slug> --preset open   # or: private  ### Publish to Hydrogen (live project use) -Hydrogen is where molecules are used in actual projects. Uses the `adom-molecule` CLI (published by John, v0.1.0).+Hydrogen is where molecules are used in actual projects. This stage is a+**handoff to the `adom-molecule-import` skill** (ships with+`adom/adom-molecule` — install via `adom-wiki pkg install adom/adom-molecule`).+Short form, after the wiki publish above:  ```bash-# Install if not present-which adom-molecule || (gh release download --repo adom-inc/adom-molecule --pattern 'adom-molecule' --output /tmp/adom-molecule-bin && sudo mv /tmp/adom-molecule-bin /usr/local/bin/adom-molecule && sudo chmod +x /usr/local/bin/adom-molecule)--# Upload to a user's Hydrogen account-adom-molecule create --name "<molecule-name>" --owner <username> \-    --usdz <name>.usdz --f3d <name>.f3d --brd <name>.brd+adom-wiki repo clone <owner>/<slug> --dir /tmp/<slug>-import   # authenticated, private-safe+adom-molecule create --owner <hydrogen-owner> --name <name> \+    --glb <name>.glb --brd <name>.brd --no-optimize ``` -The molecule becomes available at `https://hydrogen.adom.inc/<username>/molecules/<name>` and auto-queues 3D optimization (USDZ→GLB via Blender pipeline).+`--no-optimize` reuses the OCCT-converted GLB — no Blender re-optimization,+no silkscreen needed at import. Only fall back to the legacy+`--usdz/--f3d` optimization path when no GLB exists (and expect the queue).+The molecule lands at `https://hydrogen.adom.inc/<username>/molecules/<name>`.  ### Suggested prompt after export @@ -270,4 +294,10 @@ After the export completes, tell the user: - **Silkscreen capture** requires the 3D Design view, not PCB Editor. Always do Steps 4-7 after Step 3. - **pull_file from Google Drive paths** may produce empty files. Use shell_execute + base64 as a workaround if the output folder is on Google Drive. - **Shell execute needs approval** on the Adom Desktop app for each new script.-- **adom-molecule CLI** is at `adom-inc/adom-molecule` (Rust, published by John). Install via GitHub release.+- **adom-molecule CLI** installs from the wiki: `adom-wiki pkg install adom/adom-molecule` (also lays down the `adom-molecule-import` skill).++## Related++- `kicad-export-molecule` — same job from KiCad+- `altium-export-molecule` — same job from Altium (via KiCad's importer)+- `adom-molecule-import` — the Hydrogen import half (this skill's final stage)

@@ -1,6 +1,6 @@ {   "slug": "fusion-export-molecule",-  "version": "1.0.0",+  "version": "1.1.0",   "type": "skill",   "description": "Export a Fusion 360 Electronics design as an Adom molecule \u2014 orchestrates AdomBridge primitives to produce the BRD, SCH, F3D, STEP, USDZ, and silkscreen PNG source bundle the molecule pipeline (wiki, OCCT, Hydrogen) consumes. Successor to fusion-export-for-hydrogen.",   "tags": [

@@ -1,5 +1,6 @@ {   "hero": {+    "type": "billboard",     "headline": "Fusion design to molecule bundle",     "subhead": "BRD, SCH, STEP, USDZ, and silkscreen in one orchestrated export",     "screenshot": "docs/shot.png"@@ -34,5 +35,28 @@   ],   "visibility": {     "public": true+  },+  "slug": "fusion-export-molecule",+  "version": "1.1.0",+  "type": "skill",+  "description": "Export a Fusion 360 Electronics design as an Adom molecule — orchestrates AdomBridge primitives to produce the BRD, SCH, F3D, STEP, USDZ, and silkscreen PNG source bundle the molecule pipeline (wiki, OCCT, Hydrogen) consumes. Successor to fusion-export-for-hydrogen.",+  "tags": [+    "molecule",+    "fusion360",+    "export",+    "hydrogen",+    "skill"+  ],+  "dependencies": {+    "adom/adom-desktop": "^1.9.0"+  },+  "scripts": {+    "install": "./install.sh",+    "uninstall": "./uninstall.sh"+  },+  "org": "adom",+  "author": {+    "name": "Drew Owens",+    "email": "[email protected]"   } }\ No newline at end of file