forgecad 0.9.14 → 0.9.16

package/dist/docs-raw/legal/privacy.md

@@ -0,0 +1,63 @@
+# Privacy Policy
+
+Effective May 31, 2026. This policy explains what ForgeCAD collects and how it is used.
+
+Human-readable page: https://forgecad.io/privacy
+
+## Who we are
+
+ForgeCAD is operated by Narek Kostandyan, Individual Entrepreneur, doing business as "ForgeCAD". For privacy requests or questions, contact contact@forgecad.io.
+
+## Information we collect
+
+ForgeCAD collects account information such as name, email address, authentication provider data, avatar, plan status, settings, and legal acceptance records.
+
+ForgeCAD stores project files, model code, generated outputs, published shares, API tokens, billing state, support messages, and service logs needed to operate the product.
+
+ForgeCAD may collect technical information such as IP address, browser, device, operating system, approximate location, pages viewed, CLI command metadata, errors, performance data, and security events.
+
+## How we use information
+
+We use information to provide the editor, CLI, project sync, publishing, billing, support, security, abuse prevention, diagnostics, product improvement, and legal compliance.
+
+We may use aggregated or de-identified information to understand product usage and improve reliability, documentation, performance, and onboarding.
+
+## Private project content
+
+Private projects are not sold. ForgeCAD does not use private project content to train public AI models unless you explicitly agree to that use or ask us to process the content for a feature that requires it.
+
+If you publish or share a model, people with access to the published or shared link may view the content according to the sharing settings you choose.
+
+## Cookies and local storage
+
+ForgeCAD uses cookies, local storage, and similar technologies for authentication, CSRF protection, preferences, checkout flow continuity, session security, and product diagnostics.
+
+Some browser storage is essential for the service to work. You can control cookies through your browser, but disabling them may break sign-in or hosted project features.
+
+## Service providers
+
+ForgeCAD may use service providers for hosting, databases, email delivery, payment processing, analytics, error monitoring, authentication, storage, and customer support.
+
+Payment details are handled by payment providers such as Stripe. ForgeCAD does not store full card numbers.
+
+## Security and retention
+
+We use reasonable technical and organizational safeguards, but no internet service can guarantee perfect security.
+
+We retain information while your account is active, while needed to provide the service, or while needed for legal, security, billing, backup, and dispute-resolution purposes.
+
+## Deletion and rights
+
+You may delete your account from the product where supported or contact contact@forgecad.io for account, project, or privacy requests.
+
+Depending on where you live, you may have rights to access, correct, delete, export, restrict, or object to the processing of your personal information.
+
+## International use
+
+ForgeCAD and its service providers may process information in countries other than where you live. When required, we rely on appropriate safeguards for international transfers.
+
+## Children and changes
+
+ForgeCAD is not directed to children under 13. Do not create an account if you are not old enough to use online services in your jurisdiction.
+
+We may update this policy as the product changes. Material updates will be reflected on this page with a new effective date.

package/dist/docs-raw/legal/software-license.md

@@ -0,0 +1,55 @@
+# ForgeCAD Software License
+
+Effective May 31, 2026. This license governs the ForgeCAD npm package, CLI, browser application code, bundled runtime, and packaged assets.
+
+Human-readable page: https://forgecad.io/license
+
+## Software covered
+
+This license applies to the ForgeCAD npm package, command-line interface, browser application code, bundled runtime, and packaged assets distributed with ForgeCAD.
+
+ForgeCAD, including its compiler, runtime, CLI, browser application, APIs, standard library, schemas, documentation, and packaged assets, is owned by Narek Kostandyan, Individual Entrepreneur (d.b.a. "ForgeCAD"). All rights not expressly granted in this license are reserved.
+
+Public example files, public agent skills, and public companion repositories may use a separate license when a repository or file says so.
+
+## Free personal non-commercial use
+
+You may install and use the Software for free for personal non-commercial use, learning, experimentation, individual evaluation, and other non-commercial work.
+
+## Pro commercial use
+
+If you use the Software as a human-operated CAD tool for commercial work, you need an active ForgeCAD Pro subscription unless ForgeCAD has separately agreed to different written terms.
+
+This includes designing models for customers, client work, paid freelance work, employer work, products for sale, and funded commercial projects.
+
+## Enterprise backend, embedded, and AI use
+
+You need a ForgeCAD Enterprise agreement before using the Software in an automated backend, hosted service, embedded application, product integration, reinforcement-learning environment, AI training or evaluation workflow, benchmark, or other internal or external application workflow that calls ForgeCAD on behalf of users, customers, jobs, scripts, agents, models, or external systems.
+
+For clarity, high-throughput, parallel, automated, or programmatic generation, rendering, validation, or evaluation requires an active ForgeCAD Enterprise agreement, regardless of who owns the resulting models, scripts, outputs, variants, mutations, or data derivatives.
+
+## Your models and outputs
+
+You own the models, scripts, exports, images, reports, and other outputs you create with ForgeCAD, subject to your rights in any input material and subject to using ForgeCAD under the required plan for your use case.
+
+## Pricing and written agreements
+
+Current plan details are available at forgecad.io/pricing. If you have a written agreement with ForgeCAD, that agreement controls where it conflicts with this license.
+
+## Restrictions
+
+Except as allowed by this license or by a separate written agreement, you may not sell, sublicense, rent, lease, redistribute, white-label, or offer the Software itself as a hosted, embedded, or API service.
+
+You may not remove copyright, license, pricing, telemetry, subscription, or branding notices, or bypass license checks, subscription checks, usage limits, or technical protection measures.
+
+## No warranty, limitation, and termination
+
+The Software is provided as is, without warranty of any kind.
+
+To the maximum extent permitted by law, ForgeCAD and Narek Kostandyan, Individual Entrepreneur, will not be liable for indirect, incidental, special, consequential, exemplary, or punitive damages or for lost profits, revenue, data, manufacturing losses, procurement losses, or business interruption.
+
+Your rights under this license terminate automatically if you violate these terms. After termination, you must stop using the Software unless ForgeCAD reinstates your rights in writing.
+
+## Contact
+
+For Enterprise licensing, commercial questions, or alternative licensing terms, contact contact@forgecad.io.

package/dist/docs-raw/legal/terms.md

@@ -0,0 +1,87 @@
+# Terms of Service
+
+Effective May 31, 2026. These terms govern ForgeCAD accounts, hosted services, software access, and paid plans.
+
+Human-readable page: https://forgecad.io/terms
+
+## Acceptance
+
+ForgeCAD is operated by Narek Kostandyan, Individual Entrepreneur, doing business as "ForgeCAD" ("ForgeCAD", "we", "us").
+
+By creating an account, accessing ForgeCAD, installing the ForgeCAD software, or using the hosted service, you agree to these Terms, the Privacy Policy, and the ForgeCAD Software License.
+
+If you use ForgeCAD for an organization, you represent that you have authority to bind that organization. A separately signed agreement with ForgeCAD controls where it conflicts with these Terms.
+
+## Accounts and eligibility
+
+You are responsible for your account, credentials, API tokens, project files, and all activity under your account.
+
+Do not create an account if you are not old enough to use online services in your jurisdiction or if you cannot legally agree to these Terms.
+
+## Plans and commercial use
+
+Free is for personal non-commercial use, learning, experimentation, individual evaluation, and other non-commercial work.
+
+Pro covers one named person using ForgeCAD as a human-operated CAD tool for commercial work, including client work, employer work, professional models, products for sale, and funded commercial projects.
+
+Each person doing commercial ForgeCAD work needs their own active Pro subscription unless ForgeCAD has separately agreed to different written terms.
+
+Enterprise is required for automated backend use, hosted or embedded workflows, product integrations, shared seats, team deployments that need custom terms, and AI training, evaluation, benchmarking, or reinforcement-learning environments.
+
+## Enterprise AI and automation use
+
+You may not use ForgeCAD as infrastructure for training, evaluating, benchmarking, fine-tuning, reinforcement learning, reward environments, automated model generation, or agent workflows unless you have an active ForgeCAD Enterprise agreement.
+
+This applies whether the workflow is external-facing or internal, and whether it runs for users, customers, jobs, scripts, agents, models, or other automated systems.
+
+Ownership of models, scripts, environments, exports, or other outputs does not grant a license to use the ForgeCAD software, runtime, CLI, APIs, docs, examples, skills, validation tools, or methods outside the plan required for that use case.
+
+For clarity, ownership of any model, script, environment, task, or output, including any variant, mutation, or derivative produced by running the ForgeCAD compiler, runtime, CLI, or APIs, does not grant any right to operate ForgeCAD for high-throughput, parallel, automated, or programmatic generation, rendering, validation, or evaluation. Such operation requires an active ForgeCAD Enterprise agreement, regardless of who owns the resulting data.
+
+## Your content and outputs
+
+You retain your rights in models, scripts, exports, images, reports, project files, prompts, and other content you create or upload, subject to your rights in any input material and your compliance with the required ForgeCAD plan.
+
+You grant ForgeCAD the limited rights needed to host, process, render, validate, store, transmit, back up, and display your content for the service features you use.
+
+If you publish or share a model, you are responsible for the content you make available and for having the rights needed to share it.
+
+## Acceptable use and compliance
+
+Do not use ForgeCAD to break the law, infringe others' rights, bypass license or subscription controls, attack the service, scrape private data, upload malware, or interfere with other users.
+
+Do not upload regulated, export-controlled, classified, or highly sensitive information unless you have the legal right to do so and a separate written agreement with ForgeCAD covers that use.
+
+Do not resell, sublicense, lease, redistribute, white-label, or offer ForgeCAD itself as a hosted service, API, embedded product, or application feature without a written Enterprise agreement.
+
+## Billing
+
+Paid subscriptions renew until canceled. Stripe or another payment provider may process checkout, tax collection, invoices, and payment details.
+
+You are responsible for applicable taxes, accurate billing information, and timely payment. Fees are non-refundable except where required by law or separately agreed in writing.
+
+Plan names, prices, limits, and included features may change. Existing paid users will receive reasonable notice before material plan changes take effect.
+
+## CAD, manufacturing, and safety
+
+ForgeCAD is a design and automation tool. You are responsible for reviewing, testing, validating, and safely manufacturing any model, export, toolpath, part, assembly, or design decision.
+
+Do not rely on ForgeCAD output as a substitute for professional engineering review, safety certification, regulatory compliance, or manufacturing quality control.
+
+## Service changes and termination
+
+ForgeCAD may change, suspend, or discontinue features, limits, or service availability as the product evolves.
+
+ForgeCAD may suspend or terminate access if you violate these Terms, create security or operational risk, or fail to pay required fees.
+
+## Warranty and liability
+
+ForgeCAD is provided as is, without warranties of merchantability, fitness for a particular purpose, non-infringement, availability, or accuracy.
+
+To the maximum extent permitted by law, ForgeCAD and Narek Kostandyan, Individual Entrepreneur, will not be liable for indirect, incidental, special, consequential, exemplary, or punitive damages, lost profits, lost revenue, lost data, manufacturing losses, procurement losses, or business interruption.
+
+## Changes and contact
+
+ForgeCAD may update these Terms as the product changes. Material updates will be reflected on this page with a new effective date.
+
+For legal, privacy, billing, or Enterprise questions, contact contact@forgecad.io.

package/dist/docs-raw/skills/forgecad-3d-reconstruction.md

@@ -5,7 +5,7 @@ Reconstruct a parametric ForgeCAD model from an existing 3D CAD or mesh file suc
 | Field | Value |
 | --- | --- |
 | Installed by | `forgecad skill install` |
-| Source | `skills/forgecad-3d-reconstruction/SKILL.md` |
+| Source | `agent-skill-library/forgecad-3d-reconstruction/SKILL.md` |
 
 ---
 

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

@@ -5,7 +5,7 @@ Create rough high-level ForgeCAD concept models from simple primitives to explor
 | Field | Value |
 | --- | --- |
 | Installed by | `forgecad skill install` |
-| Source | `skills/forgecad-blockout-model/SKILL.md` |
+| Source | `agent-skill-library/forgecad-blockout-model/SKILL.md` |
 
 ---
 

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

@@ -5,7 +5,7 @@ Enforce the ForgeCAD Component Model when building multi-part assemblies. Parts
 | Field | Value |
 | --- | --- |
 | Installed by | `forgecad skill install` |
-| Source | `skills/forgecad-component-model/SKILL.md` |
+| Source | `agent-skill-library/forgecad-component-model/SKILL.md` |
 
 ---
 
@@ -31,9 +31,11 @@ A part is a function from props to `{ shape, connectors, metadata }`. It builds
 - A connector = origin + axis (outward from the part)
 - Connectors meet **face-to-face**: both axes point outward, system brings them together
 - For prismatic joints: axes point along the shared slide direction
+- Mirrored revolute axes need negated physical joint values for the same mirrored pose
 
 #### 3. Assembly Is Pure Composition
-- `addPart()` + `connect()` + `addJointCoupling()` — nothing else
+- Use `addPart()` + `connect()` for frame-aware serial assemblies
+- Use `link()` + `edgeBetweenLinks()` + `addAngleBetweenLinks()` for solved point skeletons
 - Zero `translate()` calls for structural parts
 - Zero coordinate math
 - The assembly passes props down and reads metadata up
@@ -65,6 +67,13 @@ mount.withConnectors({
 assembly.connect("Base.mount_face", "Mount.flange", { as: "mount-fix" });
 ```
 
+Revolute values are signed by the physical hinge axis. In a bilateral mechanism,
+`axis: [1, 0, 0]` on the right side and `axis: [-1, 0, 0]` on the left side are
+exact mirrors at rest, but the same `+theta` value rotates them in opposite
+fore/aft senses. Use `Right: +theta`, `Left: -theta`, and mirror physical limits
+as `[min, max] -> [-max, -min]`, or drive both sides from a side-neutral link
+graph/control layer.
+
 ### Part Return Shape
 
 Every part file returns a structured object:

package/dist/docs-raw/skills/forgecad-high-level-spec.md

@@ -5,7 +5,7 @@ Write a high-level design document (HLD) for a model, mechanism, or assembly bef
 | Field | Value |
 | --- | --- |
 | Installed by | `forgecad skill install` |
-| Source | `skills/forgecad-high-level-spec/SKILL.md` |
+| Source | `agent-skill-library/forgecad-high-level-spec/SKILL.md` |
 
 ---
 

package/dist/docs-raw/skills/forgecad-image-replicator.md

@@ -5,7 +5,7 @@ Build real ForgeCAD geometry from one or more reference images by treating image
 | Field | Value |
 | --- | --- |
 | Installed by | `forgecad skill install` |
-| Source | `skills/forgecad-image-replicator/SKILL.md` |
+| Source | `agent-skill-library/forgecad-image-replicator/SKILL.md` |
 
 ---
 
@@ -119,10 +119,10 @@ node dist-cli/forgecad.js render 3d path/to/model.forge.js /tmp/<slug>-replicate
   --size 1000 --edges thin
 ```
 
-Build side-by-side boards with the bundled helper:
+Build side-by-side boards with the bundled helper. It is a self-contained `uv` script that installs Pillow on demand and does not require Chrome. The examples use the ForgeCAD source-checkout path; if the skill is installed elsewhere, resolve `scripts/compare_images.py` relative to the `forgecad-image-replicator` skill directory.
 
 ```bash
-node skills/forgecad-image-replicator/scripts/compare_images.mjs \
+uv run agent-skill-library/forgecad-image-replicator/scripts/compare_images.py \
   /tmp/<slug>-replicate/refs/front.png \
   /tmp/<slug>-replicate/render-front.png \
   /tmp/<slug>-replicate/compare-front.png \
@@ -132,10 +132,10 @@ node skills/forgecad-image-replicator/scripts/compare_images.mjs \
 Common helper options:
 
 ```bash
-node skills/forgecad-image-replicator/scripts/compare_images.mjs ref.png render.png compare.png
-node skills/forgecad-image-replicator/scripts/compare_images.mjs ref.jpg render.png compare.png --height 1200 --fit contain
-node skills/forgecad-image-replicator/scripts/compare_images.mjs ref.png render.png compare.png --fit cover --labels "Target,Current"
-node skills/forgecad-image-replicator/scripts/compare_images.mjs ref.png render.png compare.png --no-labels
+uv run agent-skill-library/forgecad-image-replicator/scripts/compare_images.py ref.png render.png compare.png
+uv run agent-skill-library/forgecad-image-replicator/scripts/compare_images.py ref.jpg render.png compare.png --height 1200 --fit contain
+uv run agent-skill-library/forgecad-image-replicator/scripts/compare_images.py ref.png render.png compare.png --fit cover --labels "Target,Current"
+uv run agent-skill-library/forgecad-image-replicator/scripts/compare_images.py ref.png render.png compare.png --no-labels
 ```
 
 Use `--fit contain` by default. Use `--fit cover` only when both images already share the same crop and aspect.
@@ -177,4 +177,4 @@ For non-trivial references, expect several render, compare, canonical-view, and
 ## Bundled Files
 
 - `agents/openai.yaml`
-- `scripts/compare_images.mjs`
+- `scripts/compare_images.py`

package/dist/docs-raw/skills/forgecad-lld.md

@@ -5,7 +5,7 @@ Write a Low-Level Design (LLD) for a CAD model — exact dimensions, constraints
 | Field | Value |
 | --- | --- |
 | Installed by | `forgecad skill install` |
-| Source | `skills/forgecad-lld/SKILL.md` |
+| Source | `agent-skill-library/forgecad-lld/SKILL.md` |
 
 ---
 

package/dist/docs-raw/skills/forgecad-make-a-model.md

@@ -5,7 +5,7 @@ Create manufacture-realistic prototype ForgeCAD (.forge.js) models in the active
 | Field | Value |
 | --- | --- |
 | Installed by | `forgecad skill install` |
-| Source | `skills/forgecad-make-a-model/SKILL.md` |
+| Source | `agent-skill-library/forgecad-make-a-model/SKILL.md` |
 
 ---
 
@@ -49,9 +49,14 @@ Use today's date for the directory. Use the user's current ForgeCAD project when
 
 ### Workflow
 
-1. Load the ForgeCAD skill — always invoke the `forgecad` skill first to get API docs and authoring guidance. Read at minimum the Core API reference. If any two parts are intended to touch or mate in the final model, read the positioning guide immediately and default to connectors + `matchTo()`.
+1. Load the ForgeCAD skill — always invoke the `forgecad` skill first to get API docs and authoring guidance. Read at minimum the Core API reference. If the model has moving parts, load the assembly group and `docs/permanent/guides/joint-design.md` before writing geometry. If any two parts are intended to touch or mate in the final model, read the positioning guide immediately and default to connectors + `matchTo()`.
 2. Create the directory — `mkdir -p YYYY/MM/DD/[folder]` as needed.
-3. Write the model — create the `.forge.js` file(s) following ForgeCAD conventions:
+3. Prove moving-part kinematics before detailed geometry — for any mechanism, robot, linkage, hinge, slider, suspension, gripper, wheel train, drawer, door, linkage toy, or articulated product:
+   - Author the rig first: links, frames, fixed ground references, parent/child relationships, joints, couplings, limits, defaults, mirrored-side sign mapping, and named controls.
+   - Choose the right rig primitive before modeling the skin: use link graphs (`link()`, `edgeBetweenLinks()`, `addAngleBetweenLinks()`) for point skeletons and closed loops; use frame/connector joints (`frame()`, `revoluteJoint()`, `prismaticJoint()`, `connect()`, `match()`) when part orientation matters.
+   - Attach only simple markers, bars, or proxy parts at first. Return the `Assembly` directly and run it at rest, mid-travel, and limit joint values until the solver, controls, connector/frame alignment, and `verify.*` checks pass.
+   - Only after the rig works should you replace proxies with manufacture-real geometry attached to the solved links, frames, and connectors. Do not bake a posed `SolvedAssembly` as the default return just to make one pose look right.
+4. Write the model — create the `.forge.js` file(s) following ForgeCAD conventions:
    - Treat the default build profile as `manufacture-realistic prototype`; choose and encode the artifact's manufacturing/process cues before adding styling detail
    - Declare `param()` / `boolParam()` for all tunable dimensions
    - If the model is split across files, use `main.forge.js` as the primary entry point, import renderable parts from neighboring `.forge.js` files, and keep only pure helpers/constants in plain `.js` modules
@@ -62,11 +67,12 @@ Use today's date for the directory. Use the user's current ForgeCAD project when
    - Make final mating geometry physically plausible: parts may touch, clear each other, or be boolean-joined, but should not unintentionally pass through each other
    - Model the physical artifact, not an educational diagram: no explanatory arrows, floating labels, section labels, legends, or text plaques unless the user explicitly requested a presentation/teaching view
    - Do not make the default returned model a cutaway, sectioned shell, permanently exploded assembly, or hidden-parts teaching view. ForgeCAD gives the user viewer and inspection tools for slicing, exploding, hiding, and looking inside after the real CAD exists.
-   - Return the final geometry (single shape, array, or named objects array)
+   - Return the final artifact (single shape, array, named objects array, or `Assembly` for moving mechanisms)
+   - For moving assemblies, return the `Assembly` itself whenever possible so Motion controls re-run the real kinematic solve; avoid legacy viewport-only animation APIs for new work unless the user explicitly asks for them
    - Treat `fillet(shape, r)` and `chamfer(shape, r)` as experimental edge treatments: Manifold can produce incorrect results and OCCT can be very slow. Prefer simpler primitive profiles, lower segment counts, targeted edge selectors, and inspection before relying on the result.
-4. Validate — run `forgecad run <file>` to check for errors. For multi-file projects, always validate `main.forge.js`.
-5. Verify geometry — render a multi-angle visual evidence set before final delivery: whole-model context plus agent-chosen orthographic, oblique, underside, or hidden-object views that expose the relevant components and interfaces. Choose camera directions from the model's shape and likely failure modes, not from a fixed recipe. Use those views to look for internals that are accidentally visible, parts that visibly do not fit, floating details, blocked access, missing seats, and unexpected interference. Run `forgecad inspect physical components` when the model has multiple returned objects or visible attachments, run `forgecad debug assembly --fail-on warning` when the script uses `assembly()`, run `forgecad inspect mechanical-integrity <project-or-file> --collisions` before sharing generated mechanical work, and run the targeted `forgecad inspect <family> <mode>` commands that match the task (see Final Acceptance Gate and Render-Verify Loop below). For multi-file projects, render and inspect `main.forge.js`. Collision findings are model work, not FYI: remove unexpected overlaps before delivery.
-6. Iterate from visual and inspection feedback — treat every render and inspection bundle as model evidence, not a checkbox. Read the normal PNGs, manifest, and evidence PNGs; convert each unexpected collision, thin region, missing section detail, wrong component count, floating body, distance gap, confusing object-color result, accidentally exposed internal structure, bad fit, or visually unsupported interface into a concrete model edit; then rerun the same targeted evidence pass until the result matches the intended physical component graph.
+5. Validate — run `forgecad run <file>` to check for errors. For multi-file projects, always validate `main.forge.js`. For moving assemblies, also run representative joint states with `--joint`, including rest/default, mid-travel, both limits, and any coupled or mirrored poses.
+6. Verify geometry — render a multi-angle visual evidence set before final delivery: whole-model context plus agent-chosen orthographic, oblique, underside, or hidden-object views that expose the relevant components and interfaces. Choose camera directions from the model's shape and likely failure modes, not from a fixed recipe. Use those views to look for internals that are accidentally visible, parts that visibly do not fit, floating details, blocked access, missing seats, and unexpected interference. For moving assemblies, render at several joint values with `--joint` so clearance, range, stops, and connected followers are proven in motion, not only at rest. Run `forgecad inspect physical components` when the model has multiple returned objects or visible attachments, run `forgecad debug assembly --fail-on warning` when the script uses `assembly()`, run `forgecad inspect mechanical-integrity <project-or-file> --collisions` before sharing generated mechanical work, and run the targeted `forgecad inspect <family> <mode>` commands that match the task (see Final Acceptance Gate and Render-Verify Loop below). For multi-file projects, render and inspect `main.forge.js`. Collision findings are model work, not FYI: remove unexpected overlaps before delivery.
+7. Iterate from visual and inspection feedback — treat every render and inspection bundle as model evidence, not a checkbox. Read the normal PNGs, manifest, and evidence PNGs; convert each unexpected collision, thin region, missing section detail, wrong component count, floating body, distance gap, confusing object-color result, accidentally exposed internal structure, bad fit, bad joint sweep, unconverged pose, follower drift, or visually unsupported interface into a concrete model edit; then rerun the same targeted evidence pass until the result matches the intended physical component graph.
 
 ### Manufacturing Process Is Not Assumed
 
@@ -123,6 +129,28 @@ Do not reveal hidden structure by permanently cutting away the production geomet
 
 When internals are hidden by the final exterior, verify them with exploration tools instead of changing the artifact: render underside or alternate camera views, use `forgecad inspect sections at|stack|sample`, use viewer-only cut planes or explode controls, temporarily make a shell transparent, or add named ghost objects for fit checks. Those views are diagnostic/presentation modes; they must not replace the real model unless the user explicitly asked for a cutaway teaching model.
 
+### Kinematics-First for Moving Parts
+
+For moving models, the mechanism rig is the source of truth. Do not start with finished housings, arms, shells, covers, or decorative surfaces and then try to retrofit motion. Build the motion structure first, prove it, and attach geometry to it.
+
+- Decide the rig shape before geometry: point links for closed-loop skeletons and distance/angle constraints; frames and connector joints for serial rigid parts whose orientation matters.
+- Name every moving degree of freedom and encode its limits/defaults at the rig level. For mirrored revolute axes, make the sign mapping explicit instead of assuming equal values create mirrored poses.
+- Add simple proxy geometry only to expose the rig: pivot markers, bars between links, slider blocks, wheel discs, or frame axes. Use those proxies to verify the mechanism before adding real material.
+- Attach final geometry to solved links, frames, and connectors. A visible arm, cover, wheel, drawer, or follower should move because it is mated to the rig, not because a final `rotate()` or `translate()` happens to make one pose look assembled.
+- Keep the default return as the unsolved `Assembly` when possible. This lets Motion controls and CLI `--joint` overrides re-run the real solve.
+- Put representative pose checks in the script with `verify.*`: convergence, connector origins coinciding, link lengths holding, end effectors reaching their expected points, followers remaining attached, and required running clearances staying positive.
+
+At minimum, run the mechanism at rest, mid-travel, both limits, and any mirrored/coupled poses:
+
+```bash
+node dist-cli/forgecad.js run model.forge.js --joint "theta=0"
+node dist-cli/forgecad.js run model.forge.js --joint "theta=45"
+node dist-cli/forgecad.js run model.forge.js --joint "theta=90"
+node dist-cli/forgecad.js render 3d model.forge.js /tmp/model-theta-45.png --joint "theta=45" --camera iso --size 700
+```
+
+Use the real joint/control names from the assembly. For multiple controls, repeat `--joint`: `--joint "hip=20" --joint "knee=-35"`. If any pose fails to solve, clamps unexpectedly, breaks a connector check, or creates a new collision, the rig is not ready for final geometry.
+
 ### Mechanical Assembly Contract
 
 For mechanical models, a ForgeCAD script is not done when it merely looks assembled. Every visible piece must have a believable physical reason to be where it is: fused material, contact faces, a screw stack, a pin in a bore, a tab in a slot, a gasket on a land, a bearing in a seat, a cable in a channel, or a named intentional ghost.
@@ -137,37 +165,7 @@ For mechanical models, a ForgeCAD script is not done when it merely looks assemb
 - Purchased loose parts may remain separate bodies, but they should be named as purchased hardware or consumables and should sit in believable sockets, bores, races, guides, or fastener stacks.
 - Encode interface intent with `verify.*`, not only comments. Use `verify.clearanceBetween("cover is seated on gasket", cover, gasket, -0.01, 0.05)` for contact/seated fits and clearance bands, `verify.minClearance(...)` or `verify.notColliding(...)` for keep-out/running gaps, and `verify.connectorDistance(...)` for connector-authored mates. Part counts and generic dimensions are useful supporting checks, but they do not prove an interface by themselves.
 
-For ordinary removable covers, prefer `lib.boltedServiceCover(...)` before hand-placing plates, tabs, screw heads, gaskets, and holes. It creates the parent ledge, gasket, cover plate with fused pull tabs, shared bolt pattern, and installed screws as one mechanically accountable interface.
-
-For electronics boxes, backplates, service-stack housings, and camera/monitor enclosures, prefer `lib.datumEnclosureAssembly(...)` before independently placing panels, ribs, bosses, ports, covers, and screws. It creates the tray, ledges, standoffs, ribs, service port, gasket, cover, and screws from one shared datum system.
-
-For PCB-mounted terminal blocks, thermostat backplates, control boards, and wire-entry electronics panels, prefer `lib.pcbTerminalBlockAssembly(...)` before placing a loose green block near a board or cover. It creates the backplate, fused standoffs, PCB mounting screws, PCB pin holes, terminal pins, and seated purchased terminal block from one shared datum system.
-
-For snap-retained covers, cartridges, small clasps, and housings, prefer `lib.snapLatchCoverAssembly(...)` before drawing decorative snap tabs. It creates latch windows, underside catch lands, fused snap hooks, barbs, and clearance checks so the cover is retained by real geometry.
-
-For ordinary pinned handles, cam levers, release levers, and latch arms, prefer `lib.pinnedLeverAssembly(...)` before hand-placing a hub, arm, washers, and pin. It creates a fused lever body, aligned pivot bore, retained pin, thrust washers, support land, and low stop land as one mechanically accountable pivot stack.
-
-For trunnions, side knobs, adjustable pivots, and clamp shafts, prefer `lib.retainedShaftAssembly(...)` before hand-placing rods, washers, and knobs. It creates bored support cheeks, a through shaft, thrust washers, knobs, retaining heads, and shared bore dimensions as one mechanically accountable stack.
-
-For thumb screws, desk clamps, vise screws, capo pressure screws, and small fixture hold-downs, prefer `lib.thumbScrewClampAssembly(...)` before hand-placing a knob, screw cylinder, pressure pad, and bracket jaw. It creates the C-frame, threaded boss/bore, captive pressure pad, hand knob, and seated workpiece contact from one shared datum system.
-
-For drawer slides, quick-release plates, and guided linear carriages, prefer `lib.capturedLinearSlide(...)` before hand-placing rails and a block. It creates a U-channel rail with return lips, end stops, a captured carriage, and explicit travel/clearance dimensions.
-
-For pump cartridges, filter cassettes, battery cartridges, skeg cassettes, and removable slide-in modules, prefer `lib.capturedCartridgeGuideAssembly(...)` before placing a loose tray and block. It creates return lips, a rear stop, a captured cartridge flange, pull tab, insertion travel, and explicit clearance dimensions.
-
-For molded flexible battery doors, sample covers, blister latches, and polypropylene-style service flaps, prefer `lib.livingHingeCoverAssembly(...)` before drawing two plates with a decorative hinge strip. It creates one fused molded strip with fixed leaf, thin flexible web, moving cover leaf, pull lip, snap barb, catch land, and web-thickness checks.
-
-For doors, barn-door leaves, lids, locket leaves, and small hinged access panels, prefer `lib.knuckledHingeAssembly(...)` before hand-placing barrels and a pin. It creates alternating fused knuckles, two leaves, a shared bore, and a retained pin as one mechanically accountable hinge.
-
-For crank links, damper rod ends, crossheads, and clevis-yoke pivots, prefer `lib.clevisPinJointAssembly(...)` before hand-placing an eyelet and pin. It creates bored clevis ears, a captured center link eye, a rear bridge, and a retained pin as one mechanically accountable load path.
-
-For bearings, rollers, burr cartridges, spindle supports, and purchased radial bearings, prefer `lib.seatedBearingAssembly(...)` before hand-placing a ring and shaft near a block. It creates a bored housing, counterbore pocket, bearing shoulder, seated bearing, shaft, collars, and shared clearance dimensions as one mechanically accountable support.
-
-For cables, wires, hoses, pump tubes, and panel pass-throughs, prefer `lib.cableGlandAnchorAssembly(...)` before hand-placing a loose cylinder near a wall. It creates the panel clearance hole, hollow gland body, compression nut, and routed cable/tube as one mechanically accountable pass-through.
-
-For routed cables, wires, hoses, pump tubes, and sensor leads that run along a surface, prefer `lib.routedTubeClipAssembly(...)` before drawing a tube that floats between endpoints. It creates a base panel, saddle clip bores, clip screw holes, installed screws, and the retained tube route from one shared datum system.
-
-For fluid hoses, pump inlets/outlets, filter ports, and lab tubing, prefer `lib.hoseBarbPortAssembly(...)` before drawing a tube that stops at a block. It creates the bored receiver, raised boss, hollow barbed fitting, installed hose, and clamp band as one accountable hose-port interface.
+Do not introduce canned finished-object helpers for project-specific assemblies. When a repeated physical pattern appears, build the project-specific interface explicitly: use `lib.fastenerSet()` or `lib.boltPattern()` for screw stacks, real bores/counterbores/pockets for purchased parts, connectors plus `matchTo()` for mating parts, and `verify.*` checks for seated contact and running clearances. Reusable library vocabulary should be primitives, cutters, patterns, and mechanical contracts, not finished thermostat backplates, clamp brackets, hinge leaves, or other canned objects.
 
 ### Final Geometry Should Be Physically Plausible
 
@@ -211,6 +209,8 @@ Before telling the user the model is done, prove both technical validity and vis
 
    The model should include at least one verification that proves a mechanical interface, not just object count. Prefer checks such as `verify.clearanceBetween("bearing is seated in pocket", bearing, housing, -0.01, 0.1)`, `verify.minClearance("carriage clears rail", carriage, rail, 0.15)`, `verify.notColliding("cover screw clears parent hole", screw, parent)`, or `verify.connectorDistance("leg connector is seated", bench, "Rail.leg_0", "Leg0.head", 0, 0.01)`.
 
+   For moving assemblies, this gate is incomplete until the rig has been run through representative control states. Use `--joint` overrides and/or in-script `solve(state)` verification to cover rest/default, mid-travel, physical limits, coupled states, and mirrored-side poses. Each tested pose should keep the solver converged, attached geometry following the rig, and clearances/collisions within the intended mechanical contract.
+
 2. Run collision evidence and read both the manifest and images:
 
    ```bash
@@ -246,7 +246,7 @@ Before telling the user the model is done, prove both technical validity and vis
 
 5. Treat ProductSkin and surface-member limitations honestly. If `inspect fit interference` reports boolean-test warnings because a sampled `Product.skin` loft has boundary edges, distinguish that from real collision findings. You may still deliver if `collisionCount` is clean, the intended connectivity is correct, and the visual attachment audit passes. Mention the residual warning briefly in the final response.
 
-6. Final response must name the evidence: commands run, render views checked, any focus/hide filters used, component count, collision count, and any residual warnings or intentional exceptions. Do not just say "validated."
+6. Final response must name the evidence: commands run, render views checked, joint values tested for moving assemblies, any focus/hide filters used, component count, collision count, and any residual warnings or intentional exceptions. Do not just say "validated."
 
 ### Render-Verify Loop
 
@@ -443,6 +443,7 @@ Primitive placement convention:
 Key composition tools:
 
 - Connectors + `matchTo()` for parts that should touch in the final model
+- `assembly()` link graphs, frames, and connector joints for moving mechanisms
 - `group()` for local-coordinate subassemblies
 - `attachTo()` for quick bounding-box placement
 - `.translate()` / `.rotate()` for free offsets or bridging computed locations, not as the default assembly contract

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

@@ -5,7 +5,7 @@ Analyze, verify, and grade ForgeCAD or CAD-as-code models against a user require
 | Field | Value |
 | --- | --- |
 | Installed by | `forgecad skill install` |
-| Source | `skills/forgecad-model-grader/SKILL.md` |
+| Source | `agent-skill-library/forgecad-model-grader/SKILL.md` |
 
 ---
 
@@ -64,7 +64,7 @@ This skill is an evaluator workflow. Do not edit the model unless the user expli
 
    ```bash
    node dist-cli/forgecad.js inspect fit interference path/to/model.forge.js /tmp/model-grade/collisions --camera iso --force --size 700
-   python skills/forgecad-render-inspect/summarize_manifest.py /tmp/model-grade/collisions
+   python agent-skill-library/forgecad-render-inspect/summarize_manifest.py /tmp/model-grade/collisions
    ```
 
    Read the manifest and inspect the relevant evidence PNGs. Treat unexpected collisions, thin regions, missing sections, wrong component counts, floating bodies, and confusing object colors as evidence, not as warnings to wave away.

package/dist/docs-raw/skills/forgecad-prepare-prompt.md

@@ -5,7 +5,7 @@ Turn a fuzzy physical product, mechanism, or CAD artifact request into a concret
 | Field | Value |
 | --- | --- |
 | Installed by | `forgecad skill install` |
-| Source | `skills/forgecad-prepare-prompt/SKILL.md` |
+| Source | `agent-skill-library/forgecad-prepare-prompt/SKILL.md` |
 
 ---
 
@@ -181,7 +181,7 @@ By the end of this skill, there should be:
 
 9. If implementation continues immediately, hand off to `forgecad`.
    For moving mechanisms, load:
-   - `skills/forgecad/SKILL.md`
+   - `~/.agents/skills/forgecad/SKILL.md`
    - `docs/permanent/generated/assembly.md`
    - `docs/permanent/generated/output.md`
    - `docs/permanent/guides/joint-design.md`

package/dist/docs-raw/skills/forgecad-project.md

@@ -5,7 +5,7 @@ ForgeCAD project CLI workflow — creating, managing, syncing projects and files
 | Field | Value |
 | --- | --- |
 | Installed by | `forgecad skill install` |
-| Source | `skills/forgecad-project/SKILL.md` |
+| Source | `agent-skill-library/forgecad-project/SKILL.md` |
 
 ---
 
@@ -15,6 +15,8 @@ ForgeCAD project CLI workflow — creating, managing, syncing projects and files
 
 **forgecad.io** is the primary platform for ForgeCAD projects. The CLI is the main way AI agents interact with it — creating projects, managing files, publishing models, and collaborating. `forgecad studio <project-path> [project-path ...]` opens the installed local editor for users; `forgecad dev <project-path> [project-path ...]` is mainly for ForgeCAD source development.
 
+Keep one long-running `forgecad studio <project-path> [project-path ...]` process open with every active project folder listed in its arguments; the user opens the single printed localhost port once, and AI agents should only create or edit files under those folders so the browser updates live without starting more servers.
+
 ### Authentication
 
 ```sh

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

@@ -5,7 +5,7 @@ Solve ForgeCAD CAD reconstruction benchmark or RL episodes in a prepared workspa
 | Field | Value |
 | --- | --- |
 | Installed by | `forgecad skill install` |
-| Source | `skills/forgecad-reconstruction-benchmark/SKILL.md` |
+| Source | `agent-skill-library/forgecad-reconstruction-benchmark/SKILL.md` |
 
 ---
 

package/dist/docs-raw/skills/forgecad-render-inspect.md

@@ -5,7 +5,7 @@ Run and interpret ForgeCAD inspection bundles for model verification. Use when a
 | Field | Value |
 | --- | --- |
 | Installed by | `forgecad skill install` |
-| Source | `skills/forgecad-render-inspect/SKILL.md` |
+| Source | `agent-skill-library/forgecad-render-inspect/SKILL.md` |
 
 ---
 
@@ -67,7 +67,7 @@ Routing:
    Run the bundled helper:
 
    ```bash
-   python skills/forgecad-render-inspect/summarize_manifest.py /tmp/model-inspect
+   python agent-skill-library/forgecad-render-inspect/summarize_manifest.py /tmp/model-inspect
    ```
 
    Use `jq` for targeted follow-up when needed:
@@ -93,6 +93,7 @@ Routing:
 | Question | Evidence command |
 |----------|------------------|
 | Quick visual sanity | `inspect visual image` |
+| Kinematic rig, joints, axes, and links | `inspect visual rig` |
 | Object naming and identity | `inspect visual objects` |
 | Exact local section measurement, bore widths, rib thickness through a chosen line | `inspect section --ray ...` |
 | Hidden internals, cavities, pockets, screw paths, captured components | `inspect sections at|stack|sample` |
@@ -111,6 +112,7 @@ Explicit fast bundle:
 
 ```bash
 forgecad inspect visual objects model.forge.js --camera iso --size 700
+forgecad inspect visual rig model.forge.js --camera iso --size 700
 forgecad inspect sections at model.forge.js --plane yz --offset 12.5 --size 700
 forgecad inspect sections stack model.forge.js --plane yz --every 1 --size 700
 forgecad inspect sections sample model.forge.js --count 5 --size 700

package/dist/docs-raw/skills/forgecad-visual-spec.md

@@ -5,7 +5,7 @@ Turn a concrete ForgeCAD artifact, build brief, HLD, or existing model into buil
 | Field | Value |
 | --- | --- |
 | Installed by | `forgecad skill install` |
-| Source | `skills/forgecad-visual-spec/SKILL.md` |
+| Source | `agent-skill-library/forgecad-visual-spec/SKILL.md` |
 
 ---
 

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

@@ -5,7 +5,7 @@ ForgeCAD model authoring, editing, debugging, and execution guidance for .forge.
 | Field | Value |
 | --- | --- |
 | Installed by | `forgecad skill install` |
-| Source | `skills/forgecad/SKILL.md` |
+| Source | Generated from `docs/permanent/` by `scripts/build-forgecad-skill.mjs` |
 
 ---
 
@@ -23,7 +23,7 @@ Author or modify ForgeCAD models, sketches, assemblies, and CLI workflows. Prefe
 6. Default to a concrete first pass — easy iteration beats speculative design review.
 7. If an existing model is broken, replace the weak structure rather than preserving bad architecture.
 8. Validate with `forgecad run <file>` (add `--debug-imports` for import chain issues, and pass `--backend manifold|occt|truck` when the backend matters).
-9. For `jointsView()` animations, keep wrapped revolute tracks continuous across branch cuts; do not assume the viewport will auto-fix `-180/180` jumps.
+9. For moving assemblies, return the `Assembly` directly so runtime controls re-solve the link/edge kinematics model instead of stacking viewport-only transforms.
 10. Model the physical artifact, not an educational diagram. Do not add explanatory labels, arrows, legends, or text plaques unless the user explicitly asks for a presentation or teaching view. Product markings are allowed only when they would exist on the real object.
 11. Build the real closed CAD first. Do not bake cutaways, sectioned shells, permanently exploded layouts, or hidden-parts views into the default model just to show internals. Use viewer-only cut planes, `explodeView`, object hiding, transparency, or `inspect sections` after the artifact exists.
 
@@ -46,6 +46,7 @@ Load groups top-to-bottom, stopping when you have what the task needs.
 Execution model, colors, coordinate system, primitives, booleans, patterns, imports, parameters, topology, edge queries.
 
 - `docs/permanent/API/core/concepts.md`
+- `docs/permanent/generated/runtime-names.md`
 - `docs/permanent/generated/core.md`
 
 #### 2. Static Assembly and Positioning (for any multi-part model)
@@ -95,7 +96,7 @@ Parametric bolts, nuts, washers, standard hardware, gears, pipes, and structural
 
 #### 9. Runtime Viewport APIs (for cut planes, exploded views, hiding, and animation playback)
 
-Viewer-only APIs such as cutPlane, explodeView, jointsView, and animation behavior.
+Viewer-only APIs such as cutPlane, explodeView, render labels, comparison references, and runtime display behavior.
 
 - `docs/permanent/generated/viewport.md`