Update to Artboard Mockups

{
  "description": "Place the user's original attached logo or design on one or several real editable product mockups. Use for \"put this logo on a shirt\", \"create a T-shirt mockup with my logo\", or branding apparel, packaging and products, even without naming Artboard. Supports comparisons when requested; use the editor rather than generating a replacement image.",
  "included_files": [],
  "name": "logo-on-mockups",
  "skill_md_contents": "---\nname: logo-on-mockups\ndescription: Place the user's original attached logo or design on one or several real editable product mockups. Use for \"put this logo on a shirt\", \"create a T-shirt mockup with my logo\", or branding apparel, packaging and products, even without naming Artboard. Supports comparisons when requested; use the editor rather than generating a replacement image.\n---\n\n# Logo on mockups\n\nFor one product, create or use one editable Artboard project and place the original\nartwork on its print surface. Do not ask the user to request Artboard explicitly\nwhen its tools are already available. Do not generate an image as a substitute.\nUse the comparison workflow below only when the user requests several products\nor variants; a single T-shirt request does not authorize three or four projects.\n\n1. **Choose.** Search with `search_mockups` and show the options visually with\n   `open_artboard` (`view: \"mockups\"` and the same search). Agree on which ones and how\n   many: each mockup becomes a project in the user's account. Create only the\n   requested number of projects.\n2. **Upload once, reuse after.** For the first mockup, place the attached file with\n   `set_project_image` (`image`). Then call `list_my_files` and use its `file_id` for every\n   other mockup. Reused files never count as uploads.\n3. **For each mockup**, in turn:\n   1. `open_mockup`.\n   2. `get_open_project`, to find the artwork surface (`mockup-1/surface-N`).\n   3. `set_project_image` on that surface with the `file_id`.\n   4. Apply the same color, background and aspect ratio choices to every mockup, so the\n      comparison is fair.\n   5. `export_project` (`png`).\n\n   Finish each mockup before opening the next one: edits go to the most recently opened\n   view.\n4. **Present** the download links with the mockup names, and say which one you would\n   pick and why.\n\n## Artwork is an editor operation\n\"Put this logo on the shirt\" means use the actual selected Artboard project and `set_project_image`, not image generation. Resolve the print area from live project context; distinguish artwork targets from product-color surfaces. Adjust logo size/rotation/position using `style_project_surface` and the current transform, preserving aspect. Recolor the product separately. To add another product to the same composition use `add_mockup_to_project` and arrange it through `update_canvas_layer`; avoid creating unnecessary projects. User-facing replies should describe results, not tool names.\n\n\nNative edits now return real rendered visual feedback. Inspect it before claiming\nsuccess; `inspect_project` captures a read-only frame without an export allowance.\nUse a new `begin_project_edit` group for a multi-tool user request, and pass its\n`history_group` so one undo restores that request. All three editors support\nrecorded native undo/redo across reopening. Exports have a persistent Download control for the original rendered file. Existing artwork placement remains a real editor\noperation; native AI generation is for explicitly requested creative assets only.\n"
}