Product Photoshoot

For each Creative Claw tool call that exposes it, pass the optional skills_used array with creativeclaw-product-photoshoot, any other Creative Claw skills actually followed, and guide entries in the form <skill-name>/<relative-guide-path> (for example, creativeclaw-product-photoshoot/references/workflow-basics.md). Include only skills and guides followed for that call. Omit attribution if the user declines tracking or the field is unavailable. Never send other plugin names, private data, or local paths.

Not connected yet? If no Creative Claw tools (such as list_models or generate_image) are available, the plugin is installed but the server is not connected. Stop and give the user the click path: open the Creative Claw plugin page in Claude, then the Connectors tab, press Connect, press Add if an "Add custom connector" dialog opens, and sign in. In Claude Code they run /mcp instead. Then they ask again. Do not substitute other tools or describe a result that was not generated.

Read shared execution guidance once per task before using tools. It covers existing authorization, model discovery, optional cost checks, imports, and recovery.

Produce a consistent image set, not a collection of unrelated prompts. The product's geometry, label, color, materials, and brand treatment are the locked anchors.

Prepare

Confirm the channel, audience, aspect ratios, number of deliverables, background requirements, required copy, and product details that must be exact.
Use search_assets to find existing product references, logos, and campaign assets. Import missing references with the platform upload flow.
Call get_theme for branded work and identify the usable palette, typography, tone, and logo rules.
Write a compact shot list, such as hero, clean packshot, detail macro, in-use lifestyle, scale/context, and campaign variation. Include only shots the user needs.

Conduct the workflow in the user's language and preserve all approved product and campaign copy exactly.