Agent skill · AI & Agents

forgecad-build-model

Build or edit a manufacture-realistic `.forge.js` model in a project, then validate it with run, render, inspect, and export evidence.

ForgeCADgithub.com/ForgeCADGitHub ↗
claude-codeMIT
Install
npx skills add ForgeCAD/forgecad-public-kit --skill forgecad-build-model --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 22 KB
Bundled scripts: none
Path: skills/forgecad-build-model/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 915
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

Review
written from the skill's own SKILL.md · Aug 5, 2026

What it does

Create new ForgeCAD models in the user's active ForgeCAD project.

How it works

  • Load the forgecad skill and read the Core API reference and related guides.
  • Create a date-based directory structure under the user’s project: mkdir -p YYYY/MM/DD/[folder].
  • Write the model using param() / Param.bool() for tunable dimensions and choose a manufacturing process before styling.
  • Build real internals and ensure the model follows the manufacturing contract rules.
  • Validate the model with forgecad run <file> (or main.forge.js for multi-file projects).
  • Run the Final Acceptance Gate and Manufacturing Outputs checks on main.forge.js.
  • Iterate by converting renders/inspections into targeted model edits and re-running evidence gathering until the model aligns with the intended component graph.

When to use it

Use when you need to create or edit a manufacture-realistic .forge.js model in a ForgeCAD project and subsequently validate it with run, render, inspect, and export evidence.

What it can touch

The skill references tools and scripts like forgecad run, forgecad render, forgecad inspect, forgecad debug assembly, and verify.* checks as part of the workflow. It instructs organizing files under YYYY/MM/DD/ directories and placing parts according to the described file layout, importing parts via require('./parts/name.forge.js', params) where applicable, and using assembly functions such as matchTo() and connect() for mating interfaces.

Caveats

The approach emphasizes producing a manufacture-realistic prototype and requires adherence to collision and verification policies. It relies on a process-first mindset (manufacturing process chosen before styling) and mandates real geometry with internal features, not just conceptual surfaces. It enforces a multi-step validation gate, including the Final Acceptance Gate and dedicated inspection commands. The final model should present zero unexpected collisions unless explicitly declared as intentional in the verification steps.

From the SKILL.md

# Build Model Create new ForgeCAD models in the user's active ForgeCAD project. ## Default Output Standard Unless the user asks otherwise, the output is a **manufacture-realistic prototype**: a model someone could fabricate, buy parts for, assemble, inspect, and iterate in a real shop — not a concept sketch, not a universal 3D-printing exercise, not a claim of certified production readiness. - Include prototype-real features: wall thickness, fastener stacks, bosses, ribs, flanges, seats, gaskets, cable exits, service access, toleranced clearances, believable purchased parts. No invented tooling details, certifications, or safety ratings unless asked. - Modifiers shift the standard: `blockout` → rough massing; `production-realistic` → DFM and production-intent materials; `printable` → make the selected printed parts honest; `visual-CAD` → clearly visual, not pretending build-ready. - Zero unexpected final collisions is part of the definition of done (see Collision Policy). ## File Placement New `.forge.js` files go under date-based directories (today's date) in the user's current ForgeCAD project or a clearly named local folder: ``` YYYY/MM/DD/file.forge.js — single-file model YYYY/

What's inside
Steps it walks through
  1. Default Output Standard
  2. File Placement
  3. Workflow
  4. Process, Style, and Variants
  5. Physical Artifact, Not Teaching Diagram
  6. Kinematics-First for Moving Parts
  7. Mechanical Assembly Contract
  8. Imported Parts (User-Supplied 3D Files)
  9. Collision Policy
  10. Final Acceptance Gate
  11. Manufacturing Outputs
  12. Render and Inspect Cadence
  13. Build Bottom-Up
  14. Scene Presentation
Commands it runs
forgecad run model.forge.js --joint "theta=45"
forgecad render 3d model.forge.js /tmp/theta-45.png --joint "theta=45" --camera iso
More from forgecad-public-kit
All skills →
About this skill
What does the forgecad-build-model skill do?

Build or edit a manufacture-realistic `.forge.js` model in a project, then validate it with run, render, inspect, and export evidence.

How do I install it?

Run `npx skills add ForgeCAD/forgecad-public-kit --skill forgecad-build-model --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From ForgeCAD/forgecad-public-kit, a repository with 915 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going