forgecad 0.10.3 → 0.10.4

package/dist-skill/website/skills/{forgecad-model-grader.md → forgecad-grade-model.md}

@@ -1,17 +1,17 @@
-<!-- Generated by scripts/build-forgecad-skill.mjs — do not edit. Edit agent-skill-library/forgecad-model-grader/SKILL.md instead. -->
+<!-- Generated by scripts/build-forgecad-skill.mjs — do not edit. Edit agent-skill-library/forgecad-grade-model/SKILL.md instead. -->
 
-# forgecad-model-grader
+# forgecad-grade-model
 
-Analyze, verify, and grade ForgeCAD or CAD-as-code models against a user requirement, design brief, prompt, reference, or acceptance criteria. Use when asked to evaluate, judge, QA, benchmark, score, rate, or compare a CAD model; render it from multiple angles, run targeted inspections when needed, visually verify the evidence, and produce a 0-10 score with concise justification.
+Grade a ForgeCAD or CAD-as-code model against a requirement, brief, prompt, reference, or acceptance criteria with evidence and a 0-10 score.
 
 | Field | Value |
 | --- | --- |
 | Installed by | `forgecad skill install` |
-| Source | `agent-skill-library/forgecad-model-grader/SKILL.md` |
+| Source | `agent-skill-library/forgecad-grade-model/SKILL.md` |
 
 ---
 
-## ForgeCAD Model Grader
+## Grade Model
 
 Grade the delivered model against the requirement, not against what could be fixed later. Never edit the model unless the user explicitly requests repairs — then record the baseline grade first, change, and re-grade.
 
@@ -21,7 +21,7 @@ Grade the delivered model against the requirement, not against what could be fix
 2. **Run the model**: `forgecad run <model>.forge.js` (in the ForgeCAD repo use the local build, `node dist-cli/forgecad.js run ...`). If it fails to execute, stop and apply the caps.
 3. **Render** at least `iso`, `front`, `right`, `top` to a scratch dir; add views (back, bottom, close-up, section) when the model is asymmetric, hollow, mechanical, or likely to hide mistakes.
 4. **Open and look at every PNG** — never score from command output alone. Check silhouette, proportions, required features, part boundaries, interfaces, and whether the model reads as the requested artifact from more than one angle.
-5. **Inspect** whenever hidden internals, fit, wall thickness, or assembly behavior are central to the brief — grading without inspecting them caps the score. Delegate evidence choice, commands, and manifest reading to the `forgecad-render-inspect` skill. Findings (unexpected collisions, thin regions, floating bodies, wrong component counts) are evidence, not warnings to wave away.
+5. **Inspect** whenever hidden internals, fit, wall thickness, or assembly behavior are central to the brief — grading without inspecting them caps the score. Delegate evidence choice, commands, and manifest reading to the `forgecad-inspect-model` skill. Findings (unexpected collisions, thin regions, floating bodies, wrong component counts) are evidence, not warnings to wave away.
 6. **Score**: fill the rubric, apply caps, give a final 0-10 in whole or `.5` increments. Unknowns count against the score.
 
 ### Rubric
@@ -47,6 +47,7 @@ Maximum scores, applied after the rubric:
 - A must-have requirement is absent: max `6`.
 - Visually recognizable but physically impossible for the requested use: max `6`.
 - Internals, fit, walls, or assembly central to the brief but uninspected: max `7`.
+- Multi-part assembly violates the ForgeCAD component model — sibling imports, assembly-space coordinates inside parts, structural `translate()` placement, missing connector mates, or parent/child data flow confusion: max `7`; max `6` when the violation makes the assembly brittle or mechanically wrong.
 - Inspection finds unexpected collisions, floating bodies, critical thin walls, or wrong connectivity: max `6`; max `5` when the defect invalidates the main function.
 - Delivered as a finished product/prototype but presented with default flat lighting (no `scene()` rig), a generically colorful or material-false palette, or teaching-diagram styling: max `8`. Does not apply when the brief asks for a blockout or bare technical study.
 - Any score relying on an assumption the evidence cannot verify: mark it `Unknown`, never score above `8`.
@@ -73,6 +74,7 @@ Next fixes: the 2-5 highest-leverage improvements.
 - Grade the default returned model unless the user names a parameter set or variant.
 - No points for comments, labels, or intentions absent from the geometry.
 - Decorative screws, floating labels, and teaching-diagram callouts are not real mechanical interfaces.
+- For multi-part assemblies, require the component model: parts build locally at origin, expose connectors/metadata, the parent positions them, and inter-part data flows through parent props and returned metadata.
 - Cite which render or inspection finding drove the grade.
 - When comparing models, use identical checklist, cameras, inspection evidence, and caps for all.
 

package/{dist/docs-raw/skills/forgecad-visual-spec.md → dist-skill/website/skills/forgecad-image-prompt.md}

@@ -1,25 +1,25 @@
-<!-- Generated by scripts/build-forgecad-skill.mjs — do not edit. Edit agent-skill-library/forgecad-visual-spec/SKILL.md instead. -->
+<!-- Generated by scripts/build-forgecad-skill.mjs — do not edit. Edit agent-skill-library/forgecad-image-prompt/SKILL.md instead. -->
 
-# forgecad-visual-spec
+# forgecad-image-prompt
 
-Turn a concrete ForgeCAD artifact, build brief, HLD, or existing model into builder-honest image prompts for AI image models. Use when the user wants visual-spec renders that show the final product while keeping mechanisms, seams, hardware, and build cues visible instead of drifting into concept art.
+Write builder-honest AI image prompts from a concrete ForgeCAD model, build brief, HLD, or LLD without hiding how the artifact is built.
 
 | Field | Value |
 | --- | --- |
 | Installed by | `forgecad skill install` |
-| Source | `agent-skill-library/forgecad-visual-spec/SKILL.md` |
+| Source | `agent-skill-library/forgecad-image-prompt/SKILL.md` |
 
 ---
 
-## ForgeCAD Visual Spec
+## Image Prompt
 
 ### Scope
 
-Only for artifacts already concrete enough to visualize (a specific `.forge.js` model, build brief, or HLD); route vague briefs to `forgecad-spec-by-walking-through-it` first. Read minimum context — entry `.forge.js`, one key helper if it delegates geometry, brief/HLD — and capture what must survive the image model: artifact type and scale, major subassemblies, actuation style, visible mechanisms, material and color cues.
+Only for artifacts already concrete enough to visualize (a specific `.forge.js` model, build brief, or HLD); route vague briefs to `forgecad-design-spec` first. Read minimum context — entry `.forge.js`, one key helper if it delegates geometry, brief/HLD — and capture what must survive the image model: artifact type and scale, major subassemblies, actuation style, visible mechanisms, material and color cues.
 
 ### Core Rule
 
-Visual-spec prompts, not concept art: show the final artifact clearly, preserve build and subsystem truth, and keep visible the seams, modules, hardware, and mechanical hierarchy that matter.
+Image prompts, not concept art: show the final artifact clearly, preserve build and subsystem truth, and keep visible the seams, modules, hardware, and mechanical hierarchy that matter.
 
 Negatives (the only negatives list — reuse it, never restate variants):
 

package/dist-skill/website/skills/{forgecad-render-inspect.md → forgecad-inspect-model.md}

@@ -1,21 +1,21 @@
-<!-- Generated by scripts/build-forgecad-skill.mjs — do not edit. Edit agent-skill-library/forgecad-render-inspect/SKILL.md instead. -->
+<!-- Generated by scripts/build-forgecad-skill.mjs — do not edit. Edit agent-skill-library/forgecad-inspect-model/SKILL.md instead. -->
 
-# forgecad-render-inspect
+# forgecad-inspect-model
 
-Run and interpret ForgeCAD inspection bundles for model verification. Use when asked to inspect a ForgeCAD model, analyze an inspection bundle, validate collisions, wall thickness, connectivity, floating bodies, sections, masks, depth, normals, or Zebra stripes.
+Select, run, and interpret ForgeCAD inspection evidence for collisions, sections, wall thickness, components, masks, depth, normals, surface continuity, and fit.
 
 | Field | Value |
 | --- | --- |
 | Installed by | `forgecad skill install` |
-| Source | `agent-skill-library/forgecad-render-inspect/SKILL.md` |
+| Source | `agent-skill-library/forgecad-inspect-model/SKILL.md` |
 
 ---
 
-## ForgeCAD Render Inspect
+## Inspect Model
 
 Use `forgecad inspect ...` when a shaded render is too ambiguous and you need structured evidence: a bundle directory with evidence PNGs plus a root `manifest.json` (or, for `inspect section`, a probe directory with `result.json`, `section.svg`, `section.png`). Inspection is not a substitute artifact: look inside with sections, masks, `--focus`/`--hide`, and transparency — never edit the model into a cutaway or exploded default to make inspecting easier. Output dirs: let `inspect` allocate its timestamped directory by default (repeated probes never collide); use `/tmp/<model>-inspect` for throwaway bundles, a project directory only for persistent artifacts.
 
-Routing: authoring/API questions → `forgecad` skill; creating a new model → `forgecad-make-a-model`.
+Routing: authoring/API questions → `forgecad` skill; creating a new model → `forgecad-build-model`.
 
 ### Workflow
 

package/{dist/docs-raw/skills/forgecad-project.md → dist-skill/website/skills/forgecad-project-sync.md}

@@ -1,17 +1,17 @@
-<!-- Generated by scripts/build-forgecad-skill.mjs — do not edit. Edit agent-skill-library/forgecad-project/SKILL.md instead. -->
+<!-- Generated by scripts/build-forgecad-skill.mjs — do not edit. Edit agent-skill-library/forgecad-project-sync/SKILL.md instead. -->
 
-# forgecad-project
+# forgecad-project-sync
 
-ForgeCAD project CLI workflow — creating, managing, syncing projects and files on forgecad.io. Covers init, push, pull, file operations, member management, publishing, and sharing.
+Manage hosted ForgeCAD project sync from the CLI: init, clone, pull, push, file operations, members, publishing, and shares.
 
 | Field | Value |
 | --- | --- |
 | Installed by | `forgecad skill install` |
-| Source | `agent-skill-library/forgecad-project/SKILL.md` |
+| Source | `agent-skill-library/forgecad-project-sync/SKILL.md` |
 
 ---
 
-## ForgeCAD Project Operating Rules
+## Project Sync
 
 forgecad.io is the hosted ForgeCAD platform; a project is a local folder linked to the server by `forgecad.json`. The full command inventory (project, file, member, share, token commands and flags) lives in `forgecad project --help` and the forgecad skill's `docs/CLI.md` — do not relearn it here.
 

package/dist-skill/website/skills/{forgecad-3d-reconstruction.md → forgecad-reconstruct-cad-file.md}

@@ -1,21 +1,21 @@
-<!-- Generated by scripts/build-forgecad-skill.mjs — do not edit. Edit agent-skill-library/forgecad-3d-reconstruction/SKILL.md instead. -->
+<!-- Generated by scripts/build-forgecad-skill.mjs — do not edit. Edit agent-skill-library/forgecad-reconstruct-cad-file/SKILL.md instead. -->
 
-# forgecad-3d-reconstruction
+# forgecad-reconstruct-cad-file
 
-Reconstruct a parametric ForgeCAD model from an existing 3D CAD or mesh file such as STL, OBJ, 3MF, STEP, or STP; inspect the source asset directly, author real ForgeCAD geometry, and iteratively compare the candidate with `forgecad compare 3d`.
+Reconstruct a readable parametric ForgeCAD model from an existing CAD or mesh file such as STL, OBJ, 3MF, STEP, or STP.
 
 | Field | Value |
 | --- | --- |
 | Installed by | `forgecad skill install` |
-| Source | `agent-skill-library/forgecad-3d-reconstruction/SKILL.md` |
+| Source | `agent-skill-library/forgecad-reconstruct-cad-file/SKILL.md` |
 
 ---
 
-## ForgeCAD 3D Reconstruction
+## Reconstruct CAD File
 
 The reference asset is evidence, not the deliverable. The deliverable is a readable, parametric `.forge.js` model that runs, renders, and scores well against the source. Never return `Import.mesh()`/`Import.step()` of the source as the final model unless the user explicitly asks for an import wrapper — imports are for measurement, rendering, and scoring only.
 
-Routing: user wants to KEEP the file as a live component and design around it (bracket, enclosure, mating assembly) → `forgecad-make-a-model` (Imported Parts section), not this skill; benchmark/RL episodes → `forgecad-reconstruction-benchmark`; inspection-bundle interpretation → `forgecad-render-inspect`; independent grading after reconstruction → `forgecad-model-grader`; API and command reference → `forgecad` skill + CLI.md.
+Routing: user wants to KEEP the file as a live component and design around it (bracket, enclosure, mating assembly) → `forgecad-build-model` (Imported Parts section), not this skill; prepared benchmark/RL episodes → use the task-local benchmark instructions, not the public skill library; inspection-bundle interpretation → `forgecad-inspect-model`; independent grading after reconstruction → `forgecad-grade-model`; API and command reference → `forgecad` skill + CLI.md.
 
 ### Workflow
 
@@ -50,7 +50,7 @@ Faceted sources: decide whether tessellation itself is evidence. Matching low-po
 
 ### Done Criteria
 
-The final model must run, render, re-compare at `--samples 5000`, and pass an `inspect compare overlay`. Add targeted inspects (`forgecad-render-inspect`) when the object is multi-part, hollow, thin-walled, or surface-sensitive. Report: source and candidate paths, score JSON path, final metrics, and every known mismatch classified as intentional simplification or remaining work.
+The final model must run, render, re-compare at `--samples 5000`, and pass an `inspect compare overlay`. Add targeted inspects (`forgecad-inspect-model`) when the object is multi-part, hollow, thin-walled, or surface-sensitive. Report: source and candidate paths, score JSON path, final metrics, and every known mismatch classified as intentional simplification or remaining work.
 
 
 ## Bundled Files

package/dist-skill/website/skills/{forgecad-image-replicator.md → forgecad-reconstruct-from-images.md}

@@ -1,26 +1,26 @@
-<!-- Generated by scripts/build-forgecad-skill.mjs — do not edit. Edit agent-skill-library/forgecad-image-replicator/SKILL.md instead. -->
+<!-- Generated by scripts/build-forgecad-skill.mjs — do not edit. Edit agent-skill-library/forgecad-reconstruct-from-images/SKILL.md instead. -->
 
-# forgecad-image-replicator
+# forgecad-reconstruct-from-images
 
-Build real ForgeCAD geometry from one or more reference images by treating images as evidence, inferring the object, then validating against both reference-matched and canonical views.
+Reconstruct a real parametric ForgeCAD object from reference images by using images as evidence, not as a one-view facade.
 
 | Field | Value |
 | --- | --- |
 | Installed by | `forgecad skill install` |
-| Source | `agent-skill-library/forgecad-image-replicator/SKILL.md` |
+| Source | `agent-skill-library/forgecad-reconstruct-from-images/SKILL.md` |
 
 ---
 
-## ForgeCAD Image Replicator
+## Reconstruct From Images
 
 The reference image is evidence, not the deliverable. The deliverable is a real parametric object that holds up from front, back, side, top, bottom, and reference camera views — a model that matches one image but falls apart from other angles has failed, even if the comparison board looks close. Cutaway, sectioned, exploded, or transparent references are evidence about the complete object: build the closed artifact and recreate explanatory views with viewer/inspection tools (the main `forgecad` skill's closed-artifact rule applies).
 
 ### Companion Skills
 
 - `forgecad` — API docs, model authoring, renderer behavior.
-- `forgecad-spec-by-walking-through-it` — when the images underdetermine artifact family, process posture, scale, operating story, or validation boundary.
-- `forgecad-make-a-model` — file placement, project structure, decomposition, definition of done.
-- `forgecad-render-inspect` — pre-delivery inspection for multi-part, internal, mechanical, thin-wall, or fit-sensitive objects.
+- `forgecad-design-spec` — when the images underdetermine artifact family, process posture, scale, operating story, or validation boundary.
+- `forgecad-build-model` — file placement, project structure, decomposition, definition of done.
+- `forgecad-inspect-model` — pre-delivery inspection for multi-part, internal, mechanical, thin-wall, or fit-sensitive objects.
 
 ### Core Rule
 
@@ -30,19 +30,19 @@ Infer the real object before matching any camera — identity, manufacture, scal
 
 1. Stage references in `/tmp/<slug>-replicate/refs`, keeping originals and adding view names where possible (`front`, `side`, `rear-iso`, `top`, `detail`).
 2. Read each image as evidence, recording: visible facts; scale cues; camera cues; unknowns (hidden/occluded geometry); conflicts across images or stylization.
-3. Write a Real Object Brief — a hard gate before modeling: (a) artifact identity + operating story; (b) assumed scale and units; (c) process posture + part/BOM boundary (real geometry vs purchased vs ghost vs omitted); (d) inferred hidden-side geometry + expected canonical front/back/left/right/top/bottom forms; (e) validation views and inspection evidence. Use `forgecad-spec-by-walking-through-it` when these are underdetermined.
-4. Build a coarse 3D blockout — model the object, not the image: large volumes, axes, symmetry, side depth, rear form, underside, hidden continuations. Render canonical views before any reference-camera comparison. Follow `forgecad-make-a-model` for project structure.
+3. Write a Real Object Brief — a hard gate before modeling: (a) artifact identity + operating story; (b) assumed scale and units; (c) process posture + part/BOM boundary (real geometry vs purchased vs ghost vs omitted); (d) inferred hidden-side geometry + expected canonical front/back/left/right/top/bottom forms; (e) validation views and inspection evidence. Use `forgecad-design-spec` when these are underdetermined.
+4. Build a coarse 3D blockout — model the object, not the image: large volumes, axes, symmetry, side depth, rear form, underside, hidden continuations. Render canonical views before any reference-camera comparison. Follow `forgecad-build-model` for project structure.
 5. Calibrate one camera per usable reference, only after the blockout makes sense from canonical views. Use the object center as `target`; estimate azimuth/elevation/distance/FOV from visible faces and perspective cues; use orthographic when parallel edges stay parallel with no perspective convergence.
 6. Render comparison boards: render the model from each calibrated reference camera and place it next to the original. Never compare from memory.
 7. Iterate one class of change at a time, in order: object hypothesis → major proportions → canonical geometry → camera → details → presentation. If improving one reference view makes another view or a canonical render worse, the object hypothesis is wrong — fix the model, not the camera illusion.
 8. Use every image as a constraint. Never pick one target image and ignore the rest: assign each image a camera, evidence list, and confidence; optimize one shared geometry against the whole set; state how distorted or decorative images were weighted.
-9. Validate the final object: `forgecad run`, reference comparison boards, canonical renders, and targeted inspections via `forgecad-render-inspect`.
+9. Validate the final object: `forgecad run`, reference comparison boards, canonical renders, and targeted inspections via `forgecad-inspect-model`.
 
 ### Comparison Boards
 
 Render with exact `--camera` specs (see the forgecad CLI doc for supported forms). If exact full camera specs do not render, fix the renderer before continuing — never substitute guesses from default `iso` renders.
 
-Build side-by-side boards with the bundled self-contained `uv` helper (installs Pillow on demand). Resolve `scripts/compare_images.py` relative to the installed `forgecad-image-replicator` skill directory:
+Build side-by-side boards with the bundled self-contained `uv` helper (installs Pillow on demand). Resolve `scripts/compare_images.py` relative to the installed `forgecad-reconstruct-from-images` skill directory:
 
 ```bash
 uv run <skill-dir>/scripts/compare_images.py refs/front.png render-front.png compare-front.png

package/dist-skill/website/skills/{forgecad-mujoco-verify.md → forgecad-verify-mujoco.md}

@@ -1,21 +1,21 @@
-<!-- Generated by scripts/build-forgecad-skill.mjs — do not edit. Edit agent-skill-library/forgecad-mujoco-verify/SKILL.md instead. -->
+<!-- Generated by scripts/build-forgecad-skill.mjs — do not edit. Edit agent-skill-library/forgecad-verify-mujoco/SKILL.md instead. -->
 
-# forgecad-mujoco-verify
+# forgecad-verify-mujoco
 
-Verify ForgeCAD MJCF exports in MuJoCo with real dynamics, contacts, root behavior, controls, required joint travel, and rendered evidence before calling a model simulation-ready. Use when making a ForgeCAD assembly sim-ready, debugging MJCF contacts, checking why a body falls through the floor, validating actuator motion, or proving a mechanism moved through the intended range.
+Verify a ForgeCAD MJCF export in MuJoCo with dynamics, contacts, controls, joint travel, and rendered evidence before calling it simulation-ready.
 
 | Field | Value |
 | --- | --- |
 | Installed by | `forgecad skill install` |
-| Source | `agent-skill-library/forgecad-mujoco-verify/SKILL.md` |
+| Source | `agent-skill-library/forgecad-verify-mujoco/SKILL.md` |
 
 ---
 
-## ForgeCAD MuJoCo Verify
+## Verify MuJoCo
 
 Use this when `forgecad export mjcf ...` is part of the deliverable. A model is not sim-ready just because `forgecad check simready` passes or the MJCF file loads: it must be loaded in MuJoCo, stepped under gravity, driven with the intended controls, contact pairs inspected, and rendered from useful views.
 
-Routing: geometry-only visual inspection -> `forgecad-render-inspect`; model authoring/API questions -> `forgecad`; building a new model -> `forgecad-make-a-model`.
+Routing: geometry-only visual inspection -> `forgecad-inspect-model`; model authoring/API questions -> `forgecad`; building a new model -> `forgecad-build-model`.
 
 ### Definition Of Done
 

package/dist-skill/website/skills/index.md

@@ -11,15 +11,12 @@ forgecad skill install
 | Skill | Installed by | Purpose |
 | --- | --- | --- |
 | [forgecad](/docs/skills/forgecad) | `forgecad skill install` | ForgeCAD model authoring, editing, debugging, and execution guidance for .forge.js, SVG-import, assembly, and CLI workflows. Use when building or modifying ForgeCAD geometry, structuring multi-file projects, validating scripts, or using ForgeCAD export/render tooling. |
-| [forgecad-3d-reconstruction](/docs/skills/forgecad-3d-reconstruction) | `forgecad skill install` | Reconstruct a parametric ForgeCAD model from an existing 3D CAD or mesh file such as STL, OBJ, 3MF, STEP, or STP; inspect the source asset directly, author real ForgeCAD geometry, and iteratively compare the candidate with `forgecad compare 3d`. |
-| [forgecad-blockout-model](/docs/skills/forgecad-blockout-model) | `forgecad skill install` | Create rough high-level ForgeCAD concept models from simple primitives to explore layout, proportions, motion, and part relationships without production detail. Use when asked for a quick model sketch, blockout, spatial mockup, or intuitive low-detail 3D concept. |
-| [forgecad-component-model](/docs/skills/forgecad-component-model) | `forgecad skill install` | Enforce the ForgeCAD Component Model when building multi-part assemblies. Parts build at origin, connectors position them, data flows down from parent. Use when building or reviewing any multi-file ForgeCAD project. |
-| [forgecad-image-replicator](/docs/skills/forgecad-image-replicator) | `forgecad skill install` | Build real ForgeCAD geometry from one or more reference images by treating images as evidence, inferring the object, then validating against both reference-matched and canonical views. |
-| [forgecad-make-a-model](/docs/skills/forgecad-make-a-model) | `forgecad skill install` | Create manufacture-realistic prototype ForgeCAD (.forge.js) models in the active CAD project. Handles file placement, invokes the forgecad skill for API guidance, and validates the result. |
-| [forgecad-model-grader](/docs/skills/forgecad-model-grader) | `forgecad skill install` | Analyze, verify, and grade ForgeCAD or CAD-as-code models against a user requirement, design brief, prompt, reference, or acceptance criteria. Use when asked to evaluate, judge, QA, benchmark, score, rate, or compare a CAD model; render it from multiple angles, run targeted inspections when needed, visually verify the evidence, and produce a 0-10 score with concise justification. |
-| [forgecad-mujoco-verify](/docs/skills/forgecad-mujoco-verify) | `forgecad skill install` | Verify ForgeCAD MJCF exports in MuJoCo with real dynamics, contacts, root behavior, controls, required joint travel, and rendered evidence before calling a model simulation-ready. Use when making a ForgeCAD assembly sim-ready, debugging MJCF contacts, checking why a body falls through the floor, validating actuator motion, or proving a mechanism moved through the intended range. |
-| [forgecad-project](/docs/skills/forgecad-project) | `forgecad skill install` | ForgeCAD project CLI workflow — creating, managing, syncing projects and files on forgecad.io. Covers init, push, pull, file operations, member management, publishing, and sharing. |
-| [forgecad-reconstruction-benchmark](/docs/skills/forgecad-reconstruction-benchmark) | `forgecad skill install` | Solve ForgeCAD CAD reconstruction benchmark or RL episodes in a prepared workspace by rebuilding a visible reference asset as readable parametric ForgeCAD in the fixed submission path, using visual and geometric self-checks while respecting sandbox limits. |
-| [forgecad-render-inspect](/docs/skills/forgecad-render-inspect) | `forgecad skill install` | Run and interpret ForgeCAD inspection bundles for model verification. Use when asked to inspect a ForgeCAD model, analyze an inspection bundle, validate collisions, wall thickness, connectivity, floating bodies, sections, masks, depth, normals, or Zebra stripes. |
-| [forgecad-spec-by-walking-through-it](/docs/skills/forgecad-spec-by-walking-through-it) | `forgecad skill install` | Design a ForgeCAD model, mechanism, or assembly by fixing WHAT before HOW in a git-reviewed design document, validated by mentally operating the thing step by step. Covers fuzzy-request intake and process choice, high-level design (HLD), and low-level design (LLD). Use on "spec this out", "plan the design", "write the HLD/LLD", a vague build request that needs concrete decisions, or any moment the right move is a reviewable spec before code. |
-| [forgecad-visual-spec](/docs/skills/forgecad-visual-spec) | `forgecad skill install` | Turn a concrete ForgeCAD artifact, build brief, HLD, or existing model into builder-honest image prompts for AI image models. Use when the user wants visual-spec renders that show the final product while keeping mechanisms, seams, hardware, and build cues visible instead of drifting into concept art. |
+| [forgecad-build-model](/docs/skills/forgecad-build-model) | `forgecad skill install` | Build or edit a manufacture-realistic `.forge.js` model in a project, then validate it with run, render, inspect, and export evidence. |
+| [forgecad-design-spec](/docs/skills/forgecad-design-spec) | `forgecad skill install` | Create a ForgeCAD design brief, HLD, or LLD before coding by walking through use, assembly, interfaces, decisions, and verification. |
+| [forgecad-grade-model](/docs/skills/forgecad-grade-model) | `forgecad skill install` | Grade a ForgeCAD or CAD-as-code model against a requirement, brief, prompt, reference, or acceptance criteria with evidence and a 0-10 score. |
+| [forgecad-image-prompt](/docs/skills/forgecad-image-prompt) | `forgecad skill install` | Write builder-honest AI image prompts from a concrete ForgeCAD model, build brief, HLD, or LLD without hiding how the artifact is built. |
+| [forgecad-inspect-model](/docs/skills/forgecad-inspect-model) | `forgecad skill install` | Select, run, and interpret ForgeCAD inspection evidence for collisions, sections, wall thickness, components, masks, depth, normals, surface continuity, and fit. |
+| [forgecad-project-sync](/docs/skills/forgecad-project-sync) | `forgecad skill install` | Manage hosted ForgeCAD project sync from the CLI: init, clone, pull, push, file operations, members, publishing, and shares. |
+| [forgecad-reconstruct-cad-file](/docs/skills/forgecad-reconstruct-cad-file) | `forgecad skill install` | Reconstruct a readable parametric ForgeCAD model from an existing CAD or mesh file such as STL, OBJ, 3MF, STEP, or STP. |
+| [forgecad-reconstruct-from-images](/docs/skills/forgecad-reconstruct-from-images) | `forgecad skill install` | Reconstruct a real parametric ForgeCAD object from reference images by using images as evidence, not as a one-view facade. |
+| [forgecad-verify-mujoco](/docs/skills/forgecad-verify-mujoco) | `forgecad skill install` | Verify a ForgeCAD MJCF export in MuJoCo with dynamics, contacts, controls, joint travel, and rendered evidence before calling it simulation-ready. |

package/examples/api/texture-projection.forge.js

@@ -0,0 +1,75 @@
+// Bitmap Texturing: Projected UV
+//
+// Wrap an imported bitmap onto a surface with `Shape.wrapTexture(image,
+// projection)`. The projection (a `Wrap.*` helper) decides how each point of the
+// surface maps into the image — no UV unwrapping, no Math.sin/cos.
+//
+// The image's colored edges (top=red, right=green, bottom=blue, left=orange) and
+// the dark top-left corner wedge make the mapping orientation easy to read on
+// every shape.
+//
+// Two key properties:
+//   1. AUTO-FIT — a bare `Wrap.flat/box/aroundCylinder` (no width/height/size)
+//      maps ONE copy of the image across the shape's extent. No magic numbers:
+//      the fit is read from the shape's bounding box.
+//   2. WORLD-SPACE & BOOLEAN-SAFE — the UV is derived from each vertex's final
+//      world position at render time, so the texture survives cuts/unions AND so
+//      you must texture a shape *after* positioning it (auto-fit reads the final
+//      world box; see the rightmost part, textured *then* bored).
+
+const tile = Param.number("Tile repeat", 1, { min: 1, max: 6, step: 1 });
+
+const art = Import.image("assets/uv-grid.png");
+
+// Laid out left-to-right in a tidy row on the z = 0 ground plane, ~25 mm gaps so
+// nothing overlaps. box() and sphere() are origin-centered (lift them by half
+// their height to sit on the ground); cylinder(height, radius) already has its
+// base at z = 0, so the can needs no z lift.
+//
+// In every case: build → translate → wrapTexture LAST, so auto-fit reads the
+// final world bounding box.
+
+// 1. FLAT — lay the image onto one axis-aligned face (a logo on a plate's top).
+//    No width/height: auto-fit maps the face span to the image once. `repeat`
+//    tiles that single fitted copy.
+const plate = box(50, 50, 8)
+  .translate(-140, 0, 4)
+  .wrapTexture(art, Wrap.flat({ onto: "top", repeat: [tile, tile] }));
+
+// 2. AROUND A CYLINDER — wrap the image like a can label. `axis` is the cylinder
+//    axis; the seam falls on the -X side (the atan2 wrap at ±π). No height:
+//    auto-fit maps the can's full height to the image once.
+const can = cylinder(55, 20)
+  .translate(-70, 0, 0)
+  .wrapTexture(art, Wrap.aroundCylinder({ axis: "z" }));
+
+// 3. ONTO A SPHERE — longitude/latitude mapping, like a globe. Auto-fit centers
+//    the projection on the sphere wherever it sits.
+const globe = sphere(26)
+  .translate(0, 0, 26)
+  .wrapTexture(art, Wrap.onSphere());
+
+// 4. BOX (cube-map) — the dominant face axis picks one of three planar maps, so
+//    each of the six sides shows one copy of the image. No size: auto-fit reads
+//    the box extent.
+const crate = box(40, 40, 40)
+  .translate(70, 0, 20)
+  .wrapTexture(art, Wrap.box());
+
+// 5. BOOLEAN-SAFE — position the plate, texture it (auto-fit over the solid
+//    plate), THEN subtract a bore. The image keeps flowing across the top and
+//    around the freshly-cut hole because the UV is re-derived from world position
+//    every frame, not baked into the original mesh. (Texture-then-cut, no
+//    translate after — the world-space UV must be locked before the boolean.)
+const bored = box(50, 50, 16)
+  .translate(140, 0, 8)
+  .wrapTexture(art, Wrap.flat({ onto: "top", repeat: [tile, tile] }))
+  .subtract(cylinder(40, 12).translate(140, 0, -12)); // through-hole, centered on the plate
+
+return [
+  { name: "Flat (plate top)", shape: plate },
+  { name: "Cylinder (label)", shape: can },
+  { name: "Sphere (globe)", shape: globe },
+  { name: "Box (cube-map)", shape: crate },
+  { name: "Boolean-safe (bored)", shape: bored },
+];

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "forgecad",
-  "version": "0.10.3",
+  "version": "0.10.4",
   "description": "Code-first parametric CAD for JavaScript/TypeScript, in the browser and CLI.",
   "license": "SEE LICENSE IN LICENSE",
   "homepage": "https://forgecad.io",

package/dist/docs-raw/skills/forgecad-blockout-model.md

@@ -1,49 +0,0 @@
-<!-- Generated by scripts/build-forgecad-skill.mjs — do not edit. Edit agent-skill-library/forgecad-blockout-model/SKILL.md instead. -->
-
-# forgecad-blockout-model
-
-Create rough high-level ForgeCAD concept models from simple primitives to explore layout, proportions, motion, and part relationships without production detail. Use when asked for a quick model sketch, blockout, spatial mockup, or intuitive low-detail 3D concept.
-
-| Field | Value |
-| --- | --- |
-| Installed by | `forgecad skill install` |
-| Source | `agent-skill-library/forgecad-blockout-model/SKILL.md` |
-
----
-
-## Block Out a Model
-
-A blockout is a spatial planning artifact: 3-7 simple masses that answer where parts go, whether a mechanism makes spatial sense, and what the silhouette, footprint, or motion envelope looks like. Not for print-ready geometry, exact fit, tolerances, or detail work.
-
-| Need | Skill |
-|------|-------|
-| High-level 3D idea using simple masses | `forgecad-blockout-model` |
-| Written concept or architecture before CAD | `forgecad-spec-by-walking-through-it` |
-| Accurate, detailed, parametric ForgeCAD model | `forgecad-make-a-model` |
-
-### Method
-
-- Load the `forgecad` skill first; read its Core API and CLI docs. Load nothing else unless the concept demands it.
-- Translate the idea into 3-7 conceptual parts BEFORE writing geometry: masses and zones (base, arm, payload, sweep volume, keep-out, hand access).
-- One primitive stands in for many eventual details. A bounding box beats a fake detailed part. Never add detail as a substitute for clarity — simplify or reposition instead.
-- Use round-number dimensions; "believably shaped" beats numerically correct. Name uncertainty honestly: `armLengthGuess`, `baseWidthApprox`, `clearanceEnvelope`.
-- At most a handful of `param()` values, for comparing proportions. Do not parameterize every dimension.
-- Color by meaning; keep each conceptual part visually distinct via color or opacity. Return named shape objects so the viewer can inspect the concept part-by-part.
-- Ghost geometry: transparent volumes only for REAL physical envelopes — sweep arcs, keep-out volumes, approximate payloads, reach/access zones. Never decorative teaching overlays. Exaggerate tiny clearances when needed for readability.
-- Even a blockout represents the object in its normal assembled state: no labels, legends, cutaways, or permanently exploded layouts (full rule in the `forgecad` skill).
-- Leave out: fasteners and screw holes, wall thicknesses, fillets and blend radii, polished materials, hidden internal structure that does not affect the concept.
-
-### Verify
-
-Rendering is mandatory even for rough models. Run the script, then render from 2-3 angles with the installed `forgecad` CLI (syntax: the `forgecad` skill's CLI docs). Judge by the reader test:
-
-- Can someone unfamiliar with the idea tell what each mass represents?
-- Are proportions believable enough to discuss?
-- Is motion or interference visible where it matters?
-- Are unknowns shown honestly, not hidden behind fake detail?
-
-If any answer is no, simplify or add clearer ghost volumes.
-
-### Handoff
-
-File placement and naming follow `forgecad-make-a-model` conventions; suffix the filename `-blockout` or `-concept` unless the user supplied a clearer name. Once the high-level questions are answered, stop. If the next question is real fit, tunable dimensions, part details, or manufacturing logic, switch to `forgecad-make-a-model` instead of refining the blockout indefinitely.

package/dist/docs-raw/skills/forgecad-component-model.md

@@ -1,53 +0,0 @@
-<!-- Generated by scripts/build-forgecad-skill.mjs — do not edit. Edit agent-skill-library/forgecad-component-model/SKILL.md instead. -->
-
-# forgecad-component-model
-
-Enforce the ForgeCAD Component Model when building multi-part assemblies. Parts build at origin, connectors position them, data flows down from parent. Use when building or reviewing any multi-file ForgeCAD project.
-
-| Field | Value |
-| --- | --- |
-| Installed by | `forgecad skill install` |
-| Source | `agent-skill-library/forgecad-component-model/SKILL.md` |
-
----
-
-## Component Model
-
-The React of CAD: a part is a function from props to `{ shape, connectors, metadata }`, built at origin in local space. Parts never position themselves — the assembly positions them via connectors.
-
-### Rules
-
-1. **Parts build at origin.** Geometry starts at `[0,0,0]` in local coordinates; no assembly-space offsets; internal structure derives from the part's own props only.
-2. **Connectors are the only interface.** Declare via `.withConnectors({})`; axes point outward, mating is face-to-face (exception: prismatic joints share a co-directional slide axis). Mechanics: the forgecad skill's `docs/guides/positioning.md` and `docs/generated/assembly.md`.
-3. **Assembly is pure composition.** Zero `translate()` to position structural parts, zero coordinate math — connect connectors, pass props down, read metadata up.
-4. **Data flows down, never sideways.** Props down via `require('./part.forge.js', { Height: 20 })` overrides; metadata up via the part's return object; siblings NEVER import each other — the assembly mediates all sibling communication.
-5. **Validate with `verify.*`, never `console.log` + `if`.**
-
-### Part return shape
-
-```js
-return { shape, boltPattern, pinionZ }; // shape + metadata the parent may route to siblings
-```
-
-### File structure
-
-Default: ONE file per project-specific assembly — parts as sections, shared data as variables. Split only for cross-project reuse or past ~300 lines. Never split for "organization".
-
-### Anti-patterns (reject on review)
-
-- `shared-dims.js` — a file that only computes derived dimensions; the assembly derives and passes them.
-- Sibling `require()` — e.g. `require('./motor-mount.forge.js')` inside `cover-plate.forge.js`; route through the parent.
-- Assembly-space coordinates inside a part — a part knowing `pinionZ = 14` from a sibling's geometry; receive it as a prop.
-- `translate()` to position a structural part in an assembly — add a connector instead.
-- `console.log` + `if` validation — use `verify.*`.
-- Bare `connector.neutral()` outside a reusable component library with compatibility checking.
-
-### Design gate
-
-Before committing any multi-part assembly:
-
-1. Can you understand each part without reading other files?
-2. Does the assembly contain zero coordinate math?
-3. Do all inter-part relationships flow through connectors and props?
-
-If any answer is no, refactor.

package/dist/docs-raw/skills/forgecad-reconstruction-benchmark.md

@@ -1,60 +0,0 @@
-<!-- Generated by scripts/build-forgecad-skill.mjs — do not edit. Edit agent-skill-library/forgecad-reconstruction-benchmark/SKILL.md instead. -->
-
-# forgecad-reconstruction-benchmark
-
-Solve ForgeCAD CAD reconstruction benchmark or RL episodes in a prepared workspace by rebuilding a visible reference asset as readable parametric ForgeCAD in the fixed submission path, using visual and geometric self-checks while respecting sandbox limits.
-
-| Field | Value |
-| --- | --- |
-| Installed by | `forgecad skill install` |
-| Source | `agent-skill-library/forgecad-reconstruction-benchmark/SKILL.md` |
-
----
-
-## ForgeCAD Reconstruction Benchmark
-
-Benchmark adaptation of `forgecad-3d-reconstruction`: same reconstruction loop, but with a fixed submission path, a local CLI wrapper, sandbox limits, and a short wall-clock budget. This sheet owns only those deltas — follow `forgecad-3d-reconstruction` for the reconstruction craft.
-
-### Workspace
-
-Read first: `AGENTS.md`, `task/instructions.md`, this skill, and `agent-home/.agents/skills/forgecad/SKILL.md` (API + CLI reference).
-
-- Reference asset (evidence only): `task/reference/*`
-- Final answer: `submission/main.forge.js`, unless `task/task.json` overrides
-- CLI: the local wrapper `./bin/forgecad`, never global commands
-- Scratch renders/notes: `outputs/`
-- Stay inside the prepared workspace.
-
-```bash
-./bin/forgecad run submission/main.forge.js
-```
-
-### Rules and Done Criteria
-
-- Deliverable is readable parametric ForgeCAD source at the required submission path. A clean parametric approximation beats an unreadable mesh mimic.
-- The final source must not call `Import.mesh`, `Import.step`, `importMesh`, `importStep`, `readFile`, `readFileSync`, or any equivalent asset-embedding trick, and must contain no `compareWith(...)`, external reference paths, base64 payloads, or debug probes.
-- Sandbox: allowed local tools only — no web search, no broad home-directory access, no subagents, no remote services.
-- Before exit: the run command above succeeds; visual/section evidence checked after the last meaningful edit; model recognizable against the reference from the main views.
-
-### Budget Discipline
-
-A runnable first candidate beats a perfect investigation with no model.
-
-1. Run the starter submission once before editing so syntax/runtime problems surface early.
-2. Inspect only the highest-value reference evidence: dimensions, volume, object count, one visual or sectional view. If a reference render/inspect command fails or stalls, continue from task instructions, filename, starter code, and mechanical inference — do not burn the budget retrying.
-3. Write a short reconstruction brief in `outputs/brief.md` (fields per `forgecad-3d-reconstruction`).
-4. Edit the submission early: coarse bbox, orientation, and main masses first, then iterate coarse-to-fine per `forgecad-3d-reconstruction`.
-5. 3MF references: the `forgecad run` source-structure table is evidence — account for every substantial 3MF item in the reconstruction (the final model may be one part or many).
-6. `inspect section` probes are replayable against the candidate via `inspect replay` — the cheap way to verify an exact local measurement transfers. Mechanics: `forgecad-render-inspect`.
-
-### Pointers
-
-- `forgecad-3d-reconstruction` — the evidence → brief → coarse → fine loop and metric diagnosis
-- `forgecad-render-inspect` — inspection bundles, section probes, replay
-- forgecad skill at `agent-home/.agents/skills/forgecad/` — API and CLI syntax
-- `forgecad-make-a-model` — general quality patterns only; its date-based file-placement workflow does not apply in benchmark workspaces
-
-
-## Bundled Files
-
-- `agents/openai.yaml`

package/dist-skill/library/forgecad-3d-reconstruction/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "ForgeCAD 3D Reconstruction"
-  short_description: "Rebuild CAD files as ForgeCAD models"
-  default_prompt: "Use $forgecad-3d-reconstruction to inspect this 3D file, rebuild it as parametric ForgeCAD, and score the result against the source."

package/dist-skill/library/forgecad-blockout-model/SKILL.md

@@ -1,42 +0,0 @@
----
-name: forgecad-blockout-model
-description: Create rough high-level ForgeCAD concept models from simple primitives to explore layout, proportions, motion, and part relationships without production detail. Use when asked for a quick model sketch, blockout, spatial mockup, or intuitive low-detail 3D concept.
-forgecad-public: true
----
-
-# Block Out a Model
-
-A blockout is a spatial planning artifact: 3-7 simple masses that answer where parts go, whether a mechanism makes spatial sense, and what the silhouette, footprint, or motion envelope looks like. Not for print-ready geometry, exact fit, tolerances, or detail work.
-
-| Need | Skill |
-|------|-------|
-| High-level 3D idea using simple masses | `forgecad-blockout-model` |
-| Written concept or architecture before CAD | `forgecad-spec-by-walking-through-it` |
-| Accurate, detailed, parametric ForgeCAD model | `forgecad-make-a-model` |
-
-## Method
-
-- Load the `forgecad` skill first; read its Core API and CLI docs. Load nothing else unless the concept demands it.
-- Translate the idea into 3-7 conceptual parts BEFORE writing geometry: masses and zones (base, arm, payload, sweep volume, keep-out, hand access).
-- One primitive stands in for many eventual details. A bounding box beats a fake detailed part. Never add detail as a substitute for clarity — simplify or reposition instead.
-- Use round-number dimensions; "believably shaped" beats numerically correct. Name uncertainty honestly: `armLengthGuess`, `baseWidthApprox`, `clearanceEnvelope`.
-- At most a handful of `param()` values, for comparing proportions. Do not parameterize every dimension.
-- Color by meaning; keep each conceptual part visually distinct via color or opacity. Return named shape objects so the viewer can inspect the concept part-by-part.
-- Ghost geometry: transparent volumes only for REAL physical envelopes — sweep arcs, keep-out volumes, approximate payloads, reach/access zones. Never decorative teaching overlays. Exaggerate tiny clearances when needed for readability.
-- Even a blockout represents the object in its normal assembled state: no labels, legends, cutaways, or permanently exploded layouts (full rule in the `forgecad` skill).
-- Leave out: fasteners and screw holes, wall thicknesses, fillets and blend radii, polished materials, hidden internal structure that does not affect the concept.
-
-## Verify
-
-Rendering is mandatory even for rough models. Run the script, then render from 2-3 angles with the installed `forgecad` CLI (syntax: the `forgecad` skill's CLI docs). Judge by the reader test:
-
-- Can someone unfamiliar with the idea tell what each mass represents?
-- Are proportions believable enough to discuss?
-- Is motion or interference visible where it matters?
-- Are unknowns shown honestly, not hidden behind fake detail?
-
-If any answer is no, simplify or add clearer ghost volumes.
-
-## Handoff
-
-File placement and naming follow `forgecad-make-a-model` conventions; suffix the filename `-blockout` or `-concept` unless the user supplied a clearer name. Once the high-level questions are answered, stop. If the next question is real fit, tunable dimensions, part details, or manufacturing logic, switch to `forgecad-make-a-model` instead of refining the blockout indefinitely.