Print-Ready Agent Workflows
How agents check a file, make a verified production file at a physical size, and keep logos and products exact.
Check first, then make the production file
designgen_print_prep has three entry points. Pick by what the user needs.
- preflight (free): DPI at the print size, transparency, color count, edge halos, thin lines. Run it on every customer file before production and show the user the summary.
- print_file: the production path. A verified SVG plus a transparent 600-DPI PNG at targetWidthIn (max 24 in), made by an Operator run. Poll designgen_operator operation get by replaying nextCall, then fetch production_package.
- prepare: a quick cleanup (background removal, upscale, vectorize via flags) when no physical size is involved. It does not verify a print size.
Use reference files deliberately
For apparel and logo fidelity, pass each important reference as a separate reference image with role metadata.
- Use role=logo for exact customer logo assets.
- Use role=product for garment or product photos that should drive color and shape accuracy.
- Use role=style or role=layout for inspiration that should not override logos or product references.
Never overclaim
A production_package with ready: true passed mechanical checks; the artwork still needs a human look.
- If production_package returns needs_review, show its warnings and do not call the files print-ready.
- Use Ultra Max and high thinking budget when small details, logo fidelity, or final customer-facing artwork matter.