← FrameoCONTENT HISTORY

Update to Frameo

Snapshot Oct 8, 2026 · 18:02 UTC · version 1.2.1

Collection source: downloaded plugin package.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Packshots on several backgrounds or scenes, lifestyle shots, hero banners and carousel sets from a few product photos.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 372
    },
    {
      "relative_path": "assets/icon.svg",
      "size_in_bytes": 345
    }
  ],
  "name": "product-photoshoot",
  "skill_md_contents": "---\nname: product-photoshoot\ndescription: \"Packshots on several backgrounds or scenes, lifestyle shots, hero banners and carousel sets from a few product photos.\"\n---\n\nNeeds: 2–5 product photos on any background; the brand's look in a sentence; which set they need\nCredits: about 180 for a 10-image set (images ~18 each), plus a retake allowance of 15%\nTime: 10–20 minutes\n\n## When\n\nE-commerce and ads: a clean packshot set, lifestyle scenes, a hero banner, a carousel, a\nrestyle of an old shot. Not for video (`ugc-product-video`) or a moving spin\n(`product-spin`).\n\n## Ask first\n\n1. **Photos** — 2–5, through `show_upload` from the user's device or `import_media_url` from web links (images attached to the chat do not reach Frameo, and `create_upload_url` is for clients that send the file themselves); the more angles the better.\n2. **Set** — packshots / lifestyle / hero / carousel / restyle, and how many.\n3. **Look** — the brand in a sentence, a reference image if they have one, aspect ratio.\n\nSay the rough cost in the same turn as the questions; the user's yes comes with the plan (Steps, **The plan first.**).\n\n## Steps\n\n**Before any paid step.** The project: `list_projects` (or `create_project`) gives the `project_id`\nand, when the project has several modules, the `module_id`; every call below that takes a project —\n`estimate_cost` included — gets that same pair; without it those tools answer `project_needed`. The\nquote: one `estimate_cost(items=[…])` prices a stage in one call, with the same project, model,\nsize and number of `image_urls` or `reference_image_urls` (`reference_count`) as each generate call, and returns a `quote_id` per item plus the total. Each generate call\nthen passes its own item's `quote_id` and `confirmed_by_user=true`. A quote is single-use and lasts\n15 minutes, so a long plan is priced stage by stage, right before each stage runs; a stage that\ncomes to more than the user approved is asked about again first. Generate calls return\n`generation_ids`; `wait_task` returns the links, and `show_generations` shows each stage's running\nand finished work in one card where the chat app displays Frameo cards: all the stage's ids at\nonce, before its first `wait_task`, and the finished result with `final: true`.\n\n**The plan first.** Before the first paid call, the plan goes to the user in the chat as plain\ntext: what will be made, in order, one line per generation (for a script, the shot list; for a\nset, each shot), with each line's credits and the total. The credits come from\n`estimate_cost(items=[…])`, up to 10 items a call, so a long plan takes several calls; those\nquotes may expire unused, since each stage is quoted again right before it runs. Nothing is\ngenerated until the user says yes. The user can drop or change lines; a changed line is priced\nagain.\n\n**Review (on by default).** Every image is checked before the set is handed over, following\n`review-shots`: its checklist and steps come from `get_skill(\"review-shots\")`, loaded before\nstep 1, and the checks here are its steps 0, 1 and 4. Each preview is compared with the product\nphotos — the label, its lettering, the shape and the colour — and with the shot's pattern,\nincluding whole hands in an in-hand shot; a failed shot is retaken once. The checks are free; a\nretake is paid like the shot it replaces, from the retake allowance the plan carries as its own\nline for the user to approve. The user can turn the review off.\n\n**1. One test (~18).** `generate_image` with `image_urls=[product photos…]` (the cleanest first\n— it is the base) and a prompt for the first shot in the set; `image_model` from\n`list_models(kind=\"image\")` if the user names one. `wait_task`, show it; fix the product's\nfidelity before the batch (more photos, a tighter prompt).\n\n**2. The set (~18 each).** One `generate_image` per shot, each with its own quote, same\n`image_urls`, prompts from the recipe patterns (`hero-shot`, `flatlay`, `in-hand`, `on-desk`, `minimalist-white`,\n`luxury`, `kitchen-scene`, `angles-set`) — `get_skill` on any of them for the pattern. Then review the set.\n\n**3. Size.** There is no image upscale; for print or large use, ask for `image_resolution`\nat generation (and `image_model` from `list_models(kind=\"image\")`).\n\n**4. Deliver.** The links, the review note per shot, and `open_in_frameo` — every image is on\nthe canvas in one row.\n\n## Done\n\nThe image set in the Frameo project.\n`open_in_frameo` on the result opens the project in the Frameo app, where every take sits on\nthe canvas, ready for retakes and edits.\n\n## Files\n\nNone.\n"
}

SHA-256 of public snapshot: d09398257c67db319be6a194586eed06dda06a6937c0446c0108697a19ac300b