正在加载视频...

视频加载失败

加载此视频时出现问题。这可能是由于临时网络问题，或视频可能不可用。

Nobody's talking about the Claude trick that fixes every Seedance 2.0 video mistake. A cinematic action scene, an animated sequence, a product ad, and a dialogue scene are completely different types of content. Different camera language, different pacing, different reference logic. Most people try to force all of it... through one universal prompt. The fix turns out to be simpler than expected: Claude Skills. It's not some secret hack. It's a file of instructions you load into Claude for one specific type of task. Once it's loaded, Claude stops acting like a general assistant and starts thinking like an expert in that one niche — with its own set of rules for that scene type. Here's what that looks like in practice: ▪ Cinematic skill — generates real camera language: dolly moves, crane shots, rack focus, shot discipline across multiple cuts. Test: a medieval battle between two armies, 15 seconds, dark fantasy. Result — three shots with the shot logic of an actual film, not just "epic battle" typed as text. ▪ Animation skill — locks in style and physics before a single shot is built. One test: a rain-soaked shonen fight in the style of Tokyo Revengers. Another: a quiet Ghibli-style farm scene. Same skill, completely different visual output — because the style gets fixed at the very top of the prompt. ▪ Product ad skill — keeps the product front and center in every shot: clean hero framing, commercial lighting, a full product description built from the reference image before any shots are generated. ▪ Dialogue skill — this is where most people fall apart. Lip sync, emotional direction, shot structure, and audio cues all have to work together. Test: an interrogation scene with a fourth-wall break — and the moment landed exactly as written, down to the pause and tone. The core idea is simple: instead of writing a prompt from scratch every time and hoping for the best, you build one skill per content type — and Claude asks the right setup questions (genre, tone, shot count, camera energy) before generating a fully structured Seedance 2.0 prompt. One prompt template for everything is exactly why 90% of AI videos look the same. This 13-minute video is free, and it's more useful than a $500 course. YouTube: "Skai Generated" - Thank you for sharing this invaluable material with us.show more

Zentrix⌚️

2,403 subscribers

45,250 次观看 • 21 天前 •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

Claude Cowork + Seedance 2.0 is f*cking wild 🤯 I built a skill inside Claude Cowork that generates UGC video ads on demand using Seedance 2.0, the best AI video model. One product image + one prompt = a full UGC ad with multiple shots, dialogue, and on-brand pacing. All inside Claude Cowork. Perfect for DTC brands and agencies who need UGC creative at volume without hiring creators or paying per-video SaaS fees. If you're briefing creators every week, waiting days for footage, paying $150–$300 per UGC video, and still getting ads that miss the brand vibe... This skill eliminates the entire loop: → Drop a product image into Claude Cowork → Tell it the ad angle (unboxing, review, lifestyle, demo) → Claude writes the dialogue, shot list, and pacing → Fires it to Seedance 2.0 via FAL AI API → Downloads finished clips into organized folders → Stitches multiple shots into one finished ad No creator briefs. No waiting for footage. No $200/video platform fees. What you get: → UGC video ads generated in minutes, not days → Full control over dialogue, pacing, and shot composition → Your product photos as reference so Seedance matches your real packaging → A reusable skill: new product, new folder, same pipeline Built 100% in Claude Cowork with the Seedance 2.0 API. I put together a full playbook with the Claude Cowork skill file, the exact prompts, and the FAL AI setup to get this running yourself. Want it for free? > Like this post > Comment "UGC" And I'll send it over (must be following so I can DM)

Mike Futia

79,937 次观看 • 3 个月前

RIP Arcads 🤯 I built a Claude skill that vibe-codes UGC ads on demand. One product + one prompt = the AI creator, the script, the scene-by-scene shot list, and finished video. All inside Claude. Perfect for DTC brands and agencies who can't afford to keep paying $500-$1,500 per UGC video and waiting 2 weeks for revisions. If you're briefing creators, mailing PR boxes, waiting on first cuts, then asking for re-shoots because the hook didn't land... This skill eliminates the entire loop: → Tell Claude the product, ad angle, and length → Skill writes the GPT Image 2.0 prompt to generate the AI creator from scratch → Skill writes every scene prompt, dialogue line, and delivery direction → Pipe it into Seedance 2.0 with character + product + voice locked → Speed up + caption in CapCut → Ship the ad in 20 minutes No more paying $11 per video on Arcads. What you get: → Perfect character consistency across every scene → Voice consistency that holds clip-to-clip (small CapCut hack inside the tutorial) → Real product fidelity using your actual product photo as a reference → Multi-scene day-in-life, testimonial, and action-shot formats out of the box Built 100% with a Claude skill + Seedance 2.0. I recorded a full step-by-step tutorial showing the exact workflow + the 3 finished AI UGC ads I made for Rhode, AG1, and Barebells. Want to see the full breakdown? > Like this post > Comment "UGC" And I'll send it over (must be following so I can DM)

RIP Arcads 🤯 I built a Claude skill that vibe-codes UGC ads on demand. One product + one prompt = the AI creator, the script, the scene-by-scene shot list, and finished video. All inside Claude. Perfect for DTC brands and agencies who can't afford to keep paying $500-$1,500 per UGC video and waiting 2 weeks for revisions. If you're briefing creators, mailing PR boxes, waiting on first cuts, then asking for re-shoots because the hook didn't land... This skill eliminates the entire loop: → Tell Claude the product, ad angle, and length → Skill writes the GPT Image 2.0 prompt to generate the AI creator from scratch → Skill writes every scene prompt, dialogue line, and delivery direction → Pipe it into Seedance 2.0 with character + product + voice locked → Speed up + caption in CapCut → Ship the ad in 20 minutes No more paying $11 per video on Arcads. What you get: → Perfect character consistency across every scene → Voice consistency that holds clip-to-clip (small CapCut hack inside the tutorial) → Real product fidelity using your actual product photo as a reference → Multi-scene day-in-life, testimonial, and action-shot formats out of the box Built 100% with a Claude skill + Seedance 2.0. I recorded a full step-by-step tutorial showing the exact workflow + the 3 finished AI UGC ads I made for Rhode, AG1, and Barebells. Want to see the full breakdown? > Like this post > Comment "UGC" And I'll send it over (must be following so I can DM)

Mike Futia

34,276 次观看 • 3 个月前

$Hermes + Claude + Higgsfield MCP + ViralBuilder = 💰💰💰 Four tools. One prompt chain. Hook to finished video in 10 minutes. I built a Claude skill that writes shot-by-shot Higgsfield prompts from a single creative brief. ViralBuilder tells you what's winning. The skill turns it into a production-ready prompt. Higgsfield renders it. No creative director. No guessing. No separate tools. Here is the setup: Higgsfield MCP → Open Claude Code → Settings → Connectors → Enter: → Connect your account Hermes → The agent layer running underneath Claude Code → It holds your skills, crons, memory, and routing rules → When you prompt Claude, Hermes feeds it the context it needs ViralBuilder (like Gethookd) → The winning ecom video database → Scrapes top performing ecom videos across platforms → Claude reads the data and extracts what styles, hooks, and formats are actually scaling The skill: video-prompt-builder → Installed inside Claude via Hermes → Takes a creative brief and outputs a full shot-by-shot prompt → Covers camera work, effects, transitions, pacing, and energy arc → Every output is structured for Higgsfield to render without ambiguity No switching apps. No export steps. Everything runs from one place. ▸ FIND WINNING CREATIVE ANGLES ViralBuilder tells you what the market already validated. Claude reads it and extracts the pattern. Prompts to run: "Search ViralBuilder for the top performing ecom videos in [niche] over the last 21 days. Extract the 3 dominant hook styles and rank by view velocity." "Pull the winning video formats in [niche] from ViralBuilder. Which opening 3 seconds appears most across videos spending over $10k?" "Find what video style is scaling right now in [niche] for the US market. UGC, talking head, or product demo. Filter for videos with over 1M views." "Pull the last 30 days of viral ecom hooks in [niche] from ViralBuilder. Cluster by emotional trigger. Which cluster has the most longevity?" You are not guessing at angles. You are reading what the market already spent money validating. ▸ BUILD THE PROMPT WITH THE SKILL This is where the video-prompt-builder skill takes over. You give Claude the winning angle. The skill outputs a complete shot-by-shot prompt with effects, transitions, pacing, and energy arc ready to fire into Higgsfield. Prompts to run: "Use the video-prompt-builder skill. Brief: 15-second UGC ad for [product] in [niche]. Hook style: [style from ViralBuilder]. Tone: direct to camera, US English. Output the full shot-by-shot effects timeline, effects inventory, density map, and energy arc." "Use the video-prompt-builder skill. The dominant hook in [niche] this week is [hook]. Build a 10-second product video prompt that opens with a speed ramp into a close-up product reveal. Include a signature visual effect and a low-density CTA landing." "Use the video-prompt-builder skill. Brief: replicate the pacing and energy of a [style description] video for [product]. Target duration: 20 seconds. Output all four sections. Then generate the video with Higgsfield using the shot-by-shot prompt." The skill outputs four sections every time: → Shot-by-shot effects timeline with camera, movement, and transitions per shot → Master effects inventory showing every technique used and where → Effects density map showing high, medium, and low intensity across the timeline → Energy arc describing how the video opens, builds, and lands That output goes directly into Higgsfield. No rewriting. No translating. ▸ GENERATE THE CREATIVE Claude writes the brief via the skill. Higgsfield MCP builds the video. Both happen in the same session. Prompts to run: "Use the video-prompt-builder skill to write a 15-second UGC prompt for [product]. Hook in the first 3 seconds, speed ramp into product reveal, slow-motion CTA landing. Then generate with Higgsfield in 9:16 format." "Build 3 prompt variations on this winning angle: [angle]. Each variation opens with a different effect — speed ramp, digital zoom, whip pan. Use the video-prompt-builder skill for each. Then generate all three with Higgsfield." "Use the video-prompt-builder skill. Brief: problem-solution ad for [product], 20 seconds, US market. Problem shot at high density, product reveal at medium, result and CTA at low. Generate with Higgsfield in 9:16." No separate tool. No file transfer. The video comes back in the same thread. ▸ CHAIN THE WHOLE STACK One prompt. All four tools firing together. "You are my ad creative director. Hermes has loaded my brand context. Pull the top performing video style in [niche] from ViralBuilder this week. Use the video-prompt-builder skill to write a full shot-by-shot prompt for [product] that replicates that style — 20 seconds, 9:16, US market, hook in the first 3 seconds. Output the effects timeline, inventory, density map, and energy arc. Then generate the video with Higgsfield." That single prompt replaces a half-day of production. The math before this stack: Brief: 30 minutes Script: 1 hour Creative production: 2 to 3 hours Agency or freelancer cost: $500 to $2,000 per creative With this stack: Hook to finished creative: 10 minutes Cost per creative: tool subscription, a fraction of agency rate 5 product tests in the time it used to take to brief one Bad product tests are where US ad budget disappears. $600 to $1,500 per failed test, before you even know if the angle works. This stack shows you what the market already validated before you spend a dollar on production. Hermes = your context layer. Brand, goals, past performance. Claude is always informed. ViralBuilder = your winning video database. See exactly what styles, hooks, and formats are scaling before you produce anything. video-prompt-builder skill = the translation layer. Turns a creative brief into a structured, production-ready Higgsfield prompt every time. Claude = the brain. Reads the market, writes the brief, chains the tools. Higgsfield MCP = the output. Video generated directly from the prompt. No export step. Four tools. One session. 10 minutes. Comment + RT "STACK" and I'll DM you the full workflow + the video-prompt-builder skill file.$

Hermes + Claude + Higgsfield MCP + ViralBuilder = 💰💰💰 Four tools. One prompt chain. Hook to finished video in 10 minutes. I built a Claude skill that writes shot-by-shot Higgsfield prompts from a single creative brief. ViralBuilder tells you what's winning. The skill turns it into a production-ready prompt. Higgsfield renders it. No creative director. No guessing. No separate tools. Here is the setup: Higgsfield MCP → Open Claude Code → Settings → Connectors → Enter: → Connect your account Hermes → The agent layer running underneath Claude Code → It holds your skills, crons, memory, and routing rules → When you prompt Claude, Hermes feeds it the context it needs ViralBuilder (like Gethookd) → The winning ecom video database → Scrapes top performing ecom videos across platforms → Claude reads the data and extracts what styles, hooks, and formats are actually scaling The skill: video-prompt-builder → Installed inside Claude via Hermes → Takes a creative brief and outputs a full shot-by-shot prompt → Covers camera work, effects, transitions, pacing, and energy arc → Every output is structured for Higgsfield to render without ambiguity No switching apps. No export steps. Everything runs from one place. ▸ FIND WINNING CREATIVE ANGLES ViralBuilder tells you what the market already validated. Claude reads it and extracts the pattern. Prompts to run: "Search ViralBuilder for the top performing ecom videos in [niche] over the last 21 days. Extract the 3 dominant hook styles and rank by view velocity." "Pull the winning video formats in [niche] from ViralBuilder. Which opening 3 seconds appears most across videos spending over $10k?" "Find what video style is scaling right now in [niche] for the US market. UGC, talking head, or product demo. Filter for videos with over 1M views." "Pull the last 30 days of viral ecom hooks in [niche] from ViralBuilder. Cluster by emotional trigger. Which cluster has the most longevity?" You are not guessing at angles. You are reading what the market already spent money validating. ▸ BUILD THE PROMPT WITH THE SKILL This is where the video-prompt-builder skill takes over. You give Claude the winning angle. The skill outputs a complete shot-by-shot prompt with effects, transitions, pacing, and energy arc ready to fire into Higgsfield. Prompts to run: "Use the video-prompt-builder skill. Brief: 15-second UGC ad for [product] in [niche]. Hook style: [style from ViralBuilder]. Tone: direct to camera, US English. Output the full shot-by-shot effects timeline, effects inventory, density map, and energy arc." "Use the video-prompt-builder skill. The dominant hook in [niche] this week is [hook]. Build a 10-second product video prompt that opens with a speed ramp into a close-up product reveal. Include a signature visual effect and a low-density CTA landing." "Use the video-prompt-builder skill. Brief: replicate the pacing and energy of a [style description] video for [product]. Target duration: 20 seconds. Output all four sections. Then generate the video with Higgsfield using the shot-by-shot prompt." The skill outputs four sections every time: → Shot-by-shot effects timeline with camera, movement, and transitions per shot → Master effects inventory showing every technique used and where → Effects density map showing high, medium, and low intensity across the timeline → Energy arc describing how the video opens, builds, and lands That output goes directly into Higgsfield. No rewriting. No translating. ▸ GENERATE THE CREATIVE Claude writes the brief via the skill. Higgsfield MCP builds the video. Both happen in the same session. Prompts to run: "Use the video-prompt-builder skill to write a 15-second UGC prompt for [product]. Hook in the first 3 seconds, speed ramp into product reveal, slow-motion CTA landing. Then generate with Higgsfield in 9:16 format." "Build 3 prompt variations on this winning angle: [angle]. Each variation opens with a different effect — speed ramp, digital zoom, whip pan. Use the video-prompt-builder skill for each. Then generate all three with Higgsfield." "Use the video-prompt-builder skill. Brief: problem-solution ad for [product], 20 seconds, US market. Problem shot at high density, product reveal at medium, result and CTA at low. Generate with Higgsfield in 9:16." No separate tool. No file transfer. The video comes back in the same thread. ▸ CHAIN THE WHOLE STACK One prompt. All four tools firing together. "You are my ad creative director. Hermes has loaded my brand context. Pull the top performing video style in [niche] from ViralBuilder this week. Use the video-prompt-builder skill to write a full shot-by-shot prompt for [product] that replicates that style — 20 seconds, 9:16, US market, hook in the first 3 seconds. Output the effects timeline, inventory, density map, and energy arc. Then generate the video with Higgsfield." That single prompt replaces a half-day of production. The math before this stack: Brief: 30 minutes Script: 1 hour Creative production: 2 to 3 hours Agency or freelancer cost: $500 to $2,000 per creative With this stack: Hook to finished creative: 10 minutes Cost per creative: tool subscription, a fraction of agency rate 5 product tests in the time it used to take to brief one Bad product tests are where US ad budget disappears. $600 to $1,500 per failed test, before you even know if the angle works. This stack shows you what the market already validated before you spend a dollar on production. Hermes = your context layer. Brand, goals, past performance. Claude is always informed. ViralBuilder = your winning video database. See exactly what styles, hooks, and formats are scaling before you produce anything. video-prompt-builder skill = the translation layer. Turns a creative brief into a structured, production-ready Higgsfield prompt every time. Claude = the brain. Reads the market, writes the brief, chains the tools. Higgsfield MCP = the output. Video generated directly from the prompt. No export step. Four tools. One session. 10 minutes. Comment + RT "STACK" and I'll DM you the full workflow + the video-prompt-builder skill file.

Kid Pak

57,709 次观看 • 3 个月前

Claymotion ads are crushing it on Meta right now. Built a free claude skill to make them 👇 If you've been scrolling Meta lately, you've seen them — stop-motion clay characters, tactile textures, weirdly satisfying to watch. CTRs are 2-3x the feed average. Almost nobody is running them. The problem: they look impossible to make unless you have a studio. They're not. You just need the right prompts. So I packaged the prompt system as a Claude Code skill. It's free. Here's what it does: Paste your product URL. Out comes a full claymotion ad plan: 1/ Shot-by-shot storyboard 5-7 shots with the narrative arc. Setup → product reveal → payoff → CTA. 2/ Image prompt per shot Exact prompt you paste into Midjourney, Nano Banana, or any image gen. Camera angle, lighting, clay texture specs, character details — dialed in for consistency across shots. 3/ Video prompt per shot The animation prompt you paste into Kling, Veo, Seedance, or Sora. Motion direction, pacing, transitions — so the shots actually flow. 4/ VO script per shot Voiceover copy written for rhythm. Timed to the shot length. Hook, body, CTA — all on brand. 5/ Music + sfx direction Tone notes for the track. Specific sfx cues per shot (squish, pop, whoosh) You take the outputs. Paste them into your image + video generators. Stitch the shots. Record the VO. A full claymotion ad in under an hour, at the cost of a few API credits. Instead of $3,000 and 3 weeks with an animation studio. Why claymotion works right now: → Pattern break — nothing else in the feed looks like it → Tactile feel — clay reads as "real" even when AI-generated → High dwell time — people watch the whole thing → Cheap to test — 5-10 variations per product is now feasible Comment "Clay" and I'll send you: → The Claude Code skill (free) → A starter prompt pack → 3 example storyboards so you can see the output (must be connected)

Ahad Shams

16,836 次观看 • 4 个月前

Zero VFX experience. Just Claude, Seedance 2.0, and a phone clip. The result looks like a $10M scene In this tutorial you'll learn how to create cinematic AI VFX from your own real footage — no green screen, no masking, no compositing, no render times. Claude doesn't touch the video — it reads your clip frame by frame and writes the prompt, locking your face, camera move, light, and gestures, then naming the one thing to change and when. That prompt goes into Seedance 2.0, which only touches what was named. That's the trick. You're not describing an effect and hoping the AI gets it. Claude studies the footage first and hands Seedance a locked, precise instruction — which is why a hand can morph mid-sentence with zero visible cut, or neon reflections land on the dashboard automatically, with nothing graded by hand. One clip in, one sentence to Claude, one prompt into Seedance 2.0 — and out comes a shot that would normally cost a studio a month. ▪ 00:00 Intro ▪ 01:28 The 3 levels of AI VFX ▪ 01:59 Level 1 — Swapping the world (walking) ▪ 04:32 Level 2 — Changing an element ▪ 07:26 Level 3 — The handheld showcase ▪ 10:15 Outro YouTube: "Higgsfield AI - I Added Insane AI VFX to Real Footage in 4K(Seedance 2.0)" Thank you for sharing this free tutorial with us. It is invaluable information.

Zero VFX experience. Just Claude, Seedance 2.0, and a phone clip. The result looks like a $10M scene In this tutorial you'll learn how to create cinematic AI VFX from your own real footage — no green screen, no masking, no compositing, no render times. Claude doesn't touch the video — it reads your clip frame by frame and writes the prompt, locking your face, camera move, light, and gestures, then naming the one thing to change and when. That prompt goes into Seedance 2.0, which only touches what was named. That's the trick. You're not describing an effect and hoping the AI gets it. Claude studies the footage first and hands Seedance a locked, precise instruction — which is why a hand can morph mid-sentence with zero visible cut, or neon reflections land on the dashboard automatically, with nothing graded by hand. One clip in, one sentence to Claude, one prompt into Seedance 2.0 — and out comes a shot that would normally cost a studio a month. ▪ 00:00 Intro ▪ 01:28 The 3 levels of AI VFX ▪ 01:59 Level 1 — Swapping the world (walking) ▪ 04:32 Level 2 — Changing an element ▪ 07:26 Level 3 — The handheld showcase ▪ 10:15 Outro YouTube: "Higgsfield AI - I Added Insane AI VFX to Real Footage in 4K(Seedance 2.0)" Thank you for sharing this free tutorial with us. It is invaluable information.

Zentrix⌚️

28,606 次观看 • 19 天前

REAL ESTATE PEOPLE WILL HATE HIM FOR THIS. HE BUILT A CLAUDE AGENT THAT TURNS ANY LISTING INTO A SELLABLE VIDEO ON ITS OWN Playbook: connect Claude to a video generator, paste a listing, get a cinematic tour of every room, sell it to the agent But typing the prompt for every listing doesn't scale. He turned it into a skill his Claude runs on its own Here's how to build the automated version: 1. Connect the video engine once. In Claude, go to Customize, Connectors, Add Custom Connector, name it Higgsfield, and paste the server URL from higgsfield. ai/mcp. Authenticate through your account. No API keys. Now Claude can generate video straight from chat 2. Turn the workflow into a skill. Instead of pasting the same prompt every time, have Claude build a skill. Tell it: "Create a skill called listing-to-video. When I give it a listing URL, scrape the room photos, generate a cinematic clip of each room with Higgsfield, and save them to a folder." Now the whole process is one command, not a wall of text 3. Let the agent run the listing. Hand it a URL and say "run listing-to-video on this." It pulls the photos, fires each room through the video model, and brings the clips back. You wrote the prompt once, inside the skill. You never write it again 4. Stitch and deliver. Drop the clips together into one tour. Send a free sample to the listing's agent, then charge per video or a monthly rate for ongoing listings 5. Scale it with your team. Add a skill that drafts the outreach email and one that builds a simple landing page for the agent. Now one operator runs sourcing, production, and pitching from a single Claude session The edge isn't generating one video. It's building the skill once so every future listing runs itself Bookmark this

REAL ESTATE PEOPLE WILL HATE HIM FOR THIS. HE BUILT A CLAUDE AGENT THAT TURNS ANY LISTING INTO A SELLABLE VIDEO ON ITS OWN Playbook: connect Claude to a video generator, paste a listing, get a cinematic tour of every room, sell it to the agent But typing the prompt for every listing doesn't scale. He turned it into a skill his Claude runs on its own Here's how to build the automated version: 1. Connect the video engine once. In Claude, go to Customize, Connectors, Add Custom Connector, name it Higgsfield, and paste the server URL from higgsfield. ai/mcp. Authenticate through your account. No API keys. Now Claude can generate video straight from chat 2. Turn the workflow into a skill. Instead of pasting the same prompt every time, have Claude build a skill. Tell it: "Create a skill called listing-to-video. When I give it a listing URL, scrape the room photos, generate a cinematic clip of each room with Higgsfield, and save them to a folder." Now the whole process is one command, not a wall of text 3. Let the agent run the listing. Hand it a URL and say "run listing-to-video on this." It pulls the photos, fires each room through the video model, and brings the clips back. You wrote the prompt once, inside the skill. You never write it again 4. Stitch and deliver. Drop the clips together into one tour. Send a free sample to the listing's agent, then charge per video or a monthly rate for ongoing listings 5. Scale it with your team. Add a skill that drafts the outreach email and one that builds a simple landing page for the agent. Now one operator runs sourcing, production, and pitching from a single Claude session The edge isn't generating one video. It's building the skill once so every future listing runs itself Bookmark this

Yarchi

54,840 次观看 • 2 个月前

📖THE SEEDANCE 2.0 PROMPT FORMAT THAT NOBODY IS USING BUT EVERYONE SHOULD Most people use Seedance 2.0 wrong. They type a normal prompt and wonder why the result looks generic. The difference between these two visuals isn't a better idea — it's a better prompt format. Normal prompt gives you a good result. JSON prompt gives you a cinematic one. Here's why it works: A normal prompt describes what you want. A JSON prompt tells Seedance exactly how to build the scene — camera movement, lighting angle, atmosphere, texture, depth, timing. You're not asking for a video. You're engineering one. The crystal dolphin jumping above an ancient courtyard with floating jellyfish — same concept, two completely different outputs. The JSON version has golden hour, dramatic clouds, volumetric light, and a sense of scale the normal prompt never reached. The glowing lotus fountain — same story. Normal prompt gives you a clean render. JSON gives you a full cinematic frame with layered depth, warm lantern light, and a composition that looks like it belongs in a feature film. The workflow that produces this: • Step 1 — Write your scene idea in plain language first •Step 2 — Ask Claude to convert it into a structured JSON prompt with fields for: subject, environment, camera, lighting, mood, motion, color grade • Step 3 — Paste the JSON into Seedance 2.0 • Step 4 — Take the best clip into Premiere Pro for final color correction and sound design The tools are free or cheap. The knowledge of how to prompt is what separates the results. This is the gap most creators never close. 📥 BACK TOMORROW. There will be new life hacks 🔖 The full guide is pinned below. Save it before you need it.

📖THE SEEDANCE 2.0 PROMPT FORMAT THAT NOBODY IS USING BUT EVERYONE SHOULD Most people use Seedance 2.0 wrong. They type a normal prompt and wonder why the result looks generic. The difference between these two visuals isn't a better idea — it's a better prompt format. Normal prompt gives you a good result. JSON prompt gives you a cinematic one. Here's why it works: A normal prompt describes what you want. A JSON prompt tells Seedance exactly how to build the scene — camera movement, lighting angle, atmosphere, texture, depth, timing. You're not asking for a video. You're engineering one. The crystal dolphin jumping above an ancient courtyard with floating jellyfish — same concept, two completely different outputs. The JSON version has golden hour, dramatic clouds, volumetric light, and a sense of scale the normal prompt never reached. The glowing lotus fountain — same story. Normal prompt gives you a clean render. JSON gives you a full cinematic frame with layered depth, warm lantern light, and a composition that looks like it belongs in a feature film. The workflow that produces this: • Step 1 — Write your scene idea in plain language first •Step 2 — Ask Claude to convert it into a structured JSON prompt with fields for: subject, environment, camera, lighting, mood, motion, color grade • Step 3 — Paste the JSON into Seedance 2.0 • Step 4 — Take the best clip into Premiere Pro for final color correction and sound design The tools are free or cheap. The knowledge of how to prompt is what separates the results. This is the gap most creators never close. 📥 BACK TOMORROW. There will be new life hacks 🔖 The full guide is pinned below. Save it before you need it.

Zentrix⌚️

136,412 次观看 • 1 个月前

Skills are the quickest way to 10x the quality and consistency of what you get from Claude Code. And you don't need to be a developer to use them. Anthropic just published how they use hundreds of skills internally every day. Most skill tutorials are made for developers — if you're in marketing, sales, content ops, or GTM, you probably watched those and moved on. But skills are just as important for non-developers. A skill is just a reusable prompt with clear instructions for a specific task. Instead of prompting Claude the same way over and over, you build it once and invoke it every time. I have a skill for writing on LinkedIn. A different one for YouTube outlines. Another for X. Each platform has different rules, different voice, different structure — so each one gets its own skill. If you're doing something repeatedly, it's time to make a skill. The biggest mistake most people make: building skills as a single .md file. A single file dumps everything into context whether Claude needs it or not. Wastes tokens. Gets worse results. Skills should be folders. Here's the structure that works: skill.md — the orchestrator. Tells Claude which files to read and when. It doesn't contain rules itself — it's the playbook. instructions/ — separate files for voice, structure, scope. Claude only loads the one it needs for the current step. examples/ — good AND bad. Good examples show what success looks like. Bad examples show patterns to avoid — AI writing tells, weak hooks, generic CTAs. Most people skip bad examples. Don't. eval/ — a checklist that scores every output before you see it. "Does it have a clear hook?" "Is it free of AI buzzwords?" Pass or fail on each item. templates/ — output formatting so you get consistent structure every time. The three types of skills that matter most for non-developers: 1. Business automation. Writing a newsletter. Checking reports and drafting follow-ups. Running programmatic ad campaigns. Any workflow you repeat — build a skill for it. 2. Content templates. Landing page copy, meta ads, email sequences, SEO briefs. Each one has specific requirements. Each one gets its own skill. 3. Thinking partners. This is the one people miss. Skills don't have to produce output. They can help you think — an advisory board that reviews your work from your ICP's perspective, a coach that pressure-tests your strategy, an ideation partner that researches competitors before suggesting your next move. If you already have skills as .md files, here's the exact prompt to restructure them in the Anthropic approved format: "I want to restructure my Claude Code skill file. Right now my skill is a single .md file and I want to break it into a folder system following Anthropic's best practices. Read my current skill file, then restructure it into a folder with: a skill.md orchestrator, an instructions/ folder with separate files for each concern (voice, structure, scope), an examples/ folder with good and bad examples, an eval/ folder with a quality checklist, and a templates/ folder for output formatting. Keep all my existing rules and intent — just reorganize them into the modular structure." Paste that into Claude Code pointed at the folder where your skill lives. It handles the rest. A few caveats: 1. Don't add too many skills. Every skill adds context Claude has to process. 50 skills loaded means everything slows down. Start with 3-5 covering your most repeated workflows. 2. Vet skills before downloading. If you grab a skill from the internet, read what's inside first. Skills can include shell commands and scripts. Check what you're running. 3. Share what works. Build a skill that performs well, put it in a shared GitHub repo. Your marketing org gets shared skills for copywriting, SEO, ad copy — new hires invoke the skill instead of learning every playbook from scratch. Onboarding time drops dramatically. 4. Keep your skills updated. When you see output you love, add it as a good example. When you see a pattern you hate, add it as a bad example. The skill gets sharper every time. I made a full video walking through all of this — including a live build of two skills from scratch (no terminal, no code), the exact prompt I use to restructure old skills, and 5 pro tips from Anthropic's internal playbook. Share this with your non-developer friends that want to do more with AI; or bookmark it to come back to at a later time.

Skills are the quickest way to 10x the quality and consistency of what you get from Claude Code. And you don't need to be a developer to use them. Anthropic just published how they use hundreds of skills internally every day. Most skill tutorials are made for developers — if you're in marketing, sales, content ops, or GTM, you probably watched those and moved on. But skills are just as important for non-developers. A skill is just a reusable prompt with clear instructions for a specific task. Instead of prompting Claude the same way over and over, you build it once and invoke it every time. I have a skill for writing on LinkedIn. A different one for YouTube outlines. Another for X. Each platform has different rules, different voice, different structure — so each one gets its own skill. If you're doing something repeatedly, it's time to make a skill. The biggest mistake most people make: building skills as a single .md file. A single file dumps everything into context whether Claude needs it or not. Wastes tokens. Gets worse results. Skills should be folders. Here's the structure that works: skill.md — the orchestrator. Tells Claude which files to read and when. It doesn't contain rules itself — it's the playbook. instructions/ — separate files for voice, structure, scope. Claude only loads the one it needs for the current step. examples/ — good AND bad. Good examples show what success looks like. Bad examples show patterns to avoid — AI writing tells, weak hooks, generic CTAs. Most people skip bad examples. Don't. eval/ — a checklist that scores every output before you see it. "Does it have a clear hook?" "Is it free of AI buzzwords?" Pass or fail on each item. templates/ — output formatting so you get consistent structure every time. The three types of skills that matter most for non-developers: 1. Business automation. Writing a newsletter. Checking reports and drafting follow-ups. Running programmatic ad campaigns. Any workflow you repeat — build a skill for it. 2. Content templates. Landing page copy, meta ads, email sequences, SEO briefs. Each one has specific requirements. Each one gets its own skill. 3. Thinking partners. This is the one people miss. Skills don't have to produce output. They can help you think — an advisory board that reviews your work from your ICP's perspective, a coach that pressure-tests your strategy, an ideation partner that researches competitors before suggesting your next move. If you already have skills as .md files, here's the exact prompt to restructure them in the Anthropic approved format: "I want to restructure my Claude Code skill file. Right now my skill is a single .md file and I want to break it into a folder system following Anthropic's best practices. Read my current skill file, then restructure it into a folder with: a skill.md orchestrator, an instructions/ folder with separate files for each concern (voice, structure, scope), an examples/ folder with good and bad examples, an eval/ folder with a quality checklist, and a templates/ folder for output formatting. Keep all my existing rules and intent — just reorganize them into the modular structure." Paste that into Claude Code pointed at the folder where your skill lives. It handles the rest. A few caveats: 1. Don't add too many skills. Every skill adds context Claude has to process. 50 skills loaded means everything slows down. Start with 3-5 covering your most repeated workflows. 2. Vet skills before downloading. If you grab a skill from the internet, read what's inside first. Skills can include shell commands and scripts. Check what you're running. 3. Share what works. Build a skill that performs well, put it in a shared GitHub repo. Your marketing org gets shared skills for copywriting, SEO, ad copy — new hires invoke the skill instead of learning every playbook from scratch. Onboarding time drops dramatically. 4. Keep your skills updated. When you see output you love, add it as a good example. When you see a pattern you hate, add it as a bad example. The skill gets sharper every time. I made a full video walking through all of this — including a live build of two skills from scratch (no terminal, no code), the exact prompt I use to restructure old skills, and 5 pro tips from Anthropic's internal playbook. Share this with your non-developer friends that want to do more with AI; or bookmark it to come back to at a later time.

JJ Englert

29,322 次观看 • 4 个月前

Cat Wu, head of product for Claude Code at Anthropic: "you can build almost anything with Claude from a single prompt now" one prompt gets you a working screen, not YOUR product Claude Code has never seen your design system, so it guesses the look fresh every time. how to hand Claude Code that system is in the article. better than the $300 design course in your tabs, and this one's free.

Cat Wu, head of product for Claude Code at Anthropic: "you can build almost anything with Claude from a single prompt now" one prompt gets you a working screen, not YOUR product Claude Code has never seen your design system, so it guesses the look fresh every time. how to hand Claude Code that system is in the article. better than the $300 design course in your tabs, and this one's free.

Mnimiy

113,663 次观看 • 2 个月前

Today we're launching iMessage video ads in Claude. Faceless video is the best-performing ad format right now — and Claude can now generate a full one end to end, in one prompt. Here's how it works: 1. Install: npx gooseworks install --all 2. Run: /goose-video make an iMessage ad for [your product] Claude writes the script, generates the photos in the thread, animates the conversation, and closes on your brand. SFX, music, end card, all of it. The trick: it's just HTML. No video generation models, so it's fast and cheap — and it works because it doesn't look like an ad. It's that easy. But this is just the start. We have created a library with 100+ open-source skills for growth that some of the fastest growing startups in the world are using every day to run ads, content, competitor research, gtm, seo and more. Comment Goose and I'll DM you the full open-source skill library.

Soham Mehta

49,849 次观看 • 1 个月前

So Runway Gen 4.5 finally adds image-to-video, the workflow most pros rely on for consistency. We put it head to head with Kling AI and Flow by Google VEO using the same reference images and prompts (below) to evaluate motion quality, stability, and cinematic realism. 1. Action/WaterPhysics Test Prompt: Cinematic, wide-shot of a man running in a shallow river. The camera is tracking the man from behind as he runs up the river. Handheld camera shake as the camera follows the man. 2. Fire Physics Test Prompt: Cinematic, wide-shot of terrified woman running towards her burning barn. She abruptly stops, and puts in hands on her head as she watches her barn burn down. 3. VFX test prompt: Cinematic, wide-shot of a hooded figure. Flashes of purple magic and smoke whirl around the figure. The figure lifts its arms as the purple magic and smoke intensifies. 4. 2D Animation Test Prompt: 2D animated shot of a waiting at a bus stop in a thunderstorm. The man turns, walks to the bench, and sits down. 5. 3D Animation Test Prompt: 3D animated shot of an octopus. The octopus reaches into a coral and picks up a glowing white gem. 6. Conversation Test Prompt: slow camera push-in as two friends are having a conversation at a coffee shop Overall verdict: Despite the “world’s best” claim, Runway Gen 4.5 is not there yet. Prompt adherence is solid, but motion, physics, and cinematic realism still lag behind tools like Kling and VEO. Great platform, mid-tier model for now.

So Runway Gen 4.5 finally adds image-to-video, the workflow most pros rely on for consistency. We put it head to head with Kling AI and Flow by Google VEO using the same reference images and prompts (below) to evaluate motion quality, stability, and cinematic realism. 1. Action/WaterPhysics Test Prompt: Cinematic, wide-shot of a man running in a shallow river. The camera is tracking the man from behind as he runs up the river. Handheld camera shake as the camera follows the man. 2. Fire Physics Test Prompt: Cinematic, wide-shot of terrified woman running towards her burning barn. She abruptly stops, and puts in hands on her head as she watches her barn burn down. 3. VFX test prompt: Cinematic, wide-shot of a hooded figure. Flashes of purple magic and smoke whirl around the figure. The figure lifts its arms as the purple magic and smoke intensifies. 4. 2D Animation Test Prompt: 2D animated shot of a waiting at a bus stop in a thunderstorm. The man turns, walks to the bench, and sits down. 5. 3D Animation Test Prompt: 3D animated shot of an octopus. The octopus reaches into a coral and picks up a glowing white gem. 6. Conversation Test Prompt: slow camera push-in as two friends are having a conversation at a coffee shop Overall verdict: Despite the “world’s best” claim, Runway Gen 4.5 is not there yet. Prompt adherence is solid, but motion, physics, and cinematic realism still lag behind tools like Kling and VEO. Great platform, mid-tier model for now.

Curious Refuge

25,538 次观看 • 6 个月前

THIS GUY SPENT 5 MINUTES SETTING UP A $20 CLAUDE WORKSPACE AND TURNED 30 MINUTES OF DAILY PROMPT CHAOS INTO A SYSTEM Most people open Claude, type 1 messy prompt, rewrite it 10 times, get the same generic answer and call the model “bad.” He opens Claude Cowork, adds the project rules, past context, working files, examples, decisions and a clean place for the model to remember what it is doing. Same Claude. Same $20 tool. Completely different output. The funny part is there is no magic prompt here. No secret template. No “10x Claude” trick. Just the boring layer Karpathy keeps pointing at: context, memory and structure before output. A setup like this can save 30 minutes a day, which is 15 hours a month. If you use Claude for client work at $50 to $100/hour, that is $750 to $1,500/month in time you stop burning on repeated prompts. The model is real. The output is real. The edge is in not making Claude start from zero every single time.

THIS GUY SPENT 5 MINUTES SETTING UP A $20 CLAUDE WORKSPACE AND TURNED 30 MINUTES OF DAILY PROMPT CHAOS INTO A SYSTEM Most people open Claude, type 1 messy prompt, rewrite it 10 times, get the same generic answer and call the model “bad.” He opens Claude Cowork, adds the project rules, past context, working files, examples, decisions and a clean place for the model to remember what it is doing. Same Claude. Same $20 tool. Completely different output. The funny part is there is no magic prompt here. No secret template. No “10x Claude” trick. Just the boring layer Karpathy keeps pointing at: context, memory and structure before output. A setup like this can save 30 minutes a day, which is 15 hours a month. If you use Claude for client work at $50 to $100/hour, that is $750 to $1,500/month in time you stop burning on repeated prompts. The model is real. The output is real. The edge is in not making Claude start from zero every single time.

Gipp 🦅

14,871 次观看 • 2 个月前

i built a way to make full ai films with seedance 2.5 + higgsfield without shooting a single frame in real life you start with a screenplay, a treatment, or even just an idea and it gives you an actual production plan: scenes, shots, character references, locations, dialogue, b-roll, sound, captions, everything you need to turn it into a finished film this was supposed to stay internal but f*ck it, i’m sharing the whole workflow here’s how it works: the script gets broken down scene by scene, then every scene gets turned into a proper shot list with prompts that account for character continuity, wardrobe, lighting, locations, camera movement, pacing, and what needs to happen before and after that shot those prompts get run through seedance 2.5, using reference assets and longer generations to keep the film feeling like one world instead of a thousand random ai clips stitched together then the footage gets assembled with voice, sound design, music, dialogue, captions, and transitions into an actual watchable film the whole system is built to take you from script to a finished film seedance 2.5 is coming soon on higgsfield, but i’m sharing the full breakdown before it so you can be prepared: the script-to-scene system that turns a screenplay into a real production plan seedance 2.5 prompt setup for cinematic shots and consistent characters the reference-asset workflow for keeping faces, wardrobe, locations, and visual style locked in the editing, voice, sound, and caption workflow that turns generated clips into a finished movie RT + reply “FILM” and (i’ll send it over must follow so i can dm)

i built a way to make full ai films with seedance 2.5 + higgsfield without shooting a single frame in real life you start with a screenplay, a treatment, or even just an idea and it gives you an actual production plan: scenes, shots, character references, locations, dialogue, b-roll, sound, captions, everything you need to turn it into a finished film this was supposed to stay internal but f*ck it, i’m sharing the whole workflow here’s how it works: the script gets broken down scene by scene, then every scene gets turned into a proper shot list with prompts that account for character continuity, wardrobe, lighting, locations, camera movement, pacing, and what needs to happen before and after that shot those prompts get run through seedance 2.5, using reference assets and longer generations to keep the film feeling like one world instead of a thousand random ai clips stitched together then the footage gets assembled with voice, sound design, music, dialogue, captions, and transitions into an actual watchable film the whole system is built to take you from script to a finished film seedance 2.5 is coming soon on higgsfield, but i’m sharing the full breakdown before it so you can be prepared: the script-to-scene system that turns a screenplay into a real production plan seedance 2.5 prompt setup for cinematic shots and consistent characters the reference-asset workflow for keeping faces, wardrobe, locations, and visual style locked in the editing, voice, sound, and caption workflow that turns generated clips into a finished movie RT + reply “FILM” and (i’ll send it over must follow so i can dm)

Sulfur

48,323 次观看 • 7 天前

ByteDance released an official Seedance 2.5 prompt guide and most people still don't know it exists i turned the whole thing into a Claude skill by the time Seedance 2.5 hits every platform your claude will already be an expert at every prompting style the official ByteDance team uses, while everyone else starts from zero 30 seconds to install, then you just describe what you want • ultra realistic travel vlogs, same face in every location • cinematics that hold 4 characters without drifting • meta ads that don't read as AI • swap the product in a winning ad, every cut identical • bullet time, FPV, one-take, dolly zoom, all named in the spec 23 task types, 67 templates, straight from ByteDance and sitting inside your claude comment 'SEEDANCE' and ill send you the skill i built (must be following so the dm goes through)

ByteDance released an official Seedance 2.5 prompt guide and most people still don't know it exists i turned the whole thing into a Claude skill by the time Seedance 2.5 hits every platform your claude will already be an expert at every prompting style the official ByteDance team uses, while everyone else starts from zero 30 seconds to install, then you just describe what you want • ultra realistic travel vlogs, same face in every location • cinematics that hold 4 characters without drifting • meta ads that don't read as AI • swap the product in a winning ad, every cut identical • bullet time, FPV, one-take, dolly zoom, all named in the spec 23 task types, 67 templates, straight from ByteDance and sitting inside your claude comment 'SEEDANCE' and ill send you the skill i built (must be following so the dm goes through)

zero

125,138 次观看 • 7 天前

i built a way to generate realistic AI influencer vlogs without ever touching a camera. this was supposed to stay internal but f*ck it, i'm leaking the entire production system. pick any topic. or paste in a script. a few minutes later you've got a finished influencer-style vlog with: > a consistent AI character > cinematic shots > natural dialogue > realistic iPhone footage > b-roll here's how it works: the workflow first breaks your script into a complete scene-by-scene storyboard with timestamps, camera directions, dialogue, environments, pacing, and shot planning so every clip has a purpose instead of feeling randomly generated. each scene gets its own reference image prompt for Higgsfield that locks the character's identity, clothing, camera angle, lighting, and environment to keep the person looking the same across the entire vlog. those reference images are then animated in Seedance 2.5 using scene-specific prompts that control movement, lip sync, ambient audio, dialogue, camera motion, and timing so every clip feels like it was filmed on an iPhone instead of generated by AI. finally everything gets assembled in CapCut with b-roll, subtitles, transitions, music, pacing, and final polish into a complete vlog that's ready to upload. you're not filming,hiring actors or recording voiceovers. the whole thing goes from idea → finished AI influencer vlog. the document i'm sharing includes: > the complete scene breakdown framework > every Higgsfield image prompt > every Seedance 2.5 animation prompt > dialogue for every scene > b-roll prompts > editing workflow inside capcut > structural notes that make the vlog feel real instead of AI RT + reply "AI VLOG", i'll DM you the entire production blueprint.(must be following so i can DM.)

i built a way to generate realistic AI influencer vlogs without ever touching a camera. this was supposed to stay internal but f*ck it, i'm leaking the entire production system. pick any topic. or paste in a script. a few minutes later you've got a finished influencer-style vlog with: > a consistent AI character > cinematic shots > natural dialogue > realistic iPhone footage > b-roll here's how it works: the workflow first breaks your script into a complete scene-by-scene storyboard with timestamps, camera directions, dialogue, environments, pacing, and shot planning so every clip has a purpose instead of feeling randomly generated. each scene gets its own reference image prompt for Higgsfield that locks the character's identity, clothing, camera angle, lighting, and environment to keep the person looking the same across the entire vlog. those reference images are then animated in Seedance 2.5 using scene-specific prompts that control movement, lip sync, ambient audio, dialogue, camera motion, and timing so every clip feels like it was filmed on an iPhone instead of generated by AI. finally everything gets assembled in CapCut with b-roll, subtitles, transitions, music, pacing, and final polish into a complete vlog that's ready to upload. you're not filming,hiring actors or recording voiceovers. the whole thing goes from idea → finished AI influencer vlog. the document i'm sharing includes: > the complete scene breakdown framework > every Higgsfield image prompt > every Seedance 2.5 animation prompt > dialogue for every scene > b-roll prompts > editing workflow inside capcut > structural notes that make the vlog feel real instead of AI RT + reply "AI VLOG", i'll DM you the entire production blueprint.(must be following so i can DM.)

Sulfur

70,956 次观看 • 4 天前

The biggest mistake people make with Seedance 2.0 is writing prompts at all. Sounds strange, but the model wasn't built for describing things in words - it was built for multimodal direction: up to 12 references at once, combining images, video, and audio. Each reference type controls a different layer: the image sets the style, the video defines the camera movement, the audio sets the rhythm of the scene. When you combine all three instead of typing "camera slowly pushes in, tense atmosphere" - the model understands it directly, with no interpretation and no guessing involved. Text is the weakest control tool available here. And most users are stuck using exactly that.

The biggest mistake people make with Seedance 2.0 is writing prompts at all. Sounds strange, but the model wasn't built for describing things in words - it was built for multimodal direction: up to 12 references at once, combining images, video, and audio. Each reference type controls a different layer: the image sets the style, the video defines the camera movement, the audio sets the rhythm of the scene. When you combine all three instead of typing "camera slowly pushes in, tense atmosphere" - the model understands it directly, with no interpretation and no guessing involved. Text is the weakest control tool available here. And most users are stuck using exactly that.

Zentrix⌚️

72,877 次观看 • 25 天前

I found a Claude prompt that turns one product into an entire month of AI ads. I paste: → the product → the target audience → 5 winning ads and it gives me: • 30 unique hooks • multiple high-converting scripts • different marketing angles • CTAs • scene-by-scene prompts for Gemini Omni it's basically like having a copywriter and a creative strategist in one chat. I don't do creative research every day anymore. I do it once, then let this build everything from there. RT + comment "AI" and I'll DM you the exact prompt I use. (must be following for DM)

I found a Claude prompt that turns one product into an entire month of AI ads. I paste: → the product → the target audience → 5 winning ads and it gives me: • 30 unique hooks • multiple high-converting scripts • different marketing angles • CTAs • scene-by-scene prompts for Gemini Omni it's basically like having a copywriter and a creative strategist in one chat. I don't do creative research every day anymore. I do it once, then let this build everything from there. RT + comment "AI" and I'll DM you the exact prompt I use. (must be following for DM)

Bruno

16,205 次观看 • 13 天前

We generated this scene with just one trial on Seedance Enterprise 2.5. We had run this same shot on other models and it took us around 8 attempts before anything came back usable. Generations are billed one at a time so 8 tries to 1 is the entire cost story. 30 seconds, single shot, no stitching, what used to be a day of rerolling is now a single pass, which means the budget goes into testing new concepts instead of rescuing one. Watch the water as the creature moves through it, and watch the camera fall behind during the escape. The realistic physics, smooth camera motion, and shot consistency all came directly from the model.None of that was added in post. We used Seedream 5.0 for the visual ideation and Seedance 2.5 for the video. Both are running on lumina at 4K, up to 50 references to hold a character or product steady across a shot, and region editing to fix one part of a frame without regenerating the whole thing. Seedance 2.5 API is about to launch on BytePlus, and now you can try it directly on Lumina.

We generated this scene with just one trial on Seedance Enterprise 2.5. We had run this same shot on other models and it took us around 8 attempts before anything came back usable. Generations are billed one at a time so 8 tries to 1 is the entire cost story. 30 seconds, single shot, no stitching, what used to be a day of rerolling is now a single pass, which means the budget goes into testing new concepts instead of rescuing one. Watch the water as the creature moves through it, and watch the camera fall behind during the escape. The realistic physics, smooth camera motion, and shot consistency all came directly from the model.None of that was added in post. We used Seedream 5.0 for the visual ideation and Seedance 2.5 for the video. Both are running on lumina at 4K, up to 50 references to hold a character or product steady across a shot, and region editing to fix one part of a frame without regenerating the whole thing. Seedance 2.5 API is about to launch on BytePlus, and now you can try it directly on Lumina.

Future Stacked

86,132 次观看 • 7 天前

how to use Google's NEW open source Design.md + AI Skills to make your startup look like a $100 million company in 1 hour: 1. Design.md is an open source file from Google that captures the soul of a design. Typography, colors, spacing, all in one markdown file. You attach it to your prompt and your agent builds beautiful things every time. 2. Think of it this way. The HTML is the finished dish. The design.md is the recipe. The skills are the ingredients. Put them together and everything you build looks consistent and professional. 3. Don't create a design system from scratch. Find a brand you love. Linear, Stripe, Vercel, whatever resonates. Study it. Use ChatGPT or Claude to help you extract the design language into your own design.md file. 4. Build skills on top of your design.md. A landing page skill. A mobile app skill. A motion design skill. A slide deck skill. Each one references the same design.md so everything looks like it came from the same designer. 5. The biggest mistake people make: they nail one screen and then everything else looks generic. Design.md solves this. One file keeps every page, every format, every medium consistent. 6. Use it across everything. Your landing page. Your app. Your pitch deck. Your promo videos. Same DNA. Same taste. Same system. That's what separates a startup that looks real from one that looks vibe-coded. 7. Build a second brain for design inspiration. When you see something beautiful in the real world or online, capture it. Save it. When you're building something new, reference it. Taste is developed, not downloaded. 8. It's obvious but the difference between a product people trust and a product people bounce from is how it looks and feels. Design.md gives you that edge. you can watch below shoutout to Meng To for coming on The Startup Ideas Podcast (SIP) 🧃 and walking through his full workflow. if you want to use AI to actually build gorgeous designs, you'll want to use see this. watch

GREG ISENBERG

508,512 次观看 • 3 个月前

How to set up Claude Cowork so it actually works like an AI chief of staff (not just another chatbot): 1. Most people open Cowork, type a message, and get generic output. It's not a Claude problem. It's a setup problem. Cowork needs context before it can help you. Who you are. How you work. What you're building. Your team. Your priorities. Give it that, and every session feels like picking up a conversation with an executive assistant. 2. The setup has three layers: a) Global instructions (who you are, how you work, what Claude should never do). b) Connectors (Slack, Gmail, Google Calendar, Notion) c) And a folder structure on your computer that acts as Claude's long-term memory. That combination is what takes it from generic to personalized. 3. Skills are the real leverage. A skill is a markdown file that tells Claude exactly how to do one thing well. Write my newsletter. Coach me on a decision. Review a case study. Each skill lives in its own folder with context, examples, and a definition of what success looks like. 4. We built a CEO coach skill in the video below. Gave it business context, leadership style, company goals. Then tested it with a real decision: should we increase our newsletter from once to twice a week? It came back with trade-offs, second-order consequences, and risk assessment. 5. Then we built a multi-agent advisory board. Five subagents, each with a defined persona: a) the operator b) the skeptic c) the customer advocate d) the finance partner e) the legal/risk advisor. You feed it a decision. Each agent evaluates independently. The main agent synthesizes the feedback. It's like having a board meeting on demand. 6. Third skill: a thought leadership content pipeline. Topic scoring, idea capture, distribution cadence, tone calibration. All built from your actual expertise and audience. Designed so an executive can go from idea to published post without starting from scratch every time. 7. The workspace map is what ties it all together. It's a top-level file that shows Claude how to navigate your entire setup. Which folders exist, what skills live where, how to invoke them. Without it, Claude has to search for everything. With it, Claude goes straight to what it needs. 8. Everything you build is portable. The folder structure works in Cowork, Claude Code, and Codex. Push it to a private GitHub repo and you can access it from your phone through Claude Code, or use Claude Dispatch. 9. The pattern is repeatable. Pick a task you do often. Create a folder. Build a skill. Add examples of what success looks like, and what a bad output looks like. Test it. Workshop it. Move on to the next one. Each skill is like onboarding a new employee who never forgets and never needs to be re-trained. The people who invest in this setup now are the ones who will have a 10x advantage when these tools get even better. And they're getting better fast. I sat down with Alex Lieberman on Human In The Loop and we built all three of these live from scratch. Full breakdown in the video below.. I tried to explain this as clear as possible for my non-developer crowd. Send it to someone who should be using Cowork but isn't yet. Or bookmark it to level up when you're ready. Watch 👇🏼

How to set up Claude Cowork so it actually works like an AI chief of staff (not just another chatbot): 1. Most people open Cowork, type a message, and get generic output. It's not a Claude problem. It's a setup problem. Cowork needs context before it can help you. Who you are. How you work. What you're building. Your team. Your priorities. Give it that, and every session feels like picking up a conversation with an executive assistant. 2. The setup has three layers: a) Global instructions (who you are, how you work, what Claude should never do). b) Connectors (Slack, Gmail, Google Calendar, Notion) c) And a folder structure on your computer that acts as Claude's long-term memory. That combination is what takes it from generic to personalized. 3. Skills are the real leverage. A skill is a markdown file that tells Claude exactly how to do one thing well. Write my newsletter. Coach me on a decision. Review a case study. Each skill lives in its own folder with context, examples, and a definition of what success looks like. 4. We built a CEO coach skill in the video below. Gave it business context, leadership style, company goals. Then tested it with a real decision: should we increase our newsletter from once to twice a week? It came back with trade-offs, second-order consequences, and risk assessment. 5. Then we built a multi-agent advisory board. Five subagents, each with a defined persona: a) the operator b) the skeptic c) the customer advocate d) the finance partner e) the legal/risk advisor. You feed it a decision. Each agent evaluates independently. The main agent synthesizes the feedback. It's like having a board meeting on demand. 6. Third skill: a thought leadership content pipeline. Topic scoring, idea capture, distribution cadence, tone calibration. All built from your actual expertise and audience. Designed so an executive can go from idea to published post without starting from scratch every time. 7. The workspace map is what ties it all together. It's a top-level file that shows Claude how to navigate your entire setup. Which folders exist, what skills live where, how to invoke them. Without it, Claude has to search for everything. With it, Claude goes straight to what it needs. 8. Everything you build is portable. The folder structure works in Cowork, Claude Code, and Codex. Push it to a private GitHub repo and you can access it from your phone through Claude Code, or use Claude Dispatch. 9. The pattern is repeatable. Pick a task you do often. Create a folder. Build a skill. Add examples of what success looks like, and what a bad output looks like. Test it. Workshop it. Move on to the next one. Each skill is like onboarding a new employee who never forgets and never needs to be re-trained. The people who invest in this setup now are the ones who will have a 10x advantage when these tools get even better. And they're getting better fast. I sat down with Alex Lieberman on Human In The Loop and we built all three of these live from scratch. Full breakdown in the video below.. I tried to explain this as clear as possible for my non-developer crowd. Send it to someone who should be using Cowork but isn't yet. Or bookmark it to level up when you're ready. Watch 👇🏼

JJ Englert

569,800 次观看 • 4 个月前