Polymend

View saved version →

---
name: images-to-print
description: Turn pictures of a character or object into a physical 3D print. Use when the user wants a printable model made from reference images with a 3D generation tool they have connected (such as an image-to-3D plugin, or its command line) and then print files: it covers choosing the references, the cost question, checking the generated model, and handing it to the print-ready skill for repair, sizing, STL and 3MF, and a review.
---

# From pictures to a print

Use this with whatever 3D generation tool the user has connected. Polymend does not generate models; it reviews the generated model and makes it printable. Follow the generation tool's own instructions for its exact parameters; the points below are what decide whether the result prints well.

## 1. Before generating

- **Print height** in millimeters (optional): ask once, alongside the other questions, and say it can be skipped. If skipped, the print files keep the model's own size and the user scales them in the slicer. Never make one up, and never hold up generation waiting for it.
- **References**: separate, sharp pictures of the same subject in one consistent pose, ideally front, side and back, one subject per picture, no contact sheets or tiny thumbnails. Point out contradictions between the views before anything is spent: when the front shows the arms spread and the side shows them reaching forward, models made from them often follow the side view. If there is no side view, mention once that the depth front to back will be the generator's estimate, and that a side picture would pin it down; then carry on unless the user wants to add one.
- **How many pictures the tool takes**: check the generation tool's own limits before choosing. A common image-to-3D setting takes at most **four shape pictures** and **one texture picture** (a texture prompt, if given, is used instead of the texture picture). Tell the user the limit plainly, as a fact about the tool, so they know what to expect.
- **More pictures than the tool takes** (for example ten): never drop pictures silently or pick without saying so. Say how many the tool takes, recommend a set and why, and let the user choose or accept the recommendation before anything is spent. A good default: front, side and back, plus one more chosen for what matters most:
  - a sharp close-up of the detail that matters most (usually the face), for finer detail there; in tested runs it gave separate teeth and a raised iris that three views alone did not; or
  - a three-quarter rear view, when a feature shows only from behind (a tail, a cape, a backpack); if such a feature appears in only one or two of the four pictures it may come out stunted or missing.
  **Exactly as many pictures as the tool takes counts too**: if one of them is a close-up and a feature seen mainly from behind (a tail, a cape) shows in only one or two of the pictures, name that feature and the risk, and ask whether to swap the close-up for a three-quarter rear view before anything is spent.
  Say the trade-off when it applies: in a tested pair of runs of the same figure, a face close-up as the fourth picture gave a crisper face but the tail came out as a stub; without the close-up the tail came back (hanging straight down rather than as posed) and the face was a little softer.
- **Texture: a picture or a prompt, not both.** The tool takes one texture picture, or a short texture prompt; if both are given, the prompt is used. They behave differently, so choose with the user's goal:
  - a **texture picture** (a sharp close-up of the surface: skin, scales, stone), with no prompt: in tested runs it carried grain and scales into the model's surface, for fine prints; the same close-up can also be the fourth shape picture;
  - a **texture prompt**, short and about material and finish (colors do not matter for a single-color print): smoother surfaces with crisper features, for quick prints or larger nozzles.
- **Symmetry**: if the tool has a

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 3 — file references are metadata, not package contents.

View saved version →

---
name: print-ready
description: Prepare GLB or STL 3D models for physical 3D printing with Polymend. Use when the user wants a 3D model (a local .glb or .stl file, or an https link to one, such as a model a 3D generation tool just made) repaired, sized and exported for a 3D printer or slicer: it fixes the mesh faults slicers warn about, sets the print height if one is given, writes an STL and a 3MF, draws the model from four sides with every change marked, and reviews what came out well and what did not. Not for printing documents or photos, and not for other 3D formats (OBJ, FBX, STEP).
---

# Print-ready models with Polymend

Polymend reviews a 3D model, fixes the small faults that make a slicer complain (stray triangles stuck to the surface, pinholes, triangles facing the wrong way, split seams), stands it on the bed at the height asked for, and writes an STL and a 3MF. It is conservative: it never moves an existing point of the model except to join seam points a hair apart, and it leaves anything larger alone and says so. It checks that the mesh is sound; it does not measure wall thickness or the smallest printable detail, so a clean result still deserves a look in the slicer's preview.

Do not use it for editing a model's shape, hollowing, adding supports, or slicing; say Polymend does not do that.

## Before running

1. **Inputs**: local `.glb` / `.stl` paths, folders, or https links to `.glb` / `.stl` files (a link a 3D generation tool returned can be passed as it is). Up to 20 models per run. Polymend never changes its inputs.
2. **Print height** (optional): if the user has not given one, ask once, in the same message as any other question, and say they can skip it to size the model themselves in the slicer. Never make up a height. If they give one, use `--height <mm>`. If they skip it, leave it blank, or say they will size it themselves, run without `--height`: the files keep their own size (a GLB's meters become millimeters). Do not ask again; tell them the size it came out at, and that most slicers can scale it on import.
3. **Node**: run `node --version` once; Node 20 or later is needed. If it is missing, say this plugin runs in the ChatGPT desktop app or Codex on a computer with Node.js 20+, and that https://polymend.xyz does the same repair in a browser, on the user's own device. Do not install anything without the user's go-ahead.

## Run

The scripts are in this skill's folder (the folder that contains this SKILL.md). Call them by their full path and quote every path:

```sh
node "<skill folder>/scripts/prepare.mjs" "<file, folder or link>" ... [--height <mm>]
```

- For a link, or a file with a long machine-made name, add `--name "<short name>"` (for example `--name "crocodile warrior"`) so the files and the review read well; one model per run when naming.
- Each run writes into its own new folder, `./polymend/<date>-<time>-<model>/` under the current working folder (or `--out "<folder>"` if the user names one). Tell the user the full path printed after "Files are in". If the current folder is a code project, mention that the files are in its `polymend/` folder and should not be committed.
- The command exits with code 0 whenever it ran; each model's outcome is in the results. Read the printed summary, or add `--json` and read the last line.
- **If a download fails** with a network error (no address, connection refused, timed out), the environment may not allow downloads. Ask the user to download the file and give its path, or use the local file the generation tool saved, if there is one. Links to local or private network addresses are refused on purpose.
- Polymend uploads nothing; its only network use is downloading the links given.

Per model it writes `<name>-mended.stl`, `<name>-mended.3mf`, `<name>-report.json`, `<name>-result.png` and `<name>-views.png`; per run `polymend-batch.json` and `polymend-review.md`. Downloaded links are kept in the run folder's `sources/`.

## Review, then report

Polymend'

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 19 — file references are metadata, not package contents.