Video yükleniyor...

Video Yüklenemedi

Bu video yüklenirken bir sorun oluştu. Bu geçici bir ağ sorunundan kaynaklanıyor olabilir veya video kullanılamıyor olabilir.

Ana Sayfaya Dön

Ling-3.0-flash is built as a fast, reliable execution engine for agent workflows. It shines in long-running tasks, tool calling, and high-volume production work where speed and stability matter more than massive reasoning depth. At 124B parameters with only 5.1B active, it keeps costs low while delivering quick responses and... strong instruction following I ran a practical task using Ling-3.0-flash capabilities (based on its documented agent strengths in coding and tool use). Real Test Run I tested Ling-3.0-flash on a content creation task that matches your workflow. I asked it to generate a short, viral-style YouTube Shorts script for football highlights, including captions, title suggestions, and thumbnail ideas. Input Prompt: "Create a 30-second YouTube Shorts script for a dramatic Ronaldo goal from the 2026 World Cup qualifiers. Include engaging English narration, 3 multilingual caption versions (English, Spanish, Portuguese), a catchy title, and thumbnail description. Make it feel real and exciting for football fans." Process: The model first outlined the structure: intro hook, key action description, emotional peak, and call to action. It generated the script, then created caption variants, optimized the title for clicks, and suggested a thumbnail layout. It handled iterations well when I asked for adjustments, such as making it more dramatic or adding player stats. Total interaction took under 2 minutes with low token use. Result: - Script: Solid, ready-to-record narration with natural flow. - Captions: High-quality and culturally adapted. - Title & Thumbnail: Click-worthy and on brand. This demonstrates its strength for creators who need fast, high-quality content assets. Official account : Demo:show more

Pee✌️💜

1,682 subscribers

22,488 görüntüleme • 25 gün önce •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

I went a little overboard with Codex last week and burned through my entire weekly allowance in two days. Luckily, my quota reset today. Otherwise, I’m not sure what I would’ve done. It got me thinking: instead of asking one large model to handle everything from start to finish, why not let a stronger model plan the project and review the work, while a model built for execution handles the day-to-day implementation? So I tried it. The result was better than I expected. I used GPT-5.6 Sol in Codex as the decision-maker, then ran Ling-3.0-flash from Ant Ling inside OpenCode as the execution engine. Together, they built a small 3D farming game. Before writing any code, I had Codex create four documents: SPEC.md defined the product scope and the lines we couldn’t cross. ARCHITECTURE.md laid out the isometric coordinate system, state machine, and module boundaries. TASKS.md broke the project into small jobs Ling could tackle one at a time. ACCEPTANCE.md explained how each step would be tested and what “done” actually meant. Then I gave Ling a very straightforward role: You are the execution model for this project. Read all four documents before you begin. Work only on the task assigned for this round. When you’re done, run typecheck, test, and build. If anything fails, read the error, fix it, and run the checks again. Do not move on to the next task early. Ling handled dependency installation, project structure, strict TypeScript configuration, test setup, and a production build in 6 minutes and 3 seconds. It ran into issues with the Vite test config, a TS6310 error, and a missing jsdom dependency along the way. Instead of stopping at the first error, it kept reading the logs and fixing the problems until all three checks passed. The speed was honestly hard to believe. If you exclude the time spent waiting on tools, it was producing more than 100 tokens per second. That made the whole development loop feel noticeably faster. After this experiment, I’m planning to keep using the same workflow. If the task is small, there’s no reason to call an expensive planning model for every single step. If the task is large, handing the entire project to a Flash model in one prompt isn’t a great idea either. The setup that makes more sense to me is: Use a more capable model such as Codex to explore the project, make architectural decisions, and break the work down. Put the constraints into specs, schemas, types, and tests instead of leaving them buried in chat history. Give Ling-3.0-flash a steady stream of clear, verifiable implementation tasks. Report bugs with structured context and actual error logs, rather than saying, “It still doesn’t work.” Bring Codex back in for architecture reviews, visual checks, and changes that affect multiple parts of the project. The point of this setup isn’t to give AI a big “build the whole project” button. It’s to turn software development into a pipeline with a much more sensible cost structure: Codex figures out the plan, sets the boundaries, and catches problems. Ling-3.0-flash moves quickly, calls tools reliably, and works through well-defined tasks at scale. For agent workflows that involve lots of repetitive edits, production tasks, and tool calls, this may be a more practical answer than simply using the biggest model for everything.

I went a little overboard with Codex last week and burned through my entire weekly allowance in two days. Luckily, my quota reset today. Otherwise, I’m not sure what I would’ve done. It got me thinking: instead of asking one large model to handle everything from start to finish, why not let a stronger model plan the project and review the work, while a model built for execution handles the day-to-day implementation? So I tried it. The result was better than I expected. I used GPT-5.6 Sol in Codex as the decision-maker, then ran Ling-3.0-flash from Ant Ling inside OpenCode as the execution engine. Together, they built a small 3D farming game. Before writing any code, I had Codex create four documents: SPEC.md defined the product scope and the lines we couldn’t cross. ARCHITECTURE.md laid out the isometric coordinate system, state machine, and module boundaries. TASKS.md broke the project into small jobs Ling could tackle one at a time. ACCEPTANCE.md explained how each step would be tested and what “done” actually meant. Then I gave Ling a very straightforward role: You are the execution model for this project. Read all four documents before you begin. Work only on the task assigned for this round. When you’re done, run typecheck, test, and build. If anything fails, read the error, fix it, and run the checks again. Do not move on to the next task early. Ling handled dependency installation, project structure, strict TypeScript configuration, test setup, and a production build in 6 minutes and 3 seconds. It ran into issues with the Vite test config, a TS6310 error, and a missing jsdom dependency along the way. Instead of stopping at the first error, it kept reading the logs and fixing the problems until all three checks passed. The speed was honestly hard to believe. If you exclude the time spent waiting on tools, it was producing more than 100 tokens per second. That made the whole development loop feel noticeably faster. After this experiment, I’m planning to keep using the same workflow. If the task is small, there’s no reason to call an expensive planning model for every single step. If the task is large, handing the entire project to a Flash model in one prompt isn’t a great idea either. The setup that makes more sense to me is: Use a more capable model such as Codex to explore the project, make architectural decisions, and break the work down. Put the constraints into specs, schemas, types, and tests instead of leaving them buried in chat history. Give Ling-3.0-flash a steady stream of clear, verifiable implementation tasks. Report bugs with structured context and actual error logs, rather than saying, “It still doesn’t work.” Bring Codex back in for architecture reviews, visual checks, and changes that affect multiple parts of the project. The point of this setup isn’t to give AI a big “build the whole project” button. It’s to turn software development into a pipeline with a much more sensible cost structure: Codex figures out the plan, sets the boundaries, and catches problems. Ling-3.0-flash moves quickly, calls tools reliably, and works through well-defined tasks at scale. For agent workflows that involve lots of repetitive edits, production tasks, and tool calls, this may be a more practical answer than simply using the biggest model for everything.

雪踏乌云

23,107 görüntüleme • 25 gün önce

20 days ago, I connected Claude Code to my newly created instagram handle.. I gained 4.3M views and 6500+ followers in less than a month [ i post Ai generated animated stories ] Full workflow: i let claude study my account before i write another reel.. This is the cleanest content workflow i've built on claude. give it your IG first. 4 prompts handle the rest.. niche research, the reel script, the hook, and the daily automation.. the whole loop is basically, give claude your IG → find what's working → write retention-optimized scripts → engineer the hook → automate the daily output.. ▫️ Setup: give claude your instagram open claude code. claude code has a built-in web tool that browses any public URL. or install any agentic browser like Browser Harness or Firecrawl or Comet browser paste this with your handle filled in: "Browse and pull the last 30 reels and posts. Analyze my recurring topics, top-performing hooks, formats, and engagement patterns. Then map out my actual audience and what they consistently respond to." claude reads your profile, pulls every reel down, and now has the context to personalize every prompt below to YOUR account, not a generic niche. if you're on claude desktop, the same works with firecrawl MCP connected. ▫️ Prompt 1 find what actually goes viral in your niche: "Analyze the highest-performing Instagram Reels, TikToks, and Reddit posts in the [niche] niche from the last 30 days. Identify repeating hooks, visual styles, emotional triggers, and content formats that consistently generate high engagement. Then summarize the 5 strongest content angles optimized for AI-generated content and short-form videos." run this after the setup. you get 5 angles backed by what's already working in your niche, cross-checked against what's already working on YOUR account. ▫️ Prompt 2 write a high-retention reel script "Write a short-form Instagram Reel script about [topic] with an aggressive hook in the first 2 seconds. Create immediate curiosity, tension, or controversy to stop scrolling, then deliver a fast and satisfying payoff. Keep it under 30 seconds and optimize the structure for watch time, replays, comments, and shares. Finish with a subtle CTA." the line that matters: "optimize the structure for watch time, replays, comments, and shares." claude writes for the metrics, not just the word count. ▫️ Prompt 3 engineer better hooks "Study the top-performing Reels in [niche] and break down the hook structure, pacing, and emotional triggers used in the first 3 seconds. Then generate 5 new hook variations that are even more curiosity-driven, emotionally charged, and optimized to stop scrolling instantly. Focus on triggers like surprise, fear, ego, urgency, or desire." most reels die in the first 2 seconds. this prompt has claude reverse-engineer what already works, then give you 5 sharper versions to swap in. ▫️ Prompt 4 automate the whole workflow "Build a complete AI-powered content workflow for Instagram in the [niche] niche. The system should identify trending topics daily, generate high-retention scripts, create matching AI visuals, turn them into short-form videos, and generate optimized captions and hashtags. Structure everything as a repeatable workflow designed for consistent daily posting and growth." once the niche and script structure are validated, this turns it into a daily loop. one prompt that handles topic → script → visual → video → caption. these 4 prompts are the building blocks. the setup is what makes them yours. your real value is in the [niche] you plug in. content workflow built in one weekend, daily posting on autopilot from monday.

Axel Bitblaze 🪓

199,569 görüntüleme • 2 ay önce

GPT-5.5 is MUCH more reliable on longer running tasks - for the first time with any model. As we speak I have a migration running for over 7+ hours - this literally never happened before, the models would maybe run for 30 mins or of you really shout at them for 2-3 hours. Last night I went to sleep, set a long running task, then queued up 10 prompts to 'keep it going'. It did not stop after the first prompt and kept going for 8+ hours and I woke up to all the same prompts still queued up. The ability to run for a long time, in combination with ability to validate with computer use & other tools, makes it much more useful for building real applications.

GPT-5.5 is MUCH more reliable on longer running tasks - for the first time with any model. As we speak I have a migration running for over 7+ hours - this literally never happened before, the models would maybe run for 30 mins or of you really shout at them for 2-3 hours. Last night I went to sleep, set a long running task, then queued up 10 prompts to 'keep it going'. It did not stop after the first prompt and kept going for 8+ hours and I woke up to all the same prompts still queued up. The ability to run for a long time, in combination with ability to validate with computer use & other tools, makes it much more useful for building real applications.

Peter Gostev

105,642 görüntüleme • 3 ay önce

How I use Claude Code and Remotion to make animated diagrams. Sorry, it's not a single prompt. 1. Find an input language the model knows well. For example, Mermaid for flowcharts. Claude writes it fluently, so it's my entry point. 2. Use Claude to build components that take that input and bake in the guardrails: design system, animation patterns, layout rules. 3. Now I can describe what I want in plain English e.g. "create a flowchart for the tier check section in the script", and Claude translates it to our input language: ``` flowchart TD t1[Tier 1 read-only] t2[Tier 2 in-project writes] t3[Tier 3 everything else] action[Action] --> t1 action --> t2 action --> t3 t1 --> skip([Skips classifier]) t2 --> skip t3 --> classifier{Classifier} classifier --> approve[Approve] classifier --> deny[Deny] ``` The component handles the rest: layout, styling, node and edge reveals. It also takes events for follow-ups like the trace dot that follows a path and lights up nodes. 4. To finish it off, I wrapped the board in a separate CRT shader component. It really helps to have a shared vocabulary with your agent. When I say "rise in fast on enter", it knows I mean fade in while translating up, from a set offset, faster than the default duration, with a specific bezier curve. For common language inspo: look into Matt Pocock `/grill-with-docs` and by Emil Kowalski and Glenn Hitchcock.

How I use Claude Code and Remotion to make animated diagrams. Sorry, it's not a single prompt. 1. Find an input language the model knows well. For example, Mermaid for flowcharts. Claude writes it fluently, so it's my entry point. 2. Use Claude to build components that take that input and bake in the guardrails: design system, animation patterns, layout rules. 3. Now I can describe what I want in plain English e.g. "create a flowchart for the tier check section in the script", and Claude translates it to our input language: ``` flowchart TD t1[Tier 1 read-only] t2[Tier 2 in-project writes] t3[Tier 3 everything else] action[Action] --> t1 action --> t2 action --> t3 t1 --> skip([Skips classifier]) t2 --> skip t3 --> classifier{Classifier} classifier --> approve[Approve] classifier --> deny[Deny] ``` The component handles the rest: layout, styling, node and edge reveals. It also takes events for follow-ups like the trace dot that follows a path and lights up nodes. 4. To finish it off, I wrapped the board in a separate CRT shader component. It really helps to have a shared vocabulary with your agent. When I say "rise in fast on enter", it knows I mean fade in while translating up, from a set offset, faster than the default duration, with a specific bezier curve. For common language inspo: look into Matt Pocock `/grill-with-docs` and by Emil Kowalski and Glenn Hitchcock.

Delba

61,247 görüntüleme • 2 ay önce

Big moment for text-to-speech. Qwen just open-sourced a text-to-speech model that lets you clone voices, design new ones, and control speech using natural language. Let me explain what I mean: You can literally tell it "speak in a cheerful tone with slight nervousness," and it actually does that. No complex audio engineering needed. What makes this special: - 3-second voice cloning - Covers 10 languages: English, German, French, and more - Latency as low as 97ms for real-time applications - Supports both streaming and non-streaming generation The model comes in two sizes (0.6B and 1.7B parameters), so you can pick based on your hardware and quality needs. Three modes to work with: 1. Custom Voice: Use pre-built premium voices with instruction-based style control 2. Voice Design: Describe the voice you want in plain English (or Chinese), and the model creates it 3. Voice Clone: Provide a 3-second reference audio and clone that voice The best part? It integrates with vLLM for production deployment and has a simple Python package you can pip install. I've shared a link to the GitHub repo in the next tweet.

Big moment for text-to-speech. Qwen just open-sourced a text-to-speech model that lets you clone voices, design new ones, and control speech using natural language. Let me explain what I mean: You can literally tell it "speak in a cheerful tone with slight nervousness," and it actually does that. No complex audio engineering needed. What makes this special: - 3-second voice cloning - Covers 10 languages: English, German, French, and more - Latency as low as 97ms for real-time applications - Supports both streaming and non-streaming generation The model comes in two sizes (0.6B and 1.7B parameters), so you can pick based on your hardware and quality needs. Three modes to work with: 1. Custom Voice: Use pre-built premium voices with instruction-based style control 2. Voice Design: Describe the voice you want in plain English (or Chinese), and the model creates it 3. Voice Clone: Provide a 3-second reference audio and clone that voice The best part? It integrates with vLLM for production deployment and has a simple Python package you can pip install. I've shared a link to the GitHub repo in the next tweet.

Akshay 🚀

31,249 görüntüleme • 6 ay önce

I tried MiniMax Design (H3) to see how it handles real content creation. The workflow is simple. You just write a prompt or drop in an image, and it turns that into a dynamic video with motion, framing, and scene depth. No timeline to manage. No editing setup. No back and forth. What stood out to me: • Text to video and image to video both feel smooth. • It handles motion, camera angles, and flow on its own. • Output is fast, usually within seconds. • Works well for reels, quick ads, storytelling, and idea testing. It removes the hardest part: starting from scratch and turns your ideas into content in minutes. Instead of thinking, “How do I make this video?” You start with, “What do I want to create?” That shift alone makes it worth exploring. Try it here: #Hailuo

I tried MiniMax Design (H3) to see how it handles real content creation. The workflow is simple. You just write a prompt or drop in an image, and it turns that into a dynamic video with motion, framing, and scene depth. No timeline to manage. No editing setup. No back and forth. What stood out to me: • Text to video and image to video both feel smooth. • It handles motion, camera angles, and flow on its own. • Output is fast, usually within seconds. • Works well for reels, quick ads, storytelling, and idea testing. It removes the hardest part: starting from scratch and turns your ideas into content in minutes. Instead of thinking, “How do I make this video?” You start with, “What do I want to create?” That shift alone makes it worth exploring. Try it here: #Hailuo

Manish Kumar Shah

27,680 görüntüleme • 4 ay önce

After a few more hours, I think I've figured out Opus 5. Opus 5 is trained to be more agentic than anything I've used. All Claude 5 models are like that. So what changes? The way to interact with Opus 5 or contextualize it won't work the same way as with other models. It loves exploring, so it doesn't need much guidance for it. Unique preferences, artifacts, and references compliment it well and enable cleaner and more effective exploration and execution. Now that it can explore more effectively on its own and understand intent better, the best thing to do is to get out of its way (e.g., it doesn't need examples of your preferences; a clear high-level description of it works best). It's truly agentic in that sense. A good first step to provide better context for Opus 5 is to distinguish between what's situational and what needs persistence. Regardless, persistent system prompts and CLAUDE.MD needs to stay lightweight. Remove memories and tool descriptions from these. CLAUDE.MD is also a great place to tap into progressive disclosure by linking command/skills to it. On the situational side, agent skills and auto-memory can leverage progressive disclosure and the improved ability of the model to use its external context/knowledge. Conflicting and unnecessary instructions, which are common at this layer (mainly to ensure reliability), are going to throw off this model easily. That's the biggest change I had to make. Simple, clean, and clear prompts and skills work best. I had to clean a lot of my skills and system prompts. The way I prompt remains the same (usually clear and well-scoped). MCP tool descriptions are also more descriptive and have been deduped from the system prompt. Anthropic released a guide on the new rules for context engineering, which was helpful here. I started to test the recommendations and created a little artifact with the things that worked along the way. This might feel like a lot of work. Believe me, it has been frustrating. But I think we can expect future frontier models to become more agentic and smarter at figuring out the right context/gaps. The best thing to do is to prepare for that now. Boris Cherny mentioned that Opus 5 is their least prompt-injectable model yet. I am not sure if that was something they intentionally trained for or if it emerged based on how it was trained, which is to be extremely agentic in nature and more direct in execution.

After a few more hours, I think I've figured out Opus 5. Opus 5 is trained to be more agentic than anything I've used. All Claude 5 models are like that. So what changes? The way to interact with Opus 5 or contextualize it won't work the same way as with other models. It loves exploring, so it doesn't need much guidance for it. Unique preferences, artifacts, and references compliment it well and enable cleaner and more effective exploration and execution. Now that it can explore more effectively on its own and understand intent better, the best thing to do is to get out of its way (e.g., it doesn't need examples of your preferences; a clear high-level description of it works best). It's truly agentic in that sense. A good first step to provide better context for Opus 5 is to distinguish between what's situational and what needs persistence. Regardless, persistent system prompts and CLAUDE.MD needs to stay lightweight. Remove memories and tool descriptions from these. CLAUDE.MD is also a great place to tap into progressive disclosure by linking command/skills to it. On the situational side, agent skills and auto-memory can leverage progressive disclosure and the improved ability of the model to use its external context/knowledge. Conflicting and unnecessary instructions, which are common at this layer (mainly to ensure reliability), are going to throw off this model easily. That's the biggest change I had to make. Simple, clean, and clear prompts and skills work best. I had to clean a lot of my skills and system prompts. The way I prompt remains the same (usually clear and well-scoped). MCP tool descriptions are also more descriptive and have been deduped from the system prompt. Anthropic released a guide on the new rules for context engineering, which was helpful here. I started to test the recommendations and created a little artifact with the things that worked along the way. This might feel like a lot of work. Believe me, it has been frustrating. But I think we can expect future frontier models to become more agentic and smarter at figuring out the right context/gaps. The best thing to do is to prepare for that now. Boris Cherny mentioned that Opus 5 is their least prompt-injectable model yet. I am not sure if that was something they intentionally trained for or if it emerged based on how it was trained, which is to be extremely agentic in nature and more direct in execution.

elvis

37,647 görüntüleme • 21 gün önce

This is the easiest way to make $10k/month with organic affiliate and AI Arcads launched an ai ugc studio that lets you build an entire army of hyper-real AI actors Then you turn any static image into a high-quality video showcasing any product go to TikTok and make an account + warm it up using arcads you can run an entirely AI UGC account using the same character over and over, making it seem like an authentic TT page Mix the content up with slideshows and videos with the same character Here's the AI stack gameplan: - Claude to help you write scripts - Arcads to generate an image of an AI girlie that fits your product demographic Scroll tiktok and save + download every video / slideshow you see made by clippers promoting a product (there's literally loads) Your going to find an offer on whop for making money online or spirituality and target it towards girls feed all these videos you scraped into a custom google gemini gem trained to deconstruct hooks / angles for you for easy hook inspiration + ideas Deconstruct the hooks, put them into Claude and ask it to give you hooks for the same style of video put for your products your promoting For the videos do caption and reaction + showcase formats Generate the reactions using the character you made in arc ads then manually record the showcasing of the product or proof of the product working Also for caption generate a 8-10 second video you can put text over Include your CTA in the video for reaction style and captions for caption style Plus generate images with the same character and make slideshows directed to your product Now rinse and repeat this make multiple accounts with multiple different avatars and print

This is the easiest way to make $10k/month with organic affiliate and AI Arcads launched an ai ugc studio that lets you build an entire army of hyper-real AI actors Then you turn any static image into a high-quality video showcasing any product go to TikTok and make an account + warm it up using arcads you can run an entirely AI UGC account using the same character over and over, making it seem like an authentic TT page Mix the content up with slideshows and videos with the same character Here's the AI stack gameplan: - Claude to help you write scripts - Arcads to generate an image of an AI girlie that fits your product demographic Scroll tiktok and save + download every video / slideshow you see made by clippers promoting a product (there's literally loads) Your going to find an offer on whop for making money online or spirituality and target it towards girls feed all these videos you scraped into a custom google gemini gem trained to deconstruct hooks / angles for you for easy hook inspiration + ideas Deconstruct the hooks, put them into Claude and ask it to give you hooks for the same style of video put for your products your promoting For the videos do caption and reaction + showcase formats Generate the reactions using the character you made in arc ads then manually record the showcasing of the product or proof of the product working Also for caption generate a 8-10 second video you can put text over Include your CTA in the video for reaction style and captions for caption style Plus generate images with the same character and make slideshows directed to your product Now rinse and repeat this make multiple accounts with multiple different avatars and print

Pounds

32,407 görüntüleme • 7 ay önce

Introducing ml-intern, the agent that just automated the post-training team Hugging Face It's an open-source implementation of the real research loop that our ML researchers do every day. You give it a prompt, it researches papers, goes through citations, implements ideas in GPU sandboxes, iterates and builds deeply research-backed models for any use case. All built on the Hugging Face ecosystem. It can pull off crazy things: We made it train the best model for scientific reasoning. It went through citations from the official benchmark paper. Found OpenScience and NemoTron-CrossThink, added 7 difficulty-filtered dataset variants from ARC/SciQ/MMLU, and ran 12 SFT runs on Qwen3-1.7B. This pushed the score 10% → 32% on GPQA in under 10h. Claude Code's best: 22.99%. In healthcare settings it inspected available datasets, concluded they were too low quality, and wrote a script to generate 1100 synthetic data points from scratch for emergencies, hedging, multilingual etc. Then upsampled 50x for training. Beat Codex on HealthBench by 60%. For competitive mathematics, it wrote a full GRPO script, launched training with A100 GPUs on watched rewards claim and then collapse, and ran ablations until it succeeded. All fully backed by papers, autonomously. How it works? ml-intern makes full use of the HF ecosystem: - finds papers on arxiv and reads them fully, walks citation graphs, pulls datasets referenced in methodology sections and on - browses the Hub, reads recent docs, inspects datasets and reformats them before training so it doesn't waste GPU hours on bad data - launches training jobs on HF Jobs if no local GPUs are available, monitors runs, reads its own eval outputs, diagnoses failures, retrains ml-intern deeply embodies how researchers work and think. It knows how data should look like and what good models feel like. Releasing it today as a CLI and a web app you can use from your phone/desktop. CLI: Web + mobile: And the best part? We also provisioned 1k$ GPU resources and Anthropic credits for the quickest among you to use.

Introducing ml-intern, the agent that just automated the post-training team Hugging Face It's an open-source implementation of the real research loop that our ML researchers do every day. You give it a prompt, it researches papers, goes through citations, implements ideas in GPU sandboxes, iterates and builds deeply research-backed models for any use case. All built on the Hugging Face ecosystem. It can pull off crazy things: We made it train the best model for scientific reasoning. It went through citations from the official benchmark paper. Found OpenScience and NemoTron-CrossThink, added 7 difficulty-filtered dataset variants from ARC/SciQ/MMLU, and ran 12 SFT runs on Qwen3-1.7B. This pushed the score 10% → 32% on GPQA in under 10h. Claude Code's best: 22.99%. In healthcare settings it inspected available datasets, concluded they were too low quality, and wrote a script to generate 1100 synthetic data points from scratch for emergencies, hedging, multilingual etc. Then upsampled 50x for training. Beat Codex on HealthBench by 60%. For competitive mathematics, it wrote a full GRPO script, launched training with A100 GPUs on watched rewards claim and then collapse, and ran ablations until it succeeded. All fully backed by papers, autonomously. How it works? ml-intern makes full use of the HF ecosystem: - finds papers on arxiv and reads them fully, walks citation graphs, pulls datasets referenced in methodology sections and on - browses the Hub, reads recent docs, inspects datasets and reformats them before training so it doesn't waste GPU hours on bad data - launches training jobs on HF Jobs if no local GPUs are available, monitors runs, reads its own eval outputs, diagnoses failures, retrains ml-intern deeply embodies how researchers work and think. It knows how data should look like and what good models feel like. Releasing it today as a CLI and a web app you can use from your phone/desktop. CLI: Web + mobile: And the best part? We also provisioned 1k$ GPU resources and Anthropic credits for the quickest among you to use.

Aksel

1,266,405 görüntüleme • 4 ay önce

People assume creating a premium brand film means hiring a production crew and spending thousands on a single 15-second spot. I've been testing Pippit with the new Seedance 2.0 Mini model to see if it could handle something as high-detail as a luxury watch. Most AI struggles with the reflections and mechanical movement of a timepiece, but the output here is actually publish-ready. The real advantage for marketing teams is how this changes the workflow. Instead of treating every asset like a heavy production task, you can move from a text prompt to a cinematic brand film in minutes. It makes it much more practical to produce high-end content at scale without blowing the budget—it's roughly $0.02 per second to get this level of quality. Seedance 2.0 Mini is a massive shortcut for anyone needing to iterate faster on premium visuals without the usual studio costs. There is a limited-time deal if you want to try it out: #PippitAI #Seedancemini #PippitPartner #AIads Pippitofficial

FELIX

81,095 görüntüleme • 1 ay önce

Introducing fx, a tiny, open, native coding agent from Vercel Labs. Originally an internal tool, fx is a harness and CLI written in Zig, optimized for research and embedding in larger systems. Today, we're open sourcing it. fx is built on three principles: 1. Fast. A single native binary, no runtime to install. It cold starts in 10µs and does no unnecessary work or I/O before accepting input. fx is the answer to "how fast can a coding agent be?" 2. Light. The 6.3MiB binary uses single-digit megabytes of memory at baseline, made for instant installation and embedding in resource-constrained environments and agent sandboxes. 3. Open. Apache-2.0, model and provider agnostic, suitable for local and cloud inference. Its small core extends through skills, plugins, and MCP. Minimalism is an obsession throughout the entire harness: system prompt, tools, features, binary. The goal was to keep context usage and time to first token low, and make fx optimal for model benchmarking, sandboxing, evals, and gyms. You can use fx directly or embed it as infrastructure. The CLI feels more like a Unix shell than an IDE in the terminal: it preserves scroll history, produces minimal output, and uses complex TUI rendering very, very sparingly. Programmatically, 𝚏𝚡 𝚊𝚜𝚔 --𝚓𝚜𝚘𝚗 gives structured output, 𝚏𝚡 𝚊𝚌𝚙 connects to editors and other clients, and WebAssembly can even run the whole thing inside the browser (see: Privacy is a design constraint: no product telemetry, sessions and usage stay local, and no source code or prompts are shared with any endpoint other than inference. With local inference and auto-updates off, fx is fully hermetic. fx is experimental. Use at your own risk and expect frequent changes. Chat with us on X ( or file issues ( 𝚌𝚞𝚛𝚕 -𝚏𝚜𝚂𝙻 𝚏𝚡.𝚜𝚑/𝚜𝚎𝚝𝚞𝚙.𝚜𝚑 | 𝚋𝚊𝚜𝚑

Introducing fx, a tiny, open, native coding agent from Vercel Labs. Originally an internal tool, fx is a harness and CLI written in Zig, optimized for research and embedding in larger systems. Today, we're open sourcing it. fx is built on three principles: 1. Fast. A single native binary, no runtime to install. It cold starts in 10µs and does no unnecessary work or I/O before accepting input. fx is the answer to "how fast can a coding agent be?" 2. Light. The 6.3MiB binary uses single-digit megabytes of memory at baseline, made for instant installation and embedding in resource-constrained environments and agent sandboxes. 3. Open. Apache-2.0, model and provider agnostic, suitable for local and cloud inference. Its small core extends through skills, plugins, and MCP. Minimalism is an obsession throughout the entire harness: system prompt, tools, features, binary. The goal was to keep context usage and time to first token low, and make fx optimal for model benchmarking, sandboxing, evals, and gyms. You can use fx directly or embed it as infrastructure. The CLI feels more like a Unix shell than an IDE in the terminal: it preserves scroll history, produces minimal output, and uses complex TUI rendering very, very sparingly. Programmatically, 𝚏𝚡 𝚊𝚜𝚔 --𝚓𝚜𝚘𝚗 gives structured output, 𝚏𝚡 𝚊𝚌𝚙 connects to editors and other clients, and WebAssembly can even run the whole thing inside the browser (see: Privacy is a design constraint: no product telemetry, sessions and usage stay local, and no source code or prompts are shared with any endpoint other than inference. With local inference and auto-updates off, fx is fully hermetic. fx is experimental. Use at your own risk and expect frequent changes. Chat with us on X ( or file issues ( 𝚌𝚞𝚛𝚕 -𝚏𝚜𝚂𝙻 𝚏𝚡.𝚜𝚑/𝚜𝚎𝚝𝚞𝚙.𝚜𝚑 | 𝚋𝚊𝚜𝚑

Vercel Developers

876,083 görüntüleme • 1 gün önce

Claude Opus 5 x NexLev MCP might be the most unfair combo for building faceless YouTube channels right now So I’m giving away the FULL AI Story channel production system behind it Here’s EVERYTHING that you’ll get inside: → The exact Claude setup that turns Opus 5 into a full faceless YouTube production operator. → NexLev MCP niche validation prompts that find new channels getting 100k+ views without guessing niches manually. → 48-hour velocity check prompt to spot which AI Story angles are actually moving right now. → RPM filtering system so you avoid low-value niches and only build around $12-$20+ RPM opportunities. → Opus 5 JSON script framework for 8,000+ word videos with locked characters, pacing rules, emotional beats, and cliffhangers. → Documentary research brief prompt that verifies dates, names, timelines, and quotes before the script gets written. → ElevenLabs MCP voiceover workflow with narrator matching by niche so the voice fits the audience instead of sounding random. → Higgsfield MCP visual system using Seedance 2.0, Flux 2, and Nano Banana Pro to create animated intros, scene images, and consistent characters. → Thumbnail prompt structure for ChatGPT Image 2.0 so the final video has clean text, high emotion, and a clickable 1280x720 layout. → Full assembly checklist for taking the script, voiceover, animated clips, captions, and thumbnail into an upload-ready video in under 30 minutes. All built from the AI YouTube production playbooks used across: → 120+ Elevate members → $12k/mo average per student → 800M+ total views across the system Like + comment "CLAUDE" and I’ll send you the whole thing (Must be following so I can DM)

Claude Opus 5 x NexLev MCP might be the most unfair combo for building faceless YouTube channels right now So I’m giving away the FULL AI Story channel production system behind it Here’s EVERYTHING that you’ll get inside: → The exact Claude setup that turns Opus 5 into a full faceless YouTube production operator. → NexLev MCP niche validation prompts that find new channels getting 100k+ views without guessing niches manually. → 48-hour velocity check prompt to spot which AI Story angles are actually moving right now. → RPM filtering system so you avoid low-value niches and only build around $12-$20+ RPM opportunities. → Opus 5 JSON script framework for 8,000+ word videos with locked characters, pacing rules, emotional beats, and cliffhangers. → Documentary research brief prompt that verifies dates, names, timelines, and quotes before the script gets written. → ElevenLabs MCP voiceover workflow with narrator matching by niche so the voice fits the audience instead of sounding random. → Higgsfield MCP visual system using Seedance 2.0, Flux 2, and Nano Banana Pro to create animated intros, scene images, and consistent characters. → Thumbnail prompt structure for ChatGPT Image 2.0 so the final video has clean text, high emotion, and a clickable 1280x720 layout. → Full assembly checklist for taking the script, voiceover, animated clips, captions, and thumbnail into an upload-ready video in under 30 minutes. All built from the AI YouTube production playbooks used across: → 120+ Elevate members → $12k/mo average per student → 800M+ total views across the system Like + comment "CLAUDE" and I’ll send you the whole thing (Must be following so I can DM)

gold.

21,798 görüntüleme • 22 gün önce

Boom! Grok Tasks Make It One Of The Most POWERFUL Real-Time AI Systems In The World. — My How to Use Grok Tasks With Hidden Tools For Powerful Daily Output. Grok Tasks are customizable AI workflows that integrate a variety of tools to streamline daily activities, from research and analysis to creative planning and problem-solving. I have been using them for quite sometime and because of the vital heartbeat of news and first person data on X, it is the most powerful AI platform available. By combining Tasks with tools like web searches, X platform interactions, code execution, and media viewers, you can build efficient, automated processes. These tasks work by prompting Grok with a clear description of what you want to achieve, and Grok will intelligently call the necessary tools in sequence or parallel to deliver results. Here's a step-by-step guide to creating and using Grok Tasks: Step 1: Define Your Task Start by clearly outlining the daily activity or goal. Consider what inputs you have (e.g., a URL, a query, or an attachment) and what output you need (e.g., a summary, calculation, or visual analysis). Break it down into subtasks to identify tool needs. For example, if your task involves researching current events, note that you'll need search and browsing capabilities. Step 2: Review Available Tools Familiarize yourself with the tools Grok can access. Here's a quick overview: - Code Execution: Run Python code for calculations, data processing, or simulations using libraries like numpy, pandas, or sympy. - Browse Page: Fetch and summarize content from any website URL with custom instructions. - Web Search: Perform general internet searches, returning results with optional operators like site:. - Web Search With Snippets: Get quick, detailed excerpts from search results for fact-checking. - X Keyword Search: Advanced search for X posts using operators like from:, since:, or filter:. - X Semantic Search: Find semantically related X posts based on a query, with filters for dates or users. - X User Search: Locate X users by name or handle. - X Thread Fetch: Retrieve a full X post thread, including context like replies and parents. - View Image: Analyze an image from a URL or conversation ID. - View X Video: Extract frames and subtitles from an X-hosted video. - Search PDF Attachment: Query a PDF file for relevant pages using keyword or regex modes. - Browse PDF Attachment: View specific pages of a PDF with text and screenshots. Select tools that align with your task. Aim for a mix to handle data gathering, processing, and visualization. Step 3: Craft Your Prompt Write a detailed prompt to Grok describing the task. Include: - The overall goal. - Specific steps or subtasks. - References to tools if you want to guide the process (e.g., "Use web_search to find sources, then code_execution to analyze data"). - Any constraints, like dates or limits. Example prompt: "Create a Grok Task for my morning routine: Search recent X posts about tech news using x_keyword_search, fetch a key thread with x_thread_fetch, and summarize with browse_page on linked articles." Step 4: Submit and Interact Send your prompt to Grok. It will process the task by calling tools as needed, often in parallel for efficiency. Review the output and refine with follow-up prompts if required (e.g., "Expand on that using view_image for visuals"). Iterate to fine-tune the workflow for reuse. Step 5: Save and Reuse Once refined, note the prompt as a template for future use. You can adapt it for similar tasks, making Grok Tasks a habitual part of your day. Finding Grok Tasks To discover existing Grok Tasks or inspiration for new ones, use X searches with tools like x_keyword_search or x_semantic_search (e.g., query: "Grok Tasks examples" with mode: Latest). Browse community-shared threads via x_thread_fetch, or web_search for tutorials on xAI features. Prompt Grok directly: "Show me popular Grok Tasks for productivity." 1 of 3

Boom! Grok Tasks Make It One Of The Most POWERFUL Real-Time AI Systems In The World. — My How to Use Grok Tasks With Hidden Tools For Powerful Daily Output. Grok Tasks are customizable AI workflows that integrate a variety of tools to streamline daily activities, from research and analysis to creative planning and problem-solving. I have been using them for quite sometime and because of the vital heartbeat of news and first person data on X, it is the most powerful AI platform available. By combining Tasks with tools like web searches, X platform interactions, code execution, and media viewers, you can build efficient, automated processes. These tasks work by prompting Grok with a clear description of what you want to achieve, and Grok will intelligently call the necessary tools in sequence or parallel to deliver results. Here's a step-by-step guide to creating and using Grok Tasks: Step 1: Define Your Task Start by clearly outlining the daily activity or goal. Consider what inputs you have (e.g., a URL, a query, or an attachment) and what output you need (e.g., a summary, calculation, or visual analysis). Break it down into subtasks to identify tool needs. For example, if your task involves researching current events, note that you'll need search and browsing capabilities. Step 2: Review Available Tools Familiarize yourself with the tools Grok can access. Here's a quick overview: - Code Execution: Run Python code for calculations, data processing, or simulations using libraries like numpy, pandas, or sympy. - Browse Page: Fetch and summarize content from any website URL with custom instructions. - Web Search: Perform general internet searches, returning results with optional operators like site:. - Web Search With Snippets: Get quick, detailed excerpts from search results for fact-checking. - X Keyword Search: Advanced search for X posts using operators like from:, since:, or filter:. - X Semantic Search: Find semantically related X posts based on a query, with filters for dates or users. - X User Search: Locate X users by name or handle. - X Thread Fetch: Retrieve a full X post thread, including context like replies and parents. - View Image: Analyze an image from a URL or conversation ID. - View X Video: Extract frames and subtitles from an X-hosted video. - Search PDF Attachment: Query a PDF file for relevant pages using keyword or regex modes. - Browse PDF Attachment: View specific pages of a PDF with text and screenshots. Select tools that align with your task. Aim for a mix to handle data gathering, processing, and visualization. Step 3: Craft Your Prompt Write a detailed prompt to Grok describing the task. Include: - The overall goal. - Specific steps or subtasks. - References to tools if you want to guide the process (e.g., "Use web_search to find sources, then code_execution to analyze data"). - Any constraints, like dates or limits. Example prompt: "Create a Grok Task for my morning routine: Search recent X posts about tech news using x_keyword_search, fetch a key thread with x_thread_fetch, and summarize with browse_page on linked articles." Step 4: Submit and Interact Send your prompt to Grok. It will process the task by calling tools as needed, often in parallel for efficiency. Review the output and refine with follow-up prompts if required (e.g., "Expand on that using view_image for visuals"). Iterate to fine-tune the workflow for reuse. Step 5: Save and Reuse Once refined, note the prompt as a template for future use. You can adapt it for similar tasks, making Grok Tasks a habitual part of your day. Finding Grok Tasks To discover existing Grok Tasks or inspiration for new ones, use X searches with tools like x_keyword_search or x_semantic_search (e.g., query: "Grok Tasks examples" with mode: Latest). Browse community-shared threads via x_thread_fetch, or web_search for tutorials on xAI features. Prompt Grok directly: "Show me popular Grok Tasks for productivity." 1 of 3

Brian Roemmele

152,242 görüntüleme • 7 ay önce

HTML Artifacts are a big part of how I work with agents now. Artifacts can be more than just static files. When combined with agents, they can take action or help you take action. This unlocks all kinds of interesting ways to work with agents. This is clearly the future. Check out this writing and scheduler artifact I built in a few minutes. It uses a bit of HTML and JS. All the data is in markdown (Obsidian vaults), so the agent can access and modify it at any time. No DB needed. No sophisticated functionalities. The agent decides all that for me based on the skills, context, and memory it has access to. The best part about this simple stack is that all the important information stays with me. This has allowed me to build a recursive self-improving system and automations that can better tap into coding agents like Codex or Claude Code. I could have paid or built an entire app for scheduling posts, and there are so many of them out there. But I don't need to. I've realized a simple artifact does the job. And the simplicity of it is actually an advantage. Very little maintenance for very high returns on personalization, time, and efficiency. The other benefit of this is that I can add features as I please. That level of personalization feels magical, and we should all be pursuing more of it. All of this just keeps compounding. Of course, this example is just about writing. But I have similar artifacts for research, design, experimentation, evaluation, and so much more. And no, I didn't actually publish the post example I shared in the clip. It was just for demonstration purposes. I actually spend more time than this when writing together with agents. Lastly, having built my own agent orchestrator tool has made me realize that simplifying the tool stack is a superpower. If you are curious about how all this works, I will do a live session next week:

HTML Artifacts are a big part of how I work with agents now. Artifacts can be more than just static files. When combined with agents, they can take action or help you take action. This unlocks all kinds of interesting ways to work with agents. This is clearly the future. Check out this writing and scheduler artifact I built in a few minutes. It uses a bit of HTML and JS. All the data is in markdown (Obsidian vaults), so the agent can access and modify it at any time. No DB needed. No sophisticated functionalities. The agent decides all that for me based on the skills, context, and memory it has access to. The best part about this simple stack is that all the important information stays with me. This has allowed me to build a recursive self-improving system and automations that can better tap into coding agents like Codex or Claude Code. I could have paid or built an entire app for scheduling posts, and there are so many of them out there. But I don't need to. I've realized a simple artifact does the job. And the simplicity of it is actually an advantage. Very little maintenance for very high returns on personalization, time, and efficiency. The other benefit of this is that I can add features as I please. That level of personalization feels magical, and we should all be pursuing more of it. All of this just keeps compounding. Of course, this example is just about writing. But I have similar artifacts for research, design, experimentation, evaluation, and so much more. And no, I didn't actually publish the post example I shared in the clip. It was just for demonstration purposes. I actually spend more time than this when writing together with agents. Lastly, having built my own agent orchestrator tool has made me realize that simplifying the tool stack is a superpower. If you are curious about how all this works, I will do a live session next week:

elvis

18,374 görüntüleme • 3 ay önce

I just built a Meta Ads diagnostic in Claude Code that tells you WHY your account broke, not just what changed 🤯 It spins up a team of agents that each investigate a different reason performance dropped, then argue against each other to kill the wrong answer before it ever reaches you. All inside Claude Code. Perfect for DTC brands and agencies who panic-kill creative the second CPA spikes. If you've watched ROAS fall off a cliff and opened Ads Manager with ten tabs going, you already know what happens next. Your gut says "creative fatigue." You kill your best-performing ad. A week later performance is still broken, because that was never the problem. Guessing wrong is the most expensive move in paid social. This workflow ends the guessing: → One agent investigates each competing theory — creative fatigue, budget and delivery changes, traffic quality, offer and seasonality → Each one is blind to the others, reasoning only from its own slice of the data so they can't bias each other → A refuter agent then attacks every surviving theory and tries to kill it → A theory only stands if the data can't disprove it → You get a ranked diagnosis: the real cause, the evidence for and against it, and the one move to make this week No anchoring on the first obvious answer. No killing winning creative on a hunch. No "here's what happened" reports that never tell you why. What you get: → Every theory tested in parallel instead of one biased guess → An adversarial pass that kills the wrong answer before you act on it → A ranked diagnosis with confidence levels and evidence both ways → A reusable workflow you drop next month's export into and re-run Built 100% in Claude Code with the new dynamic workflows. The first account I ran it on looked like textbook creative fatigue. The workflow disagreed, and traced the real cause to a budget change that had doubled spend and flooded delivery with junk traffic. I put together a full playbook with the exact workflow, the prompt, and how to run it on your own account. Want it for free? > Like this post > Comment "META" And I'll send it over (must be following so I can DM)

I just built a Meta Ads diagnostic in Claude Code that tells you WHY your account broke, not just what changed 🤯 It spins up a team of agents that each investigate a different reason performance dropped, then argue against each other to kill the wrong answer before it ever reaches you. All inside Claude Code. Perfect for DTC brands and agencies who panic-kill creative the second CPA spikes. If you've watched ROAS fall off a cliff and opened Ads Manager with ten tabs going, you already know what happens next. Your gut says "creative fatigue." You kill your best-performing ad. A week later performance is still broken, because that was never the problem. Guessing wrong is the most expensive move in paid social. This workflow ends the guessing: → One agent investigates each competing theory — creative fatigue, budget and delivery changes, traffic quality, offer and seasonality → Each one is blind to the others, reasoning only from its own slice of the data so they can't bias each other → A refuter agent then attacks every surviving theory and tries to kill it → A theory only stands if the data can't disprove it → You get a ranked diagnosis: the real cause, the evidence for and against it, and the one move to make this week No anchoring on the first obvious answer. No killing winning creative on a hunch. No "here's what happened" reports that never tell you why. What you get: → Every theory tested in parallel instead of one biased guess → An adversarial pass that kills the wrong answer before you act on it → A ranked diagnosis with confidence levels and evidence both ways → A reusable workflow you drop next month's export into and re-run Built 100% in Claude Code with the new dynamic workflows. The first account I ran it on looked like textbook creative fatigue. The workflow disagreed, and traced the real cause to a budget change that had doubled spend and flooded delivery with junk traffic. I put together a full playbook with the exact workflow, the prompt, and how to run it on your own account. Want it for free? > Like this post > Comment "META" And I'll send it over (must be following so I can DM)

Mike Futia

12,772 görüntüleme • 2 ay önce

This workflow is perfect for creating short fashion-style cinematic videos. I simplified the original prompts based on willie’s method, and the whole process is now much faster and more stable: 1. Generate a 3×3 keyframe grid (Nano Banana Pro only) Use this simple prompt: “In a 3x3 grid, show this character in different angles, keep the scene the same, random poses. This is far simpler and more efficient than my old prompts. You can generate multiple times and just pick the keyframes you like most. 2. Extract a high-res keyframe (Super stable trick) Take a screenshot of the keyframe you want from the 3×3 grid, send it back to Nano Banana Pro, and simply say: “Give me a high-resolution version.” This method is much more stable than relying on complex upscaling prompts. 3. Generate the video with Kling 2.5 Turbo Upload the first and last frames to Kling 2.5 Turbo and use this prompt: “The camera very slowly and smoothly lowers on a boom.” From my testing, Kling 2.5 Turbo offers the best balance of stability and cost — other models are either less consistent or noticeably more expensive. 4. Final speed adjustment with willie’s tool (Critical step) Use the tool built by willie to fine-tune the playback speed of each clip. This step is essential for getting that premium cinematic feel. I’ll drop the tool link in the comments.

This workflow is perfect for creating short fashion-style cinematic videos. I simplified the original prompts based on willie’s method, and the whole process is now much faster and more stable: 1. Generate a 3×3 keyframe grid (Nano Banana Pro only) Use this simple prompt: “In a 3x3 grid, show this character in different angles, keep the scene the same, random poses. This is far simpler and more efficient than my old prompts. You can generate multiple times and just pick the keyframes you like most. 2. Extract a high-res keyframe (Super stable trick) Take a screenshot of the keyframe you want from the 3×3 grid, send it back to Nano Banana Pro, and simply say: “Give me a high-resolution version.” This method is much more stable than relying on complex upscaling prompts. 3. Generate the video with Kling 2.5 Turbo Upload the first and last frames to Kling 2.5 Turbo and use this prompt: “The camera very slowly and smoothly lowers on a boom.” From my testing, Kling 2.5 Turbo offers the best balance of stability and cost — other models are either less consistent or noticeably more expensive. 4. Final speed adjustment with willie’s tool (Critical step) Use the tool built by willie to fine-tune the playback speed of each clip. This step is essential for getting that premium cinematic feel. I’ll drop the tool link in the comments.

underwood

22,173 görüntüleme • 8 ay önce

MiniMax H3 Instead of sharing the prompts for each of these videos, I thought it would be more useful to share how I created that prompts. All of the videos were generated with text-to-video. First, find an image with the kind of scene, composition and mood you want to recreate. I used a few YouTube playlist thumbnails as references but Pinterest is also a great place to find inspiration. You can even use your own old or nostalgic photographs. Then upload the image to ChatGPT and ask it to describe the scene. The description it gives you can essentially become your text-to-video prompt. From there, you can generate completely new scenes with a similar composition, atmosphere and cinematic language. You can of course use the reference image directly with image-to-video or as a first frame. But if the original image isn't yours, I prefer using it only as visual inspiration and recreating the scene through text-to-video. This is the prompt I use with ChatGPT: "Describe the scene in this image in English, focusing primarily on what is happening, the characters, their actions and body language, the setting and the overall atmosphere. Also briefly describe the composition, framing, camera angle, approximate lens choice, lighting, color palette and cinematic aesthetic. Keep it concise and scene-focused rather than overly technical."

MiniMax H3 Instead of sharing the prompts for each of these videos, I thought it would be more useful to share how I created that prompts. All of the videos were generated with text-to-video. First, find an image with the kind of scene, composition and mood you want to recreate. I used a few YouTube playlist thumbnails as references but Pinterest is also a great place to find inspiration. You can even use your own old or nostalgic photographs. Then upload the image to ChatGPT and ask it to describe the scene. The description it gives you can essentially become your text-to-video prompt. From there, you can generate completely new scenes with a similar composition, atmosphere and cinematic language. You can of course use the reference image directly with image-to-video or as a first frame. But if the original image isn't yours, I prefer using it only as visual inspiration and recreating the scene through text-to-video. This is the prompt I use with ChatGPT: "Describe the scene in this image in English, focusing primarily on what is happening, the characters, their actions and body language, the setting and the overall atmosphere. Also briefly describe the composition, framing, camera angle, approximate lens choice, lighting, color palette and cinematic aesthetic. Keep it concise and scene-focused rather than overly technical."

Kōda

45,208 görüntüleme • 5 gün önce

He says he makes $6,286 a month copying YouTube Shorts. Pause his video at 0:12. A 22 year old in a red flannel and a backwards cap stands in his kitchen, points at a YouTube Studio dashboard, and tells you the part time job is dead. Just copy links. Easy money. The method: open a football channel called Avary. 48,600 subscribers from 44 videos. Click the most viral Short. Copy the link. Paste it into a tool called Viblo. Add a title in Archivo Black. Slap red numbers "1." and "2." on top of a stranger's goal compilation. Upload. Comment "Vib" for the link. That's the funnel. The link goes to a referral. $30 month subscription. He gets a cut of every kid who signs up. The dashboard he shows isn't his. YouTube demonetizes Reused Content on the first sweep. A channel built on stolen Shorts with cartoon numbers on top never sees a Partner Program approval. The $6,286 is a screenshot. The kitchen is real. The flannel is real. The green AliExpress stylus he pokes the screen with cost him $4. Here's what the whole stack actually is: yt-dlp downloads the Short. Claude reads the transcript and writes the title. FFmpeg crops it, adds the green border, burns in the text. n8n runs the whole thing from a Telegram message. Total cost: a few cents in API calls. He's selling a Python script with a logo for $30 month. The football channel doesn't make him money. The kids in the comments do.

Aeron

30,415 görüntüleme • 2 ay önce

How do you turn a scene idea into a Prompt? All you need to do is roughly describe what's in your head to an LLM. It doesn't have to be perfect or highly detailed. Once it understands the core idea, it can help turn it into a well-structured prompt. In my case, I use a custom skill file that I built myself. After I provide the idea, it generates both a storyboard and video prompts for me. I then review the outputs and refine them through iteration, giving feedback like "make this shot wider," "change this action," or "move the camera here." After a few rounds of adjustments, I usually arrive at the final result. The process is much closer to directing than writing a perfect prompt from scratch. The Idea: Two characters face each other. Serenity fights like a Wing Chun master. She unleashes a rapid barrage of punches into Ruk's abdomen. The fight should feel highly energetic and sakuga-driven, with exaggerated action beats and dynamic choreography. Use 14 panels. The final attack should show Serenity launching high into the sky, then diving straight down at extreme speed. She lands with both feet on Ruk's head, driving him deep into the ground and burying him on impact. All other scenes should be equally creative and visually inventive. Emphasize fast pacing, flash cuts, burst cuts, sudden perspective changes, dramatic impact moments, and imaginative camera angles. Use aggressive screen direction, strong momentum shifts, dynamic framing, and escalating choreography to create a thrilling, high-energy martial arts sequence. This is the final video, you can check the prompts in the replies. Used tools: Midjourney, Codex, GPT Image 2, Seedance 2.0, Suno, Capcut

How do you turn a scene idea into a Prompt? All you need to do is roughly describe what's in your head to an LLM. It doesn't have to be perfect or highly detailed. Once it understands the core idea, it can help turn it into a well-structured prompt. In my case, I use a custom skill file that I built myself. After I provide the idea, it generates both a storyboard and video prompts for me. I then review the outputs and refine them through iteration, giving feedback like "make this shot wider," "change this action," or "move the camera here." After a few rounds of adjustments, I usually arrive at the final result. The process is much closer to directing than writing a perfect prompt from scratch. The Idea: Two characters face each other. Serenity fights like a Wing Chun master. She unleashes a rapid barrage of punches into Ruk's abdomen. The fight should feel highly energetic and sakuga-driven, with exaggerated action beats and dynamic choreography. Use 14 panels. The final attack should show Serenity launching high into the sky, then diving straight down at extreme speed. She lands with both feet on Ruk's head, driving him deep into the ground and burying him on impact. All other scenes should be equally creative and visually inventive. Emphasize fast pacing, flash cuts, burst cuts, sudden perspective changes, dramatic impact moments, and imaginative camera angles. Use aggressive screen direction, strong momentum shifts, dynamic framing, and escalating choreography to create a thrilling, high-energy martial arts sequence. This is the final video, you can check the prompts in the replies. Used tools: Midjourney, Codex, GPT Image 2, Seedance 2.0, Suno, Capcut

Kōda

23,805 görüntüleme • 2 ay önce