forgecad 0.10.3 → 0.10.5

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

@@ -1,46 +0,0 @@
----
-name: forgecad-component-model
-description: "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-public: true
----
-
-# 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-skill/library/forgecad-image-replicator/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "ForgeCAD Image Replicator"
-  short_description: "Build real CAD objects from images"
-  default_prompt: "Use $forgecad-image-replicator to infer the real object from these reference images and build a ForgeCAD model that holds up from all views."

package/dist-skill/library/forgecad-model-grader/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "ForgeCAD Model Grader"
-  short_description: "Grade CAD models against a brief"
-  default_prompt: "Use $forgecad-model-grader to evaluate this ForgeCAD model against the requirement and give a 0-10 score with evidence."

package/dist-skill/library/forgecad-reconstruction-benchmark/SKILL.md

@@ -1,48 +0,0 @@
----
-name: forgecad-reconstruction-benchmark
-description: 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-public: true
----
-
-# 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

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

@@ -1,4 +0,0 @@
-interface:
-  display_name: "ForgeCAD Reconstruction Benchmark"
-  short_description: "Solve fixed-path CAD reconstruction tasks"
-  default_prompt: "Use $forgecad-reconstruction-benchmark to rebuild the reference CAD asset as readable parametric ForgeCAD in the required benchmark submission path."

package/dist-skill/library/forgecad-visual-spec/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "ForgeCAD Visual Spec"
-  short_description: "Builder-honest image prompt packs"
-  default_prompt: "Use $forgecad-visual-spec to turn this ForgeCAD artifact into image prompts that show the final product without hiding how it is built."

package/dist-skill/website/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-skill/website/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-skill/website/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`