← All use cases

中文

Building software · GPT

Check a CAD assembly for injection-molding risks with GPT's Codex CLI

Idea + starter prompt, not run by us yet

For: Product and mechanical engineers who check CAD assemblies before molding

The author turned a real structure and molding review into a reusable skill for GPT's Codex CLI. Given a STEP or native assembly and the product configuration table, it uses local CAD to check units, solid bodies, part interference and gaps, plus wall thickness and key cross sections, then flags molding risks. A script also records SHA-256 hashes for every input file.

Steps

  1. Export the assembly as a STEP file and prepare the product configuration table. Work on copies.
  2. Install the skill from the author's GitHub repo and make sure the local CAD tooling it relies on is set up.
  3. Ask for a plan first: which checks it will run and in what order. Then let it run.
  4. Read the report. Each issue lists its location, the measuring method, the recheck result and what closes it.
  5. Re-verify the conclusions. The repo holds none of the original product's data, so don't assume they carry over to a new input.
  6. Remember these are geometry measurements, not mold-flow or physical tests. Supply the material, loads and mold plan yourself.

Starter prompt

Starter prompt. Change the [brackets] first.

Review the assembly in [assembly file copy] for injection-molding risks, using the product configuration table [config table]. Work on copies only and don't change the CAD files. First show me a plan: the units and version you detect, and the list of checks (solid validity, interference, clearances, wall thickness, key sections). Wait for my OK. Then write an editable report where each issue lists its location, how it was measured, the recheck result and what would close it. Also record a SHA-256 hash for every input file. Say clearly which results are geometry only and which mold or trial evidence is still needed. Material is [material], loads are [loads], mold plan is [mold plan]. If any is missing, ask me instead of guessing. Use only a public or synthetic test assembly and configuration table. Do not read confidential designs or send their contents to a model or external service. Keep generated files in the test folder.

Original post: GitHub · found via agentusecases.ai. Written up in our own words. We haven't run it, so test it on made-up data first.