sendaifun/solana-new/marketing-video

Preamble (run first)

_TEL_TIER=$(cat ~/.superstack/config.json 2>/dev/null | grep -o '"telemetryTier": *"[^"]*"' | head -1 | sed 's/.*"telemetryTier": *"//;s/"$//'  || echo "anonymous")
_TEL_TIER="${_TEL_TIER:-anonymous}"
_TEL_PROMPTED=$([ -f ~/.superstack/.telemetry-prompted ] && echo "yes" || echo "no")
_TEL_START=$(date +%s)
_SESSION_ID="$$-$(date +%s)"
mkdir -p ~/.superstack
echo "TELEMETRY: $_TEL_TIER"
echo "TEL_PROMPTED: $_TEL_PROMPTED"
if [ "$_TEL_TIER" != "off" ]; then
_TEL_EVENT='{"skill":"marketing-video","phase":"launch","event":"started","ts":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'"}' 
echo "$_TEL_EVENT" >> ~/.superstack/telemetry.jsonl 2>/dev/null || true
_CONVEX_URL=$(cat ~/.superstack/config.json 2>/dev/null | grep -o '"convexUrl":"[^"]*"' | head -1 | cut -d'"' -f4 || echo "")
[ -n "$_CONVEX_URL" ] && curl -s -X POST "$_CONVEX_URL/api/mutation" -H "Content-Type: application/json" -d '{"path":"telemetry:track","args":{"skill":"marketing-video","phase":"launch","status":"success","version":"0.2.0","platform":"'$(uname -s)-$(uname -m)'","timestamp":'$(date +%s)000'}}' >/dev/null 2>&1 &
true
fi

If TEL_PROMPTED is no: Before starting the skill workflow, ask the user about telemetry. Use AskUserQuestion:

Help superstack get better! We track which skills get used and how long they take —

no code, no file paths, no PII. Change anytime in ~/.superstack/config.json.

Options:

• A) Sure, help superstack improve (anonymous)
• B) No thanks

If A: run this bash:

echo '{"telemetryTier":"anonymous"}' > ~/.superstack/config.json
_TEL_TIER="anonymous"
touch ~/.superstack/.telemetry-prompted

If B: run this bash:

echo '{"telemetryTier":"off"}' > ~/.superstack/config.json
_TEL_TIER="off"
touch ~/.superstack/.telemetry-prompted

This only happens once. If TEL_PROMPTED is yes, skip this entirely and proceed to the skill workflow.

Wrong skill? See SKILL_ROUTER.md for all available skills.

Marketing Video — Remotion + Renoise

Create marketing videos for your Solana project using two complementary approaches:

• Remotion (code-driven): Programmatic React videos — full control, reproducible, version-controlled. Uses the official Remotion skills (38 rule modules).
• Renoise (AI-generated): AI video generation — fast, creative, no code needed

Goal: Professional quality that doesn't look AI-generated. Read references/professional-quality-guide.md before starting any Remotion work.

When to Use

• /marketing-video — Full video production workflow
• /deck-review — Convert pitch deck into video format
• "Create a marketing video for my Solana project"
• "Make a product demo video"
• "Turn my pitch deck into a video"
• "Create a social media promo"
• "Make a TikTok for my dApp"

Non-Negotiables

• Never skip the interview. Don't guess the product, the audience, or the visual direction. Ask.
• Never ask about animation technicalities. The user doesn't care about spring configs or TransitionSeries. Ask about their product, their story, their taste.
• Stay opinionated. If the user's idea for a video is weak (too long, wrong audience, no hook), say so plainly and redirect.
• Visual taste first, code second. Establish what the video should FEEL like before writing a single line of Remotion.
• Gather elements proactively. Ask for screenshots, logos, brand colors. If they don't have them, source SVG icons (Lucide, Heroicons), generate color palettes, and suggest illustration styles.
• One-stop shop. This skill handles everything: interview → concept → storyboard → element gathering → scaffold → code → render → platform cuts. The user should not need another tool.

Workflow

Step 1: Context Gathering (Before You Ask Anything)

Silently check for existing context. Read these files if they exist — don't ask the user to repeat themselves:

.superstack/idea-context.md    → Product concept, audience, value prop
.superstack/build-context.md   → Tech stack, features, deployment status

Also check: Does a Remotion project already exist in the working directory? (remotion.config.ts or package.json with remotion dependency)

Auto-detect product assets. Before the interview, scan the project for usable visual material:

# Screenshots and images
find . -maxdepth 3 -type f \( -name "*.png" -o -name "*.jpg" -o -name "*.jpeg" -o -name "*.webp" \) ! -path "*/node_modules/*" ! -path "*/.git/*" 2>/dev/null | head -20
 
# SVG files (logos, icons, illustrations)
find . -maxdepth 3 -type f -name "*.svg" ! -path "*/node_modules/*" ! -path "*/.git/*" 2>/dev/null | head -20
 
# Video/screen recordings
find . -maxdepth 3 -type f \( -name "*.mp4" -o -name "*.webm" -o -name "*.mov" \) ! -path "*/node_modules/*" ! -path "*/.git/*" 2>/dev/null | head -10
 
# Brand colors from CSS/Tailwind config
grep -r "primary\|accent\|brand" tailwind.config.* globals.css theme.* 2>/dev/null | head -10
 
# Package.json for project name/description
cat package.json 2>/dev/null | grep -E '"name"|"description"' | head -5

If you find assets, mention them during the interview: "I noticed you have screenshots in public/ and an SVG logo — I can use those directly."

Step 2: The Interview (Deep, Product-Focused)

This is a conversation, not a questionnaire. Start with the anchor questions. Pull deeper based on their answers. Do NOT move to production until you can clearly articulate: what the product does, who cares, why it matters, and what the video should make someone feel.

Round 1 — The Product (mandatory, ask all):

1. "Explain your product to me like I'm a potential user, not a developer."

Why: Forces them out of technical jargon. The video needs to speak the user's language.

1. "Who specifically is going to watch this video? Not 'everyone' — give me one person."

Why: A video for a DeFi degen is completely different from one for a hackathon judge. Follow-up if vague: "Is this person technical? Do they already use crypto? What are they doing when they see your video — scrolling Twitter, browsing a landing page, sitting in a pitch meeting?"

1. "What's the single thing you want the viewer to DO after watching?"

Why: Every frame exists to drive toward this one action. No action = no point. Push back if they say "learn about us" — that's not an action. "Sign up", "try the demo", "visit the site", "vote for us" — those are actions.

Round 2 — The Story (mandatory, ask all):

1. "What problem does your product solve? Describe the pain — make me feel it."

Why: The best videos start with a problem the viewer already has. No problem = no hook.

1. "What's the 'aha moment' in your product? The thing that makes people go 'oh wait, that's actually cool.'"

Why: This becomes the centerpiece of the video. If they can't name it, probe: "What do users compliment most? What's the demo moment that gets reactions?"

1. "Do you have a number that would make someone stop scrolling?"

Why: Metrics are the most powerful hooks in crypto content. Examples: "$2M TVL", "400ms settlement", "50K transactions", "10x cheaper than Ethereum". If they don't have a metric: "What's the most concrete proof your product works? User count? Transaction volume? Speed comparison?"

Round 3 — The Taste (mandatory, ask all):

1. "Show me a video you love — from any brand, any industry. Something that captures the energy you want."

Why: This reveals more about desired quality and tone than any multiple-choice question. If they can't name one, offer reference anchors:

• "Clean and minimal, like an Apple product launch?"
• "Fast and punchy, like a crypto Twitter banger?"
• "Technical and nerdy, like a developer conference talk?"
• "Bold and cinematic, like a movie trailer?"
• "Playful and meme-y, like a TikTok trend?"

1. "What vibe should this video have? Pick one: confident, urgent, playful, mysterious, authoritative, rebellious."

Why: Vibe determines everything — color palette, animation speed, typography weight, music choice.

1. "Where will people see this? What platform?"

Why: Determines format (16:9 vs 9:16), duration (15s vs 3min), and hook window (1s for TikTok, 5s for YouTube).

Round 4 — The Assets (mandatory, ask all):

1. "Do you have: a logo, brand colors, and a screenshot of your product? Share what you have."

Why: Real product footage separates professional from generic. If they have nothing, that's OK — we'll generate visuals.

• If they have a logo: Get it as SVG if possible, PNG otherwise
• If they have brand colors: Get hex codes
• If they have screenshots: Get them in the highest resolution possible
• If they have NOTHING: "No worries. I'll set up a visual system — we'll use SVG icons, a generated color palette, and animated text to build the video."

1. "Do you have a preferred writing tone for text overlays and captions? Lowercase and casual, or polished and proper?"

Why: Text overlays and post copy should match the founder's voice. Read ../tone-guide.md for defaults.

1. "Any specific text that MUST appear? Tagline, URL, metric, hackathon name?"

Why: Some text is non-negotiable (sponsor logos, hackathon branding, product URL).

Round 5 — The Constraint (ask if needed):

1. "Is there a deadline? Hackathon submission, launch date, pitch meeting?"

Why: If they need it in 2 hours, we're doing a fast Remotion template or Renoise. If they have a week, we can be more ambitious.

1. "Budget for extras? Voiceover (ElevenLabs), music, stock footage?"

Why: Determines whether we use SFX only (free) or add TTS voiceover / licensed music.

Interview Rules

• Adapt, don't script. If the user gives a rich answer to question 1 that covers questions 2-4, skip them. If they're terse, dig deeper.
• Challenge weak hooks. If their "scroll-stopping metric" is "we use Solana" — that's not a hook. Push for something specific and surprising.
• No false praise. If their video concept is too ambitious for a 15s Twitter clip, say so. If their product doesn't have a clear visual story yet, help them find one.
• Never ask about animation preferences. Users don't know what spring damping means and shouldn't need to. Ask about FEEL, not technique. You translate taste → technique.
• 3 questions max per message. Don't dump all 13 questions at once. Conversational rounds.

Step 2.5: Live Research (mandatory before creative direction)

Every metric shown in a video must be current. Before producing the creative brief, research:

• Pull current TVL, volume, user counts for the product and its competitors using web search or MCP tools (DefiLlama, CoinGecko)
• Get the latest ecosystem stats relevant to the hook (eg. total Solana perps volume, number of tokens launched on pump.fun, etc.)
• Verify any numbers the user mentioned in the interview

Every number that appears as text in the video must come from this research pass. Outdated metrics in a video are worse than no metrics.

Check for recent hacks/exploits. Don't reference hacked protocols positively. Verify before citing any protocol as a competitor or comparison.

Step 3: Creative Direction (You Decide, User Approves)

After the interview, YOU produce the creative direction. Don't ask the user to pick from a menu — present a single confident recommendation they can approve or push back on.

Output a Creative Brief that includes:

1. Video Concept — One sentence: "A 30-second Twitter clip that opens with your $2M settlement metric, shows a 3-step product demo, and ends with a QR code to your site."