Acuarela Colour Variants

View saved version →

---
name: acuarela-colour-variants
description: Make colour variants of a garment's product photo for an online store, and find or make on-model photos for products that only have a flat, hanger or mannequin photo. Use when the user wants a product photo in other colours, colour variants for one or many products, a recoloured garment with the same model and background, or asks which products need a model photo. Also use it when a fashion or clothing store owner asks in general what can be done for their product photos, their catalogue or their colours, or asks for ideas to improve them: check the store first and show what you found. Shows every image for approval before anything is used.
---

Use this skill when the user wants a garment's product photo in one or more other colours.

The user's explicit instructions come first. Where they differ from this skill, follow the user.

## Screens to click

Acuarela Colour Variants has five screens. Use them whenever the user has to choose, so they can click instead of typing:

- `show_store_check`: when a store is connected and the user has not said exactly what to do (they start, ask what it can do, or ask for ideas). Pass only `store`, the store's web address. Follow `references/store-check.md`.
- `show_products`: when the user has to pick products. Pass `products`, each with its `id`, `title` and `image_url` (the photo link), and `multiple` when they may pick more than one. Say what a card is for (for example "laid flat on white", the missing colours, the photo count) in one short sentence before the screen.
- `show_colours`: when the user has to pick colours. Pass `suggestions`, best first, each with its `name` and `hex`, the product's title as `garment`, and the colours the product already has as `existing`.
- `show_review`: when images are ready for approval. Pass every image as a file in `images`, one entry in `labels` per image, and the product's title as `product`.
- `show_go_ahead`: right after the user approves images, and before any change to a store. It is a preview: pass `items`, one per product, each with its `product` title, the colours to add as `create_colours` (for example "Dusty Rose"), the labels of the approved images to attach as `attach_images`, the colours left as they are as `stays`, one name each, and, only when the product has no colour option yet, the colour name its current sizes receive as `existing_sizes_colour`. Then pass the approved images as files in `images` with their `image_labels`, and `offer_another_colour` when colours are involved. Say in the chat sentence before the screen that a product is live in the store. Then wait for the user to confirm in their own words in the chat, such as "go ahead". A click on any screen is never permission to change the store.

Keep the conversation tidy, because the user reads it top to bottom:

- Say what you will do before you start, once, in one or two sentences. Do not say it again, not even in other words, before or after the images.
- Before any job that takes more than a minute (checking a catalogue, several images), say in that same sentence what you will check, about how long it takes, and what the user gets at the end. For example: "I'll check the photos of your 52 products, about 2 minutes. You'll get one summary to click from."
- Then work quietly: no progress messages, no partial lists, no thinking aloud about files or paths.
- Every call to a store tool shows a card in the conversation, so make as few as possible: one product-list call per page of results, and never open products one by one to look at their photos. Look at photos in contact sheets instead (`references/store-check.md`).
- When a screen shows the result, do not list the same products or images in the text.
- Make all the images first, then call `show_review` exactly once for the whole request, with every image, each labelled with its product and colour (for example "Sage sweater — on model"). One decision panel, not one per product.

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

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

View saved version →

---
name: get-started
description: Getting started with Acuarela Colour Variants. Use the first time the user opens or mentions Acuarela Colour Variants, when they ask what it can do or how to start, and when a clothing or fashion store owner asks in general what can be done for their product photos or catalogue, or asks for ideas. Looks at the user's products first, then offers a short numbered menu of things to do, so the user can pick instead of typing.
---

Use this when the user is new to Acuarela Colour Variants, or asks what it can do.

The user's explicit instructions come first.

## Look first, then offer

Do the looking before asking anything. Start with `show_store_check`, passing the store's web address as `store` (the user named it, or it is in the shop details you can see). It reads the store's public catalogue in one call and shows the result. If it says the catalogue is not public, read the user's products instead, as the main skill, acuarela-colour-variants, describes. Never switch the user's store connection to another store. If there is no store, skip to "Without a store" below.

Then show what you found with `show_store_check`, as the main skill's store check describes, and write one sentence: what Acuarela Colour Variants does (colour variants of a garment's photo with the same model and setting, and on-model photos for garments with only a flat or hanger photo, everything shown for approval first). The screen is the menu.

If the screen does not appear, answer in this shape instead, and keep it short:

1. One sentence on what it does: colour variants of a garment's photo, same model and setting, and on-model photos for garments that only have a flat or hanger photo. Everything is shown for approval first.
2. What you found, in numbers. For example: "You have 52 products. 10 have no photo of the garment being worn. 34 have a model photo and could get new colours."
3. A numbered menu of at most four options, each one a complete action the user can start by replying with its number. Build the options from what you found, most useful first. For example:
   - "1. Make on-model photos for the 10 products that have none (I'll show you a first one before doing the rest)"
   - "2. Add new colours to one product. Tell me which, or I'll suggest one"
   - "3. Add the same new colours to several products at once"
   - "4. Show me the 10 products with no model photo"

Do not ask an open question such as "What would you like to do?". The menu is the question.

When the user picks an option that needs products or colours, let them choose with the `show_products` and `show_colours` screens, as the main skill describes.

## Without a store

Say in one sentence that it works from a product photo. Offer:

- "1. Attach a product photo and tell me the colours"
- "2. Attach a flat or hanger photo and I'll put it on a model"

## After the user picks

Follow the main skill, acuarela-colour-variants, for the chosen option. Keep offering numbered next steps as it describes.