Randmar / Prompts

Create a musical cartoon ad for your Shopify store

Turn a product, collection or blog post into a musical cartoon story with your AI agent. Bring your subject and a required storytelling or ideal customer profile document.

← All prompts

Use this page’s URL as your conversation objective, or copy the objective below. Your agent can read the full instructions on this page or the plain-text agent version.

Start the conversation

Help me create a musical cartoon ad for my Shopify store.
Read and follow this Randmar prompt: https://randmar.io/prompts/musical-cartoon-ads
Start by reading my subject and my storytelling or ideal customer profile document.

Instructions for AI agents

# Objective: Create a musical cartoon ad for my Shopify store

Act as my creative and production guide. Help me turn one Shopify product, category, collection or blog post into a musical cartoon ad shaped by my storytelling or ideal customer profile (ICP) document. Carry the work through production and review in my configured AI environment when the required tools and access are available.

This prompt is adapted from the Randmar Musical Ads Developer Handoff v1.0, dated 16 October 2026. It is not the released starter prompt or complete student SOP. Do not claim to have read, downloaded or validated the approved student kit, SOP or accepted example unless I actually supply them. If I provide the kit, extract and read it before production, preserve its accepted workflow and use its documented tools rather than reconstructing an older singing-character workflow.

## 1. Read both required inputs

Before personalized creative production, obtain and read:
- One subject: a Shopify product, category, collection or blog post, provided as a URL or readable source content.
- At least one storytelling or ideal customer profile document. Read both if I supply both.

If either input is missing or inaccessible, ask for the missing document or readable content before writing personalized concepts, lyrics or scenes. Do not substitute a guessed audience for my customer document.

Also collect my store name and URL, campaign language, desired viewer action, exact CTA destination and available production account. Ask for official product images, a logo and useful brand guidance. Resolve missing details with focused questions; reuse information I already supplied. Keep documents and production files in my chosen AI environment, not on the Randmar prompt page. Never ask me to paste private credentials into chat.

## 2. Verify facts, tools and production access

Use my supplied customer documents and brand guidance for audience, situation and voice. Verify product facts against my readable source material and official product assets. Preserve authentic product appearance and packaging. Do not invent claims, prices, promotions, testimonials or customer outcomes. Flag conflicting or unverified facts before using them.

Use ChatGPT with the necessary coding and connected tools, or a configured Codex or Claude Code environment. Verify Python and FFmpeg for editing, authorized video-generation access, and an original or licensed song or a compatible music setup. Check the current tool schemas, available account access, intended partner account, generation charges, budget and local model requirements before producing the full ad. Do not assume a particular endpoint, model, clip duration or subscription is available. Explain missing capabilities and continue only with supported work.

Randmar setup references:
- ChatGPT and Codex: https://randmar.io/codex
- Randmar MCP setup for Claude: https://randmar.io/claude-code
The Claude reference describes a desktop connector; verify a genuine Claude Code CLI setup path before treating it as CLI instructions.

The workflow does not require a new creative subscription, but metered generation charges and local setup may still apply. Obtain my authorization for the concrete paid production scope unless I already authorized it. Do not buy subscriptions, publish an ad or change my store without explicit instructions.

## 3. Shape the customer story

Identify one customer situation grounded in my documents. Connect the customer's problem, desired outcome and objection to my brand voice and verified subject facts. Develop a focused creative brief, lyrics and visible story actions. Make the product's role understandable without unsupported promises. Confirm the desired viewer action and exact destination for the separate final CTA.

## 4. Lock the song before the picture edit

Use a suitable original or licensed song, or create an original take with my available music setup. Verify usage rights and language fit. Let me review the song before planning the picture edit. Do not use an example campaign's song, event date, venue, character or CTA as defaults for my campaign.

## 5. Test the visual direction

Create a consistent character reference and a representative short scene. When the direction is new, gather my feedback and apply it before the full build. Keep character design, product appearance and visual continuity consistent across clips.

The song plays off-screen. Characters perform varied, natural, task-focused story actions with little or no visible singing. Do not turn the workflow into a sequence of singing or lip-syncing characters.

## 6. Generate and assemble

Generate story clips using the verified tools and approved direction. Remove the clips' sound and assemble them with the approved song using Python and FFmpeg or the supplied kit's supported assembler. Follow the song's timing and keep the visible story coherent.

Use exactly one lyric-caption layer. Each lyric appears once; do not repeat it as a top headline. A small brand label is fine. Keep a separate, readable final CTA card with the agreed action and exact destination. Check text legibility, caption timing, safe placement and product accuracy throughout.

If presenting an accepted example that already has embedded lyric captions, do not add an HTML lyric overlay or enable a second external caption layer by default. Provide a readable transcript alongside it.

## 7. Review and deliver the complete ad

Review the full assembled ad, not only isolated clips. Check:
- The story reflects my subject and required customer document.
- Product facts, appearance, packaging and branding are accurate.
- The approved song is synchronized and its usage rights are suitable.
- Characters act naturally, with little or no visible singing.
- There is one readable, correctly timed lyric-caption layer without duplicated lyric headlines.
- The separate final CTA is readable and uses my exact destination.
- The exported video plays correctly and the complete edit has been reviewed.

Revise against my feedback and keep the accepted project, source assets, lyrics, transcript, production scripts and reproducible assembly instructions. Report what was verified, what remains blocked and where the deliverables are saved. Do not claim that an export, kit validation, video review or publication succeeded without actual evidence. If production is unavailable, provide the completed brief and production-ready materials, clearly identify the missing capability, and state the next concrete step.

Updated . Adapted from the Randmar Musical Ads Developer Handoff v1.0.