DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to catch print problems before the printer runs with Nurb

Run Nurb's printability rules on a part to find overhangs, thin walls, and floating islands early.

Who it is forA maker or developer who wants to avoid failed prints and checks each part before sending it to the printer.

The problemFailed prints waste filament and time, and many problems such as thin walls are hard to spot by eye in a model.

The outcomeA list of findings with coordinates that point to the exact faces where each rule fired.

What you need first

  • An AI subscription you already pay for, such as one that works with your agent or terminal
  • A Mac (the app is provided for Apple silicon and Intel) or a terminal with uv or pip available
  • A 3D printer and a slicer such as OrcaSlicer or Bambu Studio, if you want print time and filament estimates

Steps

  1. Install Nurb with uv tool install nurb or pip install nurb.
  2. Run nurb check to run the printability rules on the project's parts.
  3. Run nurb inspect to see faces, normals, concave edges, and each finding on its face.
  4. Fix the design in the part file or card, then run nurb check again.
  5. Add nurb check --strict to your CI so findings fail the build. (inferred, check the README)

Prompt for your agent

Using the nurb repo (Shpigford/nurb), run the printability checks on the part <target part name> in this project. Expected output: a list of findings such as overhang or min_wall with coordinates. Verify by running `nurb inspect` and confirming each finding appears on a face.

Caveat. The README warns that min_wall samples faces, so a clean result means no thin walls were found, not that none exist.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page