← LoovaCONTENT HISTORY

Update to Loova

Snapshot Nov 5, 2026 · 06:11 UTC · version 2.1.4

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Loova and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Create studio, lifestyle, or campaign images for a specific product using Loova. Use for new product photography from product references or a concept brief; use an editing or listing workflow for local retouching or a product listing set.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 287
    },
    {
      "relative_path": "references/execution.md",
      "size_in_bytes": 14081
    }
  ],
  "name": "loova-product-photoshoot",
  "skill_md_contents": "---\nname: loova-product-photoshoot\ndescription: \"Create studio, lifestyle, or campaign images for a specific product using Loova. Use for new product photography from product references or a concept brief; use an editing or listing workflow for local retouching or a product listing set.\"\nmetadata:\n  version: \"2.1.4\"\n  brand: \"Loova\"\n  category: \"image-creation\"\n---\n\n# Product Photoshoot\n\nCreate product images with consistent identity, credible materials, and intentional photography. Deliver images, a plan, or prompts according to the user's request.\n\n## Inputs and defaults\n\nUse real product references when available. Extract visible silhouette, proportions, color, structure, materials, logo, and packaging copy. With text alone, create a concept product and identify it as such. Reuse context rather than asking for information already supplied. For an unspecified single image, use one square image as a working default if the selected model supports it.\n\nChoose studio for a clean product presentation, lifestyle for a believable use setting, or campaign for a specific brand message with deliberate copy space. A request to change only an existing background belongs to image editing. A multi-module shopping page belongs to listing images; those skills need not be installed to explain the distinction.\n\n## Workflow\n\n1. Lock visible product features. Separate permissible changes in photography from unknown rear surfaces, accessories, and functions. Do not invent concealed product details.\n2. Define the relationship between product, camera height, viewing angle, framing, key light, fill, background distance, and supporting surface. Use controlled broad reflections for reflective materials; consider transmission and edge light for transparent objects.\n3. For studio work, prioritize silhouette and material. For lifestyle work, choose a plausible use moment before adding props. For campaign work, establish the message and copy area before arranging the product. Do not add splashes, levitation, or people by default.\n4. Treat the product reference as identity and any scene reference as environment or style. Read [Loova execution](references/execution.md) before creating media and translate the intent into supported tool fields.\n5. For a set, keep product identity and lighting logic consistent. Change the requested scene or camera variables without introducing unnecessary variants.\n\n## Request brief\n\nInclude only relevant fields: intended use and aspect ratio; product reference and locked features; studio/lifestyle/campaign mode; orientation and framing; light and supporting surface; purposeful props; copy space; permitted changes.\n\n## Quality and delivery\n\nCheck caps, buttons, ports, proportions, packaging, and logo. Do not mark unreadable text as verified. Look for floating products, inconsistent reflections, plastic-looking metal or glass, and depth of field hiding essential details. Confirm realistic product scale and contact with hands or surfaces.\n\nRepair identity problems through the product constraints, material problems through lighting and reflection, and unclear compositions by simplifying props. Prefer a viable local repair over regenerating a successful composition. Deliver the requested count with recognizable filenames and a brief result description; include prompts or production notes only when useful or requested.\n"
}

SHA-256 of public snapshot: 0beb6f7dca88452bca6bd1d4821610761c1e1fa6c8ccd3869956fa19610c9b7a