Communitygithub.com

evgenspm/launchfilm

Brand intake for a launch film, product video or promo: capture the product's real colors, fonts, logo, radius and theme from the user's repo (Tailwind config, CSS variables, shadcn tokens, next/font, logo SVG), then the live website, then screenshots, and write films/<slug>/brand.json with a source for every value. Use when starting a new film, when the brand, logo or colors changed, or when the user says "use my brand / my colors / my logo". Hard stop if capture fails: never invent a logo or colors. Not for picking a look or grade (scene-build, craft/06) or for writing copy (story).

What is launchfilm?

launchfilm is a Claude Code agent skill that brand intake for a launch film, product video or promo: capture the product's real colors, fonts, logo, radius and theme from the user's repo (Tailwind config, CSS variables, shadcn tokens, next/font, logo SVG), then the live website, then screenshots, and write films/<slug>/brand.json with a source for every value. Use when starting a new film, when the brand, logo or colors changed, or when the user says "use my brand / my colors / my logo". Hard stop if capture fails: never invent a logo or colors. Not for picking a look or grade (scene-build, craft/06) or for writing copy (story).

Works with~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/evgenspm/launchfilm/tree/HEAD/skills/brand-intake
View original→Browse all skills

Ask in your favorite AI

Open a new chat with this agent skill pre-loaded.

OpenAIChatGPTClaudeClaudeGeminiGeminiGrokGrokPerplexityPerplexityDeepSeekDeepSeek

Documentation

name: brand-intake description: Brand intake for a launch film, product video or promo: capture the product's real colors, fonts, logo, radius and theme from the user's repo (Tailwind config, CSS variables, shadcn tokens, next/font, logo SVG), then the live website, then screenshots, and write films//brand.json with a source for every value. Use when starting a new film, when the brand, logo or colors changed, or when the user says "use my brand / my colors / my logo". Hard stop if capture fails: never invent a logo or colors. Not for picking a look or grade (scene-build, craft/06) or for writing copy (story).

brand-intake: real tokens in, brand.json out

The film must look like the product, so tokens come from the product, never from taste. Order of sources, stop at the first that yields a value for a field, and record where each value came from:

  1. The user's repo (best: exact tokens, real font names, the real logo file).
  2. The live URL (computed styles, meta tags, header SVG).
  3. Screenshots the user provides (pixel sampling).
  4. Ask the user for anything still missing. Never guess.

Output (paths relative to launch-video/): films/<slug>/brand.json, films/<slug>/BRAND-SOURCES.md, and logo files copied as-is to public/films/<slug>/brand/ (so scenes load them with staticFile()). Extraction recipes: references/sources.md. Field mapping, font fallbacks, contrast math: references/brand-json.md.

Steps

  1. Find the product root. If launch-video/ sits inside a product repo, the repo root is one level up. Else ask for the URL and screenshots. Note the stack: package.json deps (tailwindcss version, next, @fontsource/*, shadcn).
  2. Colors from the repo. In order: Tailwind v4 @theme vars in CSS, Tailwind v3 tailwind.config.{js,ts,cjs,mjs} theme.extend.colors, shadcn tokens in globals.css (--background, --foreground, --primary, --muted, --card, --accent), other :root custom properties. Convert HSL/OKLCH/RGB to 6-digit hex. Use the theme the marketing site uses (dark or light), not both mixed.
  3. Fonts from the repo. next/font/google or next/font/local imports, @fontsource* deps, @font-face, font-family on body/html/h1, Tailwind fontFamily. Record the family names and weights actually used.
  4. Logo from the repo. Look for SVG first: public/logo*.svg, public/*mark*.svg, app/icon.svg, public/favicon.svg, src/assets/*logo*, src/components/*Logo* (inline JSX SVG: extract the <svg>), then PNG ≥ 512 px (apple-touch-icon.png is 180 px: last resort for a mark, never for a wordmark). Copy to public/films/<slug>/brand/ unmodified.
  5. Radius and theme. --radius or Tailwind borderRadius; theme = dark if bg relative luminance < 0.2.
  6. Fill gaps from the live URL (references/sources.md § live URL): theme-color meta, og:image, link rel=icon, header inline SVG, computed styles of body, primary button, h1.
  7. Fill gaps from screenshots: sample pixels at named points (page background, body text, primary button, card). Write the pixel coordinates in BRAND-SOURCES.md.
  8. Name, tagline, URL: from package.json name/description, the site <title>, hero h1, og:description, README first line. Use the user's own words; never write a new tagline here (story does copy).
  9. Map fonts you cannot ship or load to a shipped OFL font by role (brand-json.md § fonts) and say so.
  10. Contrast check (brand-json.md § contrast): fg on bg ≥ 4.5:1 required (target 7:1), accent on bg ≥ 3:1. Write the numbers. Failing accent → keep it for shapes, pick fg for text on it.
  11. Write brand.json, then validate if schemas/brand.schema.json exists: npx -y -p ajv-cli@5 -p ajv-formats ajv validate --spec=draft2020 -c ajv-formats -s schemas/brand.schema.json -d films/<slug>/brand.json
  12. Write BRAND-SOURCES.md: one line per value → source (file:line, URL + selector, or screenshot + x,y).
  13. Show the user a 6-line summary (name, theme, 6 swatches as hex, fonts, logo file, anything mapped or asked).

Hard stops (do not continue the pipeline)

SituationDoNever
No logo file in repo, site or screenshotsAsk: "Send the logo as SVG (best) or a PNG ≥ 512 px with transparency."draw, trace, generate, or approximate a logo
Logo only as a tiny faviconAsk for a larger fileupscale a 32 px favicon into a hero mark
No colors captured (no repo access, site blocked, no screenshots)Ask for the URL or 2–3 screenshots, or the hex codespick "nice" colors or a default palette
Conflicting palettes (app vs marketing)Ask which one the film should use; default to the marketing siteblend them
User wants a text wordmark because no logo existsAllowed only with explicit "yes": product name in the display font, fg colorpresent it as their logo

Rules

  • Copy logo files byte-for-byte. Don't recolor, crop or "clean up" a logo unless the user asks.
  • Never use another company's logo or the user's customers' logos without the user confirming they have the right.
  • Never fetch fonts from sources whose license forbids redistribution into a repo (Fontshare FFL faces such as Satoshi or General Sans, Apple SF Pro): map them (brand-json.md § fonts).
  • brand.json holds no secrets and no personal data beyond the public product name and URL.
  • Re-running intake overwrites only fields whose source changed; keep fields the user edited by hand (diff first).
  • Downstream skills read only brand.json; never hardcode brand hex values in scenes [craft/06#grade-discipline].

Individual skills in this repo

This repo contains 4 individual skills — each has its own dedicated page.

evgenspm/launchfilm

QA a rendered launch film before anyone ships it. Use for "QA the video", "check the render", "is it ready to post", "review the film", "why does it look cheap", "check the captions/safe zones/loudness", after every render and before package. Reads the CLI's automatic report (`npx launchfilm qa <slug>`), contact sheets and stills at key timestamps, then checks text-at-time readability, contrast, platform safe zones, loudness (−14 LUFS, −1.5 dBTP), ffprobe encode specs, black and frozen frames, cuts on the beat, and the 12 amateur tells as blocking checks. Writes qa/<slug>/QA.md where every line cites a file or a measured number; a check that was not run says NOT CHECKED, never PASS. Use scene-build to fix picture problems it finds, sound to fix the mix, launch-film for the whole pipeline, reference-study for reference videos.

evgenspm/launchfilm

Launch video, launch film, product video, product launch, promo, teaser, trailer, demo video, Product Hunt video, X / LinkedIn launch clip, reel, hero loop, motion graphics, "make a video for my product", Remotion film. Router and gated pipeline for making a pro product-launch film with the launchfilm studio in ./launch-video: brief, brand intake, story and storyboard (user approves), sound, scene build, frame QA, render per platform preset, package, post copy, one-time credit note. Use this first for any request to make, remake or revise a launch or product film; it calls the sibling skills (brand-intake, story, sound, scene-build, recipes, film-qa, launch-post). Do not use it to study a reference video (use reference-study), to browse recipes only (use recipes), or for generic Remotion questions unrelated to a launch film.

evgenspm/launchfilm

Write the launch post that goes with the film: X / Twitter post, LinkedIn post, Product Hunt tagline, description and maker comment, written in the founder's own voice, concrete, no AI slop ("excited to announce", em dashes, buzzwords). Triggers: write the tweet, launch post, LinkedIn post, Product Hunt copy, PH tagline, maker comment, caption for the video, announcement copy. Use after the film is rendered (or when the user asks for post copy for an existing film); starts from `npx launchfilm post <slug>` and the film's BRIEF.md and STORYBOARD.md, writes out/<slug>/POST.md. Never posts anything. Not for the film's own on-screen script or VO (story).

evgenspm/launchfilm

Find launchfilm recipes (published launch films studied frame by frame and written down as text, some with ready Remotion code) and build the user's film from 1 to 3 of them. Use for "use a template", "start from a recipe", "make a 30s launch film from recipe <id>", "something like this style", "show me options", "which recipe fits a 30 s vertical launch", "remix recipe X with our brand", or when a storyboard needs a proven hook, feature beat, logo reveal or end card. Searches recipes/CATALOG.md or recipes/index.json, scores and picks 1 to 3, shows each with its source link, reads the recipe.md beat sheet, then scaffolds with `npx launchfilm new <slug> --recipe <id>`: ready code when Recipe.tsx exists, else TODO scenes built from the beat sheet with studio presets, keeping the recipe's timings, springs and sounds re-timed to the user's length and beat grid. Use reference-study to make a new recipe, story for the storyboard, scene-build for scenes, launch-film for the whole pipeline.

Related Skills

steipete/video-frames

Extract frames or short clips from videos using ffmpeg.

community

steipete/summarize

Summarize or transcribe URLs, YouTube/videos, podcasts, articles, transcripts, PDFs, and local files.

community

openclaw/openclaw

Use when testing, fixing, or extending the OpenClaw Control UI GUI with Vitest + Playwright end-to-end checks, mocked Gateway WebSocket flows, mocked dashboard runs, screenshots/videos, or agent-verifiable browser proof.

community

obra/superpowers

Obra superpowers agent skills.

community

affaan-m/ECC

See, Understand, Act on video and audio. See- ingest from local files, URLs, RTSP/live feeds, or live record desktop; return realtime context and playable stream links. Understand- extract frames, build visual/semantic/temporal indexes, and search moments with timestamps and auto-clips. Act- transcode and normalize (codec, fps, resolution, aspect ratio), perform timeline edits (subtitles, text/image overlays, branding, audio overlays, dubbing, translation), generate media assets (image, audio...

community

affaan-m/everything-claude-code

End-to-end marketing campaign planning and execution. Covers audience research, positioning, campaign angle definition, landing page copy, email sequences, social posts, ad copy, short-form video scripts, and content calendars. Use as the orchestration layer for multi-channel product launches. Use when planning or executing a multi-channel product launch, or producing landing page, email, social, or ad copy.

community