launch-video
Skill0 starsChanged 17 days agoMITView on GitHub
Make a 30-45 second product launch video in code with Claude Code, the kind SaaS companies post on launch day. One sentence split across scenes, real product screens with slow camera moves, a typed prompt, a proof beat and a clear call to action. Use when someone says "launch video", "promo video for my product", "announce my course/cohort/offer", "make a launch reel" or "trailer for my product".
27 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- aya-taleb/mimic-skillstheir own version, first seen Nov 15, 2026
- JorgeMenaDev/skillstheir own version, first seen Nov 11, 2026
- dzhng/jevgreptheir own version, first seen Nov 11, 2026
- dzhng/skillstheir own version, first seen Nov 10, 2026
- imMamdouhaboammar/motion-graphics-skillsedited, first seen Nov 1, 2026
- Mathews-Tom/armorytheir own version, first seen Nov 1, 2026
Used with
Projects with it also use marketing-pages and implement-spec-with-codex.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
dzhngSkillmarketing-pages
Best-practice rulebook for a marketing site's pages, organized by page class — campaign landers, product pages, programmatic SEO trees, editorial. Use when writing or updating a landing/marketing page, wiring a campaign lander to an attribution identifier, changing site-wide nav/footer links, touching sitemap/robots/agent-readable surfaces, or auditing a public site's indexing, reachability, and conversion setup.
Also in 3 projects that use this
dzhngSkillimplement-spec-with-codex
Run [implement-spec](../implement-spec/SKILL.md) with Codex doing the implementation passes while you orchestrate, integrate, and review. Use when the user asks to implement a spec with Codex, or to run implement-spec with Codex as the implementer.
Also in 3 projects that use this
Other versions27 projects use a version of this.
Word for word · 1
- charlie947/motion-graphics-skills★ 247100% same
Edited · 1
- imMamdouhaboammar/motion-graphics-skills★ 5076% same
Wrote their own version · 25
- dzhng/jevgrep★ 3.2ksame name
- dzhng/skills★ 1.5ksame name
- Mathews-Tom/armory★ 340same name
- dzhng/yap★ 118same name
- iamvicliu/AgentHub★ 80same name
- timscheuerai/content-vault★ 38same name
- pragma-sh/pragma★ 25same name
- iart-ai/ad-video-skills★ 22same name
- ucsandman/claude-skills★ 5same name
- broomva/skills★ 4same name
15 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository45 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/smokekit-ai-workflow-orchestration/templates/CLAUDE.mdCLAUDE.md
- afficheuxSkill
- animateSkill
- motion-designSkill
- review-loopSkill
- claude-motionSkill
- sound-designSkill
- web-simsSkill
- collectSkill
- explainer-storyboardSkill
- explainrooSkill
- fixitSkill
- herdr-teamSkill
- merge-gateSkill
- motion-designSkill
- motion-graphicsSkill
- animated-chartSkill
- apple-launch-filmSkill
- brand-intakeSkill
- loop-coverSkill
- milestone-revealSkill
- model-showdownSkill
- motion-brief-writerSkill
- motion-effectsSkill
- motion-prompt-writerSkill
- newsletter-promoSkill
- reel-exportSkill
- reference-to-motionSkill
- motion-graphics-skillsSkill
- title-sequence-3dSkill
- vox-explainerSkill
- motion-illustrateSkill
- motion-launchSkill
- motion-principlesSkill
- motion-soundSkill
- motion-webSkill
- prd-table-rondeSkill
- product-launch-motionSkill
- remotion-motion-graphicsSkill
- rush-cutSkill
- secretscanSkill
- smokekit-ai-workflow-orchestrationSkill
- uxfixSkill
- wassupSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 24 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Before you start: read brand.md and MOTION.md if they exist.
- Distinctive: line 20
Never invent a price, a date, a "spots left" count, a testimonial or a result.
- Distinctive: line 29
Variety: No two beats share the same layout.
“Common” is measured: kept by at least 6 in 10 of the 24 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Launch video, built in code
A launch video sells one thing in 30-45 seconds. You build it as one HTML file with window.seek(seconds), then export to MP4.
Before you start: read brand.md and MOTION.md if they exist. If not, run brand-intake first, or ask for hex codes, a font and a logo file. Never call a result on-brand without them.
Step 1: Ask for five things, then wait
- What's launching, in one line. Example: "LinkedIn AI OS, a six-week cohort that sets up your content system."
- The one sentence the video says, split into 3-5 beats. Example: "Your next post, / in your voice, / checked before you see it."
- Proof. Real screenshots of the product, real results with their source, or real customer posts. Attached files only.
- The call to action, word for word, exactly as it appears on the sales page.
- Brand. Hex codes, font, logo file. Plus the size: 1920 x 1080, 1080 x 1350 or 1080 x 1920.
Never invent a price, a date, a "spots left" count, a testimonial or a result.
What "premium" means here (learned the hard way)
Three first drafts were rejected as "not premium" and "not my brand colours". What fixed it:
- Your real brand colours, sampled from your landing page or your best graphic. Never a default palette.
- Glass UI. Product surfaces as frosted, liquid-glass panels with soft depth, like Apple's current UI.
- The prompt typed live into a real-looking input box. That is the one place typing belongs.
- Real, recent work on the proof cards, not old examples.
- Variety. No two beats share the same layout.
Build the first 10 seconds in two or three styles first. Pick one. Only then build the rest.
Step 2: Lay out the beats
Default 7 beats, 45 seconds:
| # | Time | Beat |
| 1 | 0-4s | First words of the sentence, big, on a clean background. The hook. |
| 2 | 4-9s | Next words over real proof (posts, results, screens). |
| 3 | 9-17s | The product working: a screen, a cursor typing a real prompt, the output appearing. |
| 4 | 17-22s | The quality beat: something checks, passes or ticks. |
| 5 | 22-32s | How it works: steps, weeks or features as one simple visual. |
| 6 | 32-38s | The number that matters, counted up, with its source. |
| 7 | 38-45s | Name, call to action, requirement. Holds long enough to read. |
Show the beat sheet and wait for a yes.
Step 3: Build brief (paste into Claude Code)
Build one self-contained HTML file called index.html for a [LENGTH]-second product launch video at [WIDTH] x [HEIGHT]. Use only the files I attached. Nothing loaded from the internet.
Style: clean, premium product launch. Background [BG], text [TEXT], one accent [ACCENT], font [FONT] or a system sans-serif. Generous space. Product screens float on soft shadows with slow push-ins. One sentence is split across the beats and each fragment lands with a short, confident move.
Banned: typewriter reveals on headlines (typing belongs only inside the product's input box), glow, bouncing, gradients on text, stock-photo people, fake testimonials, any number I did not give you.
Beats: follow my beat sheet exactly, with its timings.
Build rules: work out every frame from the time alone. Add window.seek(seconds) that draws that exact moment. Autoplay on a loop when opened normally, wait for seek when the URL has ?render.
After the build: capture one frame from the middle of every beat. Check for cut-off text, overlapping elements, anything unreadable at phone size, and any word or number not in my brief. Fix what is real and keep the first version.Step 4: Check it like a buyer
- Would a stranger know what's launching by second 4?
- Is every number traceable to a source?
- Does the call to action hold for at least 3 seconds?
- Is it readable on a phone, with the sound off?
Step 5: Export
HyperFrames (free, open source): npx skills add heygen-com/hyperframes, then npx hyperframes render. Export a 16:9 and a 4:5 cut. Check which tools exist before installing, and ask first.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

