Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

[ลองฟีเจอร์ใหม่ Claude Design แบบเร็วๆ] workflow ที่ใช้ทำคลิปนี้: 1. บอก Claude ว่าอยากทำคอนเทนต์ "5 คำ AI ที่ต้องรู้" ความยาว 2 นาที → Claude เจน script voice-over + video prompt + caption ให้ครบ 2. เอา script ไปเจนเสียง voice-over ใน ElevenLabs (แพลตฟอร์มเจนเสียงพูด AI จากข้อความ) 3. เอา video prompt ไป paste ใน Claude Design (ฟีเจอร์ใหม่ของ Claude...

0xJui10's profile picture

Jui (Colby Daddy) 🐶

3,096 subscribers

35,858 Aufrufe • vor 5 Monaten •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

13 Kommentare

Profilbild von ใดใดในโลกล้วนอุรังอุตัง
ใดใดในโลกล้วนอุรังอุตังvor 5 Monaten

@ElevenLabs เคยลองให้ cowork ตัดต่อด้วย davinci แล้วยังไม่ค่อย work คือมันยังไม่เนียนในกรณีมีคลิปสั้นๆ หลายอัน รอดูเผื่อคุณจะทำได้ผล

Profilbild von Jui (Colby Daddy) 🐶
Jui (Colby Daddy) 🐶vor 5 Monaten

@ElevenLabs ได้เลยฮะ ถ้าผลลัพท์ดีจะมาแชร์

Profilbild von Jui (Colby Daddy) 🐶
Jui (Colby Daddy) 🐶vor 5 Monaten

หลายคนอยากรู้ว่ามันกิน token ขนาดไหน(ผมก็อยากรู้) Anthropic ไม่ประกาศตัวเลข token ที่แน่นอนว่าปล่อยให้ใช้มากแค่ไหนในแต่ละแพ็คเกจ แต่การคำนวนคงคิดแบบปกติ ℹ️input (prompt + context + ไฟล์แนบ) + output (โค้ด/visual ที่ generate) แต่เนื่องจาก Design งาน visual-heavy → output มักยาว (HTML/CSS/SVG/React) กิน output token เยอะกว่า chat ปกติ ในรูปผมเป้น Claude Max $200 ลองใช้งานไปแค่ 2รอบ เป็นการลองทำสไลด์หลายๆหน้า และทำแบบในคลิป = วันเดียวกินไป 40+%

Profilbild von modty ai
modty aivor 5 Monaten

@ElevenLabs เจ๋งมากกก ถ้ากินโทเคยดุๆใช้gemini ทำสไลด์แล้วบันทึกหน้าจอพอแทนกันได้อยุ่

Profilbild von Alizza Chu 💜
Alizza Chu 💜vor 5 Monaten

@ElevenLabs อุ้ยยยของดีขอบคุณจั๊พ🙏

Profilbild von รึเอง feat. AI x Econ 🟡
รึเอง feat. AI x Econ 🟡vor 5 Monaten

@ElevenLabs เจ๋งมากก

Profilbild von Earn Earn🩷
Earn Earn🩷vor 5 Monaten

@ElevenLabs ดีม้ากก

Profilbild von Jui (Colby Daddy) 🐶
Jui (Colby Daddy) 🐶vor 5 Monaten

@ElevenLabs แต่กิน token สุดด

Profilbild von goodday, LARA✨
goodday, LARA✨vor 5 Monaten

@ElevenLabs ขอบคุณคร้าบ งานออกมาดีแหะ

Profilbild von Jui (Colby Daddy) 🐶
Jui (Colby Daddy) 🐶vor 5 Monaten

@XMeetoo2 @ElevenLabs ใช้เวลาไม่นานด้วย เป็นจุดเริ่มที่ดีเลย

Profilbild von FU11🔴
FU11🔴vor 5 Monaten

@ElevenLabs กิน token เยอะมากมั้ยคับ 55

Profilbild von Jui (Colby Daddy) 🐶
Jui (Colby Daddy) 🐶vor 5 Monaten

@ElevenLabs เยอะแน่นอนครับ ยิ่ง output เป็นงาน Visual 💸

Profilbild von FU11🔴
FU11🔴vor 5 Monaten

@ElevenLabs โอเครๆๆ ขอบคุณนะจุ้ยๆ

Ähnliche Videos

THIS IS F**KING GOLD Claude can now produce fully animated YouTube videos directly inside your chat. No video editors. No external rendering tools. No timeline slicing. Nobody is talking about this workflow yet, but connecting Claude to a custom Model Context Protocol (MCP) completely changes multimedia creation. Here is what happens from a single prompt: → Script generation: Claude drafts a structured, production-ready script. → Voice narration: Converts the text into timed voiceover audio. → Scene animation: Generates and sequences animated visual assets. All executed natively inside the conversation. The era of copying prompts into 4 different AI tools is over. MCP turns Claude into an end-to-end media engine. Bookmark to try this setup when you build your next workflow.
0:32

THIS IS F**KING GOLD Claude can now produce fully animated YouTube videos directly inside your chat. No video editors. No external rendering tools. No timeline slicing. Nobody is talking about this workflow yet, but connecting Claude to a custom Model Context Protocol (MCP) completely changes multimedia creation. Here is what happens from a single prompt: → Script generation: Claude drafts a structured, production-ready script. → Voice narration: Converts the text into timed voiceover audio. → Scene animation: Generates and sequences animated visual assets. All executed natively inside the conversation. The era of copying prompts into 4 different AI tools is over. MCP turns Claude into an end-to-end media engine. Bookmark to try this setup when you build your next workflow.

Mayor.

116,445 Aufrufe • vor 1 Monat

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)
0:20

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,531 Aufrufe • vor 4 Monaten

CANCEL Your Weekend Plans, & Learn Claude Code Today. This Claude Code teaches more about vibe-coding in 30 mins than most tutorials do in hours. Save this, it'll change how you build forever People are building entire apps and charging clients $5,000 to $20,000 using Claude Code. This Claude Code video is a goldmine. Full Claude Code tutorial. Beginner to pro. Every feature. Every setup step. Every best practice. Zero prior knowledge needed. Save it. Watch it tonight. Not tomorrow. Tonight. Follow Himanshu Kumar so you don't miss the breakdowns for each feature. This is your complete Claude Code roadmap. Lose it and you lose the next 12 months of income. ↓ 1. Understand What Claude Code Actually Is. You think Claude Code is just another chatbot. It's not. And that misunderstanding is why you're broke. ChatGPT gives you text. Claude Code gives you software. It runs in your terminal. It reads your entire codebase. It writes files directly to your project. It runs commands on your machine. It debugs errors autonomously. It builds features end to end. You're not chatting. You're deploying a developer. One that works 24/7. Never asks for a raise. Never calls in sick. Never pushes broken code at 5 PM on a Friday. People are charging clients $5,000-$10,000 for apps they built with Claude Code in 3 hours. And you didn't even know this tool existed because you're still asking ChatGPT to write you a to-do list. The gap between you and people making money with AI isn't intelligence. It's awareness. Now you're aware. Save this post. Follow Himanshu Kumar for the complete breakdown of every Claude Code feature. ↓ 2. Set Up Claude Code Properly. Most people quit here. "It's too complicated." "I don't know terminal." "I'll set it up later." Later never comes. And "complicated" means "I watched for 30 seconds and gave up." The setup takes 10 minutes. Install Node.js. Install Claude Code via npm. Authenticate your account. Open your terminal. Done. 10 minutes. You spent longer this morning deciding what to have for breakfast. The video walks through every single click. Every command. Every screen. Assuming you know absolutely nothing. If you can download an app on your phone, you can set up Claude Code. It's the same level of difficulty. But you'll still tell yourself it's "too technical" because that excuse is more comfortable than admitting you're just scared to try something new. This is the setup that everything else builds on. Skip it and nothing works. ↓ 3. Use the Desktop App. You don't even need to live in the terminal if you don't want to. Claude Code has a desktop app. Clean interface. Visual feedback. Everything you need without touching command line. But here's the thing most people don't know: The desktop app isn't just a pretty wrapper. It lets you manage projects visually. See file changes in real time. Switch between projects instantly. The people making money with Claude Code use the desktop app for client projects because it's faster to manage multiple builds simultaneously. You're still opening 14 browser tabs to organize one project. They open one app and everything's there. Efficiency isn't a personality trait. It's a tool choice. Save this post. Follow Himanshu Kumar for the desktop app workflow that handles 5 client projects at once. ↓ 4. Install the Right Dependencies. This is where beginners silently fail and blame the tool. Claude Code needs certain dependencies installed to work properly. Miss one and everything breaks. Then you go on Twitter and say "Claude Code doesn't work." It works fine. You just didn't read the setup guide. The video covers every dependency you need. What to install. How to install it. How to verify it's working. No guessing. No Stack Overflow rabbit holes at midnight. No "why isn't this working" for 3 hours. Watch the dependency section once. Follow every step. Never deal with setup issues again. You spent more time last week troubleshooting a printer than this takes. ↓ 5. Work Inside Your Code Editor. Claude Code integrates directly with your code editor. VS Code. Cursor. Whatever you use. It's not a separate window you alt-tab between. It's right there. In your workflow. You type a request. Claude writes the code. The code appears in your editor. You review it. Accept it. Done. No copy pasting between windows. No reformatting code that got mangled in transit. No "which version was the right one." It's like pair programming with someone who never gets distracted, never argues about naming conventions, and actually writes code that works on the first try. Your current coding process is: Google the problem, read 5 answers on Stack Overflow, copy the wrong one, debug for an hour, find the right one, paste it in, break something else, repeat. Claude Code's process is: describe what you want, get working code, move on with your life. Same hour. One method produces working software. The other produces frustration and a browser history full of Stack Overflow tabs. Stop coding the hard way. Save this post. Follow Himanshu Kumar for code editor setup guides and integration tips. ↓ 6. Master Basic Usage. Most people learn 5% of a tool and say they "know" it. You "know" Photoshop because you can crop an image. You "know" Excel because you can sum a column. You "know" Claude Code because you asked it one question. Basic usage means: How to give Claude Code context about your project. How to ask for changes to existing code. How to generate new files and features. How to review what Claude produces. How to iterate when the output isn't perfect. These basics are the foundation of everything. Skip them and every advanced feature feels confusing. Master them and every advanced feature feels obvious. The video breaks down each one with real examples. Not theory. Actual usage on actual projects. You've been using AI tools at 5% capacity and wondering why your results are 5% of what others get. Save this post. Follow Himanshu Kumar for daily Claude Code usage tips. ↓ 7. Learn Every Command. Claude Code has commands that most users never discover. Because most users type one message and expect magic. That's not how professionals use it. Professionals use specific commands that tell Claude Code exactly what to do, how to do it, and what constraints to follow. The difference between a beginner and someone making $10K/month with Claude Code is knowing which command to use and when. The video walks through every single one. Not just what they do. But when to use each one. And why one command is better than another for specific situations. You've been using Claude Code like a hammer. These commands turn it into a full toolbox. Stop treating a power tool like a blunt instrument. Save this post. Follow Himanshu Kumar for the command cheat sheet I use daily. ↓ 8. Understand Modes and Shortcuts. Speed matters. The person who builds an app in 2 hours charges $5,000. The person who builds the same app in 2 days charges $2,000. Same app. Same quality. Different speed. Different income. Claude Code has modes that change how it operates. And shortcuts that cut your workflow time in half. Most people don't know either exists. They use Claude Code in default mode for everything. Like driving a car in first gear on the highway. Technically it works. But everyone is passing you. The video shows you every mode. Every shortcut. Every time-saving trick that separates the people charging $2,000 per project from the people charging $10,000. Speed is money. Literally. Save this post. Follow Himanshu Kumar for the shortcuts that cut my build time by 60%. ↓ 9. Write a Proper Planning Prompt. This is the section that separates amateurs from professionals. And it's the section most people skip. A planning prompt tells Claude Code what you're building before you start building it. Architecture. File structure. Technologies. Features. Constraints. Edge cases. Without a planning prompt, Claude Code guesses. And guessing produces garbage. With a planning prompt, Claude Code executes a clear plan. And clear plans produce working software. The video shows you exactly how to write a planning prompt that makes Claude Code produce professional-grade output on the first try. "But I just want to start coding." That's why your code breaks every time. That's why you restart projects 4 times. That's why nothing you build ever gets finished. Because you refuse to plan. A 5-minute planning prompt saves you 5 hours of debugging. But you'd rather skip the 5 minutes and suffer through the 5 hours because patience isn't your thing. And that's exactly why you're not making money. Planning is the most underpaid skill in coding. And the most overpaid when you master it. Save this post. Follow Himanshu Kumar for the planning prompt templates I use for every client project. ↓ 10. Choose the Right Model. Claude Code lets you select different AI models. Not all models are the same. Not all tasks need the same model. Using the most powerful model for a simple task wastes credits. Using a basic model for a complex task wastes time. The video explains: Which model to use for quick fixes. Which model to use for complex architecture. Which model to use for debugging. Which model to use for code generation. Most people pick one model and use it for everything. That's like using a sledgehammer to hang a picture frame. Model selection is strategy. And strategy is money. The people making $10K/month with Claude Code are strategic about every credit they spend. You're burning through credits because you use the most expensive model to write a hello world. ↓ 11. Use Git and Version Control. If you're not using version control, you're one mistake away from losing everything. Claude Code integrates with Git. Every change tracked. Every version saved. Every mistake reversible. Without Git: Claude makes a change. It breaks something. You can't undo it. You start over. 3 hours wasted. With Git: Claude makes a change. It breaks something. You roll back in 5 seconds. Keep working. Version control isn't optional. It's insurance. And the people not using it are the same people who say "I lost my entire project" like it's something that just happens. It doesn't just happen. It happens because you didn't set up Git. The video walks through the entire Git integration. Save this post. Follow Himanshu Kumar for the Git workflow that's saved every project I've ever built. ↓ 12. Set Up Claude MD and Memory. This is the feature that makes Claude Code feel like a real team member instead of a stranger you explain everything to every time. ClaudeMD is a memory file. You tell Claude Code about your project once. It remembers forever. Coding style preferences. Project architecture decisions. Technology stack. File naming conventions. Business logic rules. Without ClaudeMD: Every new conversation starts from zero. You explain the same things repeatedly. Output is inconsistent. With ClaudeMD: Claude knows your project. Claude follows your rules. Claude produces consistent, professional code. The difference between a sloppy freelancer and a reliable agency is consistency. Claude. MD gives you consistency without the agency overhead. Most people don't set this up and wonder why Claude Code gives different answers every time. ↓ 13. Automate with Tasks. This is where Claude Code stops being a tool and starts being an employee. Tasks let you define repeating workflows. "Every time I push code, run tests." "Every time I create a new file, add boilerplate." "Every time I start a session, check for errors." Automated. Hands-free. Consistent. You're doing these things manually every single day. The same checks. The same steps. The same routine. Tasks do them automatically. So you can focus on the work that actually makes money. Every manual task you automate is time you get back. And time is the only thing you can never make more of. Save this post. Follow Himanshu Kumar for the task automation templates that run my entire workflow. ↓ 14. Explore Features Most People Never Touch. The video covers features that 95% of Claude Code users don't know exist. Because they watched a 3-minute TikTok about Claude Code and think they're experts now. They're not. They're using 5% of a tool that can do everything. The full tutorial goes deep into features that most tutorials skip because they're "too advanced." They're not too advanced. They're too valuable for lazy creators to bother explaining. This video explains all of them. Clearly. For beginners. The 5% of features you don't know about are the 5% that make people rich. ↓ Let's zoom out. I just broke down 14 sections of Claude Code. Setup and installation. Desktop app. Dependencies. Code editor integration. Basic usage. Commands. Modes and shortcuts. Planning prompts. Model selection. Git and version control. Memory and Claude. MD. Tasks and automation. Advanced features. All in one video. All free. All beginner friendly. The person who masters even half of these in the next 2 weeks will be in the top 1% of Claude Code users. The top 1% of Claude Code users are the ones charging $5,000-$10,000 per project and building them in a single afternoon. Everyone else is asking ChatGPT to fix their resume. Same tools. Same access. Completely different outcomes. Because one person treats AI like a toy. And the other treats it like a business. ↓ Here's the hard truth nobody wants to hear. You don't have a talent problem. You don't have an intelligence problem. You don't have a resources problem. You have an action problem. Everything I just listed has a free tutorial right here in the attached video. 33 minutes. That's it. 33 minutes to learn the tool that people are using to build $5,000-$20,000/month businesses. You spent more time today scrolling Twitter than it takes to watch this video. You spent more time this week watching Netflix than it takes to master Claude Code basics. You spent more time this month doing nothing than it would take to completely change your income. The information is free. The tool is accessible. The opportunity is here. The only thing missing is you caring enough to start. ↓ CANCEL your plans this week. This isn't optional anymore. The people learning Claude Code right now will be building apps for the people who didn't learn it. That's not a prediction. That's already happening. Companies are replacing $150/hour developers with one person and Claude Code. If you code: learn Claude Code or become half as valuable by next year. If you don't code: learn Claude Code or miss the biggest opportunity to start earning from tech without a CS degree. There's no path forward that doesn't include AI coding tools. None. You have one window. Right now. This week. ↓ Here's your action plan for the next 7 days: Day 1: Watch the full video. Install Claude Code. Set up dependencies. Day 2: Learn basic usage. Try 5 different commands. Day 3: Write your first planning prompt. Build a small project. Day 4: Set up Claude. MD. Configure your memory file. Day 5: Master modes and shortcuts. Build a second project faster. Day 6: Set up Git integration. Automate with tasks. Day 7: Build something real. A tool, an app, a website. Ship it. 7 days. One tool. One completely different skill set. One completely different income potential. Or 7 more days of scrolling Twitter watching other people build things while you "plan to start." Your call. ↓ This is the most important video you'll watch this year. 33 minutes. Complete Claude Code mastery. From zero to building real projects. Save this post. Come back to it every single day this week. Check off each section as you complete it. Follow Himanshu Kumarfor daily Claude Code breakdowns, advanced tutorials, and the exact workflows that are turning beginners into $10K/month builders. The only thing between you and $10K/month with Claude Code is this video and 7 days. Don't waste them. You Must Follow me Himanshu Kumar, so i can send you DM.
35:48

CANCEL Your Weekend Plans, & Learn Claude Code Today. This Claude Code teaches more about vibe-coding in 30 mins than most tutorials do in hours. Save this, it'll change how you build forever People are building entire apps and charging clients $5,000 to $20,000 using Claude Code. This Claude Code video is a goldmine. Full Claude Code tutorial. Beginner to pro. Every feature. Every setup step. Every best practice. Zero prior knowledge needed. Save it. Watch it tonight. Not tomorrow. Tonight. Follow Himanshu Kumar so you don't miss the breakdowns for each feature. This is your complete Claude Code roadmap. Lose it and you lose the next 12 months of income. ↓ 1. Understand What Claude Code Actually Is. You think Claude Code is just another chatbot. It's not. And that misunderstanding is why you're broke. ChatGPT gives you text. Claude Code gives you software. It runs in your terminal. It reads your entire codebase. It writes files directly to your project. It runs commands on your machine. It debugs errors autonomously. It builds features end to end. You're not chatting. You're deploying a developer. One that works 24/7. Never asks for a raise. Never calls in sick. Never pushes broken code at 5 PM on a Friday. People are charging clients $5,000-$10,000 for apps they built with Claude Code in 3 hours. And you didn't even know this tool existed because you're still asking ChatGPT to write you a to-do list. The gap between you and people making money with AI isn't intelligence. It's awareness. Now you're aware. Save this post. Follow Himanshu Kumar for the complete breakdown of every Claude Code feature. ↓ 2. Set Up Claude Code Properly. Most people quit here. "It's too complicated." "I don't know terminal." "I'll set it up later." Later never comes. And "complicated" means "I watched for 30 seconds and gave up." The setup takes 10 minutes. Install Node.js. Install Claude Code via npm. Authenticate your account. Open your terminal. Done. 10 minutes. You spent longer this morning deciding what to have for breakfast. The video walks through every single click. Every command. Every screen. Assuming you know absolutely nothing. If you can download an app on your phone, you can set up Claude Code. It's the same level of difficulty. But you'll still tell yourself it's "too technical" because that excuse is more comfortable than admitting you're just scared to try something new. This is the setup that everything else builds on. Skip it and nothing works. ↓ 3. Use the Desktop App. You don't even need to live in the terminal if you don't want to. Claude Code has a desktop app. Clean interface. Visual feedback. Everything you need without touching command line. But here's the thing most people don't know: The desktop app isn't just a pretty wrapper. It lets you manage projects visually. See file changes in real time. Switch between projects instantly. The people making money with Claude Code use the desktop app for client projects because it's faster to manage multiple builds simultaneously. You're still opening 14 browser tabs to organize one project. They open one app and everything's there. Efficiency isn't a personality trait. It's a tool choice. Save this post. Follow Himanshu Kumar for the desktop app workflow that handles 5 client projects at once. ↓ 4. Install the Right Dependencies. This is where beginners silently fail and blame the tool. Claude Code needs certain dependencies installed to work properly. Miss one and everything breaks. Then you go on Twitter and say "Claude Code doesn't work." It works fine. You just didn't read the setup guide. The video covers every dependency you need. What to install. How to install it. How to verify it's working. No guessing. No Stack Overflow rabbit holes at midnight. No "why isn't this working" for 3 hours. Watch the dependency section once. Follow every step. Never deal with setup issues again. You spent more time last week troubleshooting a printer than this takes. ↓ 5. Work Inside Your Code Editor. Claude Code integrates directly with your code editor. VS Code. Cursor. Whatever you use. It's not a separate window you alt-tab between. It's right there. In your workflow. You type a request. Claude writes the code. The code appears in your editor. You review it. Accept it. Done. No copy pasting between windows. No reformatting code that got mangled in transit. No "which version was the right one." It's like pair programming with someone who never gets distracted, never argues about naming conventions, and actually writes code that works on the first try. Your current coding process is: Google the problem, read 5 answers on Stack Overflow, copy the wrong one, debug for an hour, find the right one, paste it in, break something else, repeat. Claude Code's process is: describe what you want, get working code, move on with your life. Same hour. One method produces working software. The other produces frustration and a browser history full of Stack Overflow tabs. Stop coding the hard way. Save this post. Follow Himanshu Kumar for code editor setup guides and integration tips. ↓ 6. Master Basic Usage. Most people learn 5% of a tool and say they "know" it. You "know" Photoshop because you can crop an image. You "know" Excel because you can sum a column. You "know" Claude Code because you asked it one question. Basic usage means: How to give Claude Code context about your project. How to ask for changes to existing code. How to generate new files and features. How to review what Claude produces. How to iterate when the output isn't perfect. These basics are the foundation of everything. Skip them and every advanced feature feels confusing. Master them and every advanced feature feels obvious. The video breaks down each one with real examples. Not theory. Actual usage on actual projects. You've been using AI tools at 5% capacity and wondering why your results are 5% of what others get. Save this post. Follow Himanshu Kumar for daily Claude Code usage tips. ↓ 7. Learn Every Command. Claude Code has commands that most users never discover. Because most users type one message and expect magic. That's not how professionals use it. Professionals use specific commands that tell Claude Code exactly what to do, how to do it, and what constraints to follow. The difference between a beginner and someone making $10K/month with Claude Code is knowing which command to use and when. The video walks through every single one. Not just what they do. But when to use each one. And why one command is better than another for specific situations. You've been using Claude Code like a hammer. These commands turn it into a full toolbox. Stop treating a power tool like a blunt instrument. Save this post. Follow Himanshu Kumar for the command cheat sheet I use daily. ↓ 8. Understand Modes and Shortcuts. Speed matters. The person who builds an app in 2 hours charges $5,000. The person who builds the same app in 2 days charges $2,000. Same app. Same quality. Different speed. Different income. Claude Code has modes that change how it operates. And shortcuts that cut your workflow time in half. Most people don't know either exists. They use Claude Code in default mode for everything. Like driving a car in first gear on the highway. Technically it works. But everyone is passing you. The video shows you every mode. Every shortcut. Every time-saving trick that separates the people charging $2,000 per project from the people charging $10,000. Speed is money. Literally. Save this post. Follow Himanshu Kumar for the shortcuts that cut my build time by 60%. ↓ 9. Write a Proper Planning Prompt. This is the section that separates amateurs from professionals. And it's the section most people skip. A planning prompt tells Claude Code what you're building before you start building it. Architecture. File structure. Technologies. Features. Constraints. Edge cases. Without a planning prompt, Claude Code guesses. And guessing produces garbage. With a planning prompt, Claude Code executes a clear plan. And clear plans produce working software. The video shows you exactly how to write a planning prompt that makes Claude Code produce professional-grade output on the first try. "But I just want to start coding." That's why your code breaks every time. That's why you restart projects 4 times. That's why nothing you build ever gets finished. Because you refuse to plan. A 5-minute planning prompt saves you 5 hours of debugging. But you'd rather skip the 5 minutes and suffer through the 5 hours because patience isn't your thing. And that's exactly why you're not making money. Planning is the most underpaid skill in coding. And the most overpaid when you master it. Save this post. Follow Himanshu Kumar for the planning prompt templates I use for every client project. ↓ 10. Choose the Right Model. Claude Code lets you select different AI models. Not all models are the same. Not all tasks need the same model. Using the most powerful model for a simple task wastes credits. Using a basic model for a complex task wastes time. The video explains: Which model to use for quick fixes. Which model to use for complex architecture. Which model to use for debugging. Which model to use for code generation. Most people pick one model and use it for everything. That's like using a sledgehammer to hang a picture frame. Model selection is strategy. And strategy is money. The people making $10K/month with Claude Code are strategic about every credit they spend. You're burning through credits because you use the most expensive model to write a hello world. ↓ 11. Use Git and Version Control. If you're not using version control, you're one mistake away from losing everything. Claude Code integrates with Git. Every change tracked. Every version saved. Every mistake reversible. Without Git: Claude makes a change. It breaks something. You can't undo it. You start over. 3 hours wasted. With Git: Claude makes a change. It breaks something. You roll back in 5 seconds. Keep working. Version control isn't optional. It's insurance. And the people not using it are the same people who say "I lost my entire project" like it's something that just happens. It doesn't just happen. It happens because you didn't set up Git. The video walks through the entire Git integration. Save this post. Follow Himanshu Kumar for the Git workflow that's saved every project I've ever built. ↓ 12. Set Up Claude MD and Memory. This is the feature that makes Claude Code feel like a real team member instead of a stranger you explain everything to every time. ClaudeMD is a memory file. You tell Claude Code about your project once. It remembers forever. Coding style preferences. Project architecture decisions. Technology stack. File naming conventions. Business logic rules. Without ClaudeMD: Every new conversation starts from zero. You explain the same things repeatedly. Output is inconsistent. With ClaudeMD: Claude knows your project. Claude follows your rules. Claude produces consistent, professional code. The difference between a sloppy freelancer and a reliable agency is consistency. Claude. MD gives you consistency without the agency overhead. Most people don't set this up and wonder why Claude Code gives different answers every time. ↓ 13. Automate with Tasks. This is where Claude Code stops being a tool and starts being an employee. Tasks let you define repeating workflows. "Every time I push code, run tests." "Every time I create a new file, add boilerplate." "Every time I start a session, check for errors." Automated. Hands-free. Consistent. You're doing these things manually every single day. The same checks. The same steps. The same routine. Tasks do them automatically. So you can focus on the work that actually makes money. Every manual task you automate is time you get back. And time is the only thing you can never make more of. Save this post. Follow Himanshu Kumar for the task automation templates that run my entire workflow. ↓ 14. Explore Features Most People Never Touch. The video covers features that 95% of Claude Code users don't know exist. Because they watched a 3-minute TikTok about Claude Code and think they're experts now. They're not. They're using 5% of a tool that can do everything. The full tutorial goes deep into features that most tutorials skip because they're "too advanced." They're not too advanced. They're too valuable for lazy creators to bother explaining. This video explains all of them. Clearly. For beginners. The 5% of features you don't know about are the 5% that make people rich. ↓ Let's zoom out. I just broke down 14 sections of Claude Code. Setup and installation. Desktop app. Dependencies. Code editor integration. Basic usage. Commands. Modes and shortcuts. Planning prompts. Model selection. Git and version control. Memory and Claude. MD. Tasks and automation. Advanced features. All in one video. All free. All beginner friendly. The person who masters even half of these in the next 2 weeks will be in the top 1% of Claude Code users. The top 1% of Claude Code users are the ones charging $5,000-$10,000 per project and building them in a single afternoon. Everyone else is asking ChatGPT to fix their resume. Same tools. Same access. Completely different outcomes. Because one person treats AI like a toy. And the other treats it like a business. ↓ Here's the hard truth nobody wants to hear. You don't have a talent problem. You don't have an intelligence problem. You don't have a resources problem. You have an action problem. Everything I just listed has a free tutorial right here in the attached video. 33 minutes. That's it. 33 minutes to learn the tool that people are using to build $5,000-$20,000/month businesses. You spent more time today scrolling Twitter than it takes to watch this video. You spent more time this week watching Netflix than it takes to master Claude Code basics. You spent more time this month doing nothing than it would take to completely change your income. The information is free. The tool is accessible. The opportunity is here. The only thing missing is you caring enough to start. ↓ CANCEL your plans this week. This isn't optional anymore. The people learning Claude Code right now will be building apps for the people who didn't learn it. That's not a prediction. That's already happening. Companies are replacing $150/hour developers with one person and Claude Code. If you code: learn Claude Code or become half as valuable by next year. If you don't code: learn Claude Code or miss the biggest opportunity to start earning from tech without a CS degree. There's no path forward that doesn't include AI coding tools. None. You have one window. Right now. This week. ↓ Here's your action plan for the next 7 days: Day 1: Watch the full video. Install Claude Code. Set up dependencies. Day 2: Learn basic usage. Try 5 different commands. Day 3: Write your first planning prompt. Build a small project. Day 4: Set up Claude. MD. Configure your memory file. Day 5: Master modes and shortcuts. Build a second project faster. Day 6: Set up Git integration. Automate with tasks. Day 7: Build something real. A tool, an app, a website. Ship it. 7 days. One tool. One completely different skill set. One completely different income potential. Or 7 more days of scrolling Twitter watching other people build things while you "plan to start." Your call. ↓ This is the most important video you'll watch this year. 33 minutes. Complete Claude Code mastery. From zero to building real projects. Save this post. Come back to it every single day this week. Check off each section as you complete it. Follow Himanshu Kumarfor daily Claude Code breakdowns, advanced tutorials, and the exact workflows that are turning beginners into $10K/month builders. The only thing between you and $10K/month with Claude Code is this video and 7 days. Don't waste them. You Must Follow me Himanshu Kumar, so i can send you DM.

Himanshu Kumar

85,668 Aufrufe • vor 4 Monaten

CANCEL Your Weekend Plans, and Learn Claude Code Today. $5,000/month. $10,000/month. $20,000/month. People are building entire apps and charging clients thousands using Claude Code. You're still Googling 'how to center a div.' While you're binge-watching a show you won't remember next week, a 19 year old with zero coding experience just built a $5,000 SaaS product in one afternoon using the tool I'm about to break down. Same laptop. Same internet. Same 24 hours. He has Claude Code. You have Netflix. That's the only difference. This YouTube video is a goldmine. Full Claude Code tutorial. Beginner to pro. Every feature. Every setup step. Every best practice. Zero prior knowledge needed. Save it. Watch it tonight. Not tomorrow. Tonight. Save this post. This is your complete Claude Code roadmap. Lose it and you lose the next 12 months of income. Follow Himanshu Kumar so you don't miss the breakdowns for each feature. ↓ 1. Understand What Claude Code Actually Is. You think Claude Code is just another chatbot. It's not. And that misunderstanding is why you're broke. ChatGPT gives you text. Claude Code gives you software. It runs in your terminal. It reads your entire codebase. It writes files directly to your project. It runs commands on your machine. It debugs errors autonomously. It builds features end to end. You're not chatting. You're deploying a developer. One that works 24/7. Never asks for a raise. Never calls in sick. Never pushes broken code at 5 PM on a Friday. People are charging clients $5,000-$10,000 for apps they built with Claude Code in 3 hours. And you didn't even know this tool existed because you're still asking ChatGPT to write you a to-do list. The gap between you and people making money with AI isn't intelligence. It's awareness. Now you're aware. Save this post. Follow Himanshu Kumar for the complete breakdown of every Claude Code feature. ↓ 2. Set Up Claude Code Properly. Most people quit here. "It's too complicated." "I don't know terminal." "I'll set it up later." Later never comes. And "complicated" means "I watched for 30 seconds and gave up." The setup takes 10 minutes. Install Node.js. Install Claude Code via npm. Authenticate your account. Open your terminal. Done. 10 minutes. You spent longer this morning deciding what to have for breakfast. The video walks through every single click. Every command. Every screen. Assuming you know absolutely nothing. If you can download an app on your phone, you can set up Claude Code. It's the same level of difficulty. But you'll still tell yourself it's "too technical" because that excuse is more comfortable than admitting you're just scared to try something new. This is the setup that everything else builds on. Skip it and nothing works. ↓ 3. Use the Desktop App. You don't even need to live in the terminal if you don't want to. Claude Code has a desktop app. Clean interface. Visual feedback. Everything you need without touching command line. But here's the thing most people don't know: The desktop app isn't just a pretty wrapper. It lets you manage projects visually. See file changes in real time. Switch between projects instantly. The people making money with Claude Code use the desktop app for client projects because it's faster to manage multiple builds simultaneously. You're still opening 14 browser tabs to organize one project. They open one app and everything's there. Efficiency isn't a personality trait. It's a tool choice. Save this post. Follow Himanshu Kumar for the desktop app workflow that handles 5 client projects at once. ↓ 4. Install the Right Dependencies. This is where beginners silently fail and blame the tool. Claude Code needs certain dependencies installed to work properly. Miss one and everything breaks. Then you go on Twitter and say "Claude Code doesn't work." It works fine. You just didn't read the setup guide. The video covers every dependency you need. What to install. How to install it. How to verify it's working. No guessing. No Stack Overflow rabbit holes at midnight. No "why isn't this working" for 3 hours. Watch the dependency section once. Follow every step. Never deal with setup issues again. You spent more time last week troubleshooting a printer than this takes. ↓ 5. Work Inside Your Code Editor. Claude Code integrates directly with your code editor. VS Code. Cursor. Whatever you use. It's not a separate window you alt-tab between. It's right there. In your workflow. You type a request. Claude writes the code. The code appears in your editor. You review it. Accept it. Done. No copy pasting between windows. No reformatting code that got mangled in transit. No "which version was the right one." It's like pair programming with someone who never gets distracted, never argues about naming conventions, and actually writes code that works on the first try. Your current coding process is: Google the problem, read 5 answers on Stack Overflow, copy the wrong one, debug for an hour, find the right one, paste it in, break something else, repeat. Claude Code's process is: describe what you want, get working code, move on with your life. Same hour. One method produces working software. The other produces frustration and a browser history full of Stack Overflow tabs. Stop coding the hard way. Save this post. Follow Himanshu Kumar for code editor setup guides and integration tips. ↓ 6. Master Basic Usage. Most people learn 5% of a tool and say they "know" it. You "know" Photoshop because you can crop an image. You "know" Excel because you can sum a column. You "know" Claude Code because you asked it one question. Basic usage means: How to give Claude Code context about your project. How to ask for changes to existing code. How to generate new files and features. How to review what Claude produces. How to iterate when the output isn't perfect. These basics are the foundation of everything. Skip them and every advanced feature feels confusing. Master them and every advanced feature feels obvious. The video breaks down each one with real examples. Not theory. Actual usage on actual projects. You've been using AI tools at 5% capacity and wondering why your results are 5% of what others get. Save this post. Follow Himanshu Kumar for daily Claude Code usage tips. ↓ 7. Learn Every Command. Claude Code has commands that most users never discover. Because most users type one message and expect magic. That's not how professionals use it. Professionals use specific commands that tell Claude Code exactly what to do, how to do it, and what constraints to follow. The difference between a beginner and someone making $10K/month with Claude Code is knowing which command to use and when. The video walks through every single one. Not just what they do. But when to use each one. And why one command is better than another for specific situations. You've been using Claude Code like a hammer. These commands turn it into a full toolbox. Stop treating a power tool like a blunt instrument. Save this post. Follow Himanshu Kumar for the command cheat sheet I use daily. ↓ 8. Understand Modes and Shortcuts. Speed matters. The person who builds an app in 2 hours charges $5,000. The person who builds the same app in 2 days charges $2,000. Same app. Same quality. Different speed. Different income. Claude Code has modes that change how it operates. And shortcuts that cut your workflow time in half. Most people don't know either exists. They use Claude Code in default mode for everything. Like driving a car in first gear on the highway. Technically it works. But everyone is passing you. The video shows you every mode. Every shortcut. Every time-saving trick that separates the people charging $2,000 per project from the people charging $10,000. Speed is money. Literally. Save this post. Follow Himanshu Kumar for the shortcuts that cut my build time by 60%. ↓ 9. Write a Proper Planning Prompt. This is the section that separates amateurs from professionals. And it's the section most people skip. A planning prompt tells Claude Code what you're building before you start building it. Architecture. File structure. Technologies. Features. Constraints. Edge cases. Without a planning prompt, Claude Code guesses. And guessing produces garbage. With a planning prompt, Claude Code executes a clear plan. And clear plans produce working software. The video shows you exactly how to write a planning prompt that makes Claude Code produce professional-grade output on the first try. "But I just want to start coding." That's why your code breaks every time. That's why you restart projects 4 times. That's why nothing you build ever gets finished. Because you refuse to plan. A 5-minute planning prompt saves you 5 hours of debugging. But you'd rather skip the 5 minutes and suffer through the 5 hours because patience isn't your thing. And that's exactly why you're not making money. Planning is the most underpaid skill in coding. And the most overpaid when you master it. Save this post. Follow Himanshu Kumar for the planning prompt templates I use for every client project. ↓ 10. Choose the Right Model. Claude Code lets you select different AI models. Not all models are the same. Not all tasks need the same model. Using the most powerful model for a simple task wastes credits. Using a basic model for a complex task wastes time. The video explains: Which model to use for quick fixes. Which model to use for complex architecture. Which model to use for debugging. Which model to use for code generation. Most people pick one model and use it for everything. That's like using a sledgehammer to hang a picture frame. Model selection is strategy. And strategy is money. The people making $10K/month with Claude Code are strategic about every credit they spend. You're burning through credits because you use the most expensive model to write a hello world. ↓ 11. Use Git and Version Control. If you're not using version control, you're one mistake away from losing everything. Claude Code integrates with Git. Every change tracked. Every version saved. Every mistake reversible. Without Git: Claude makes a change. It breaks something. You can't undo it. You start over. 3 hours wasted. With Git: Claude makes a change. It breaks something. You roll back in 5 seconds. Keep working. Version control isn't optional. It's insurance. And the people not using it are the same people who say "I lost my entire project" like it's something that just happens. It doesn't just happen. It happens because you didn't set up Git. The video walks through the entire Git integration. Save this post. Follow Himanshu Kumar for the Git workflow that's saved every project I've ever built. ↓ 12. Set Up Claude.MD and Memory. This is the feature that makes Claude Code feel like a real team member instead of a stranger you explain everything to every time. ClaudeMD is a memory file. You tell Claude Code about your project once. It remembers forever. Coding style preferences. Project architecture decisions. Technology stack. File naming conventions. Business logic rules. Without ClaudeMD: Every new conversation starts from zero. You explain the same things repeatedly. Output is inconsistent. With ClaudeMD: Claude knows your project. Claude follows your rules. Claude produces consistent, professional code. The difference between a sloppy freelancer and a reliable agency is consistency. Claude. MD gives you consistency without the agency overhead. Most people don't set this up and wonder why Claude Code gives different answers every time. ↓ 13. Automate with Tasks. This is where Claude Code stops being a tool and starts being an employee. Tasks let you define repeating workflows. "Every time I push code, run tests." "Every time I create a new file, add boilerplate." "Every time I start a session, check for errors." Automated. Hands-free. Consistent. You're doing these things manually every single day. The same checks. The same steps. The same routine. Tasks do them automatically. So you can focus on the work that actually makes money. Every manual task you automate is time you get back. And time is the only thing you can never make more of. Save this post. Follow Himanshu Kumar for the task automation templates that run my entire workflow. ↓ 14. Explore Features Most People Never Touch. The video covers features that 95% of Claude Code users don't know exist. Because they watched a 3-minute TikTok about Claude Code and think they're experts now. They're not. They're using 5% of a tool that can do everything. The full tutorial goes deep into features that most tutorials skip because they're "too advanced." They're not too advanced. They're too valuable for lazy creators to bother explaining. This video explains all of them. Clearly. For beginners. The 5% of features you don't know about are the 5% that make people rich. ↓ Let's zoom out. I just broke down 14 sections of Claude Code. Setup and installation. Desktop app. Dependencies. Code editor integration. Basic usage. Commands. Modes and shortcuts. Planning prompts. Model selection. Git and version control. Memory and Claude. MD. Tasks and automation. Advanced features. All in one video. All free. All beginner friendly. The person who masters even half of these in the next 2 weeks will be in the top 1% of Claude Code users. The top 1% of Claude Code users are the ones charging $5,000-$10,000 per project and building them in a single afternoon. Everyone else is asking ChatGPT to fix their resume. Same tools. Same access. Completely different outcomes. Because one person treats AI like a toy. And the other treats it like a business. ↓ Here's the hard truth nobody wants to hear. You don't have a talent problem. You don't have an intelligence problem. You don't have a resources problem. You have an action problem. Everything I just listed has a free tutorial right here in the attached video. 33 minutes. That's it. 33 minutes to learn the tool that people are using to build $5,000-$20,000/month businesses. You spent more time today scrolling Twitter than it takes to watch this video. You spent more time this week watching Netflix than it takes to master Claude Code basics. You spent more time this month doing nothing than it would take to completely change your income. The information is free. The tool is accessible. The opportunity is here. The only thing missing is you caring enough to start. ↓ CANCEL your plans this week. This isn't optional anymore. The people learning Claude Code right now will be building apps for the people who didn't learn it. That's not a prediction. That's already happening. Companies are replacing $150/hour developers with one person and Claude Code. If you code: learn Claude Code or become half as valuable by next year. If you don't code: learn Claude Code or miss the biggest opportunity to start earning from tech without a CS degree. There's no path forward that doesn't include AI coding tools. None. You have one window. Right now. This week. ↓ Here's your action plan for the next 7 days: Day 1: Watch the full video. Install Claude Code. Set up dependencies. Day 2: Learn basic usage. Try 5 different commands. Day 3: Write your first planning prompt. Build a small project. Day 4: Set up Claude. MD. Configure your memory file. Day 5: Master modes and shortcuts. Build a second project faster. Day 6: Set up Git integration. Automate with tasks. Day 7: Build something real. A tool, an app, a website. Ship it. 7 days. One tool. One completely different skill set. One completely different income potential. Or 7 more days of scrolling Twitter watching other people build things while you "plan to start." Your call. ↓ This is the most important video you'll watch this year. 33 minutes. Complete Claude Code mastery. From zero to building real projects. Save this post. Come back to it every single day this week. Check off each section as you complete it. Follow Himanshu Kumar for daily Claude Code breakdowns, advanced tutorials, and the exact workflows that are turning beginners into $10K/month builders. The only thing between you and $10K/month with Claude Code is this video and 7 days. Don't waste them. You Must Follow me Himanshu Kumar, so i can send you DM.
35:48

CANCEL Your Weekend Plans, and Learn Claude Code Today. $5,000/month. $10,000/month. $20,000/month. People are building entire apps and charging clients thousands using Claude Code. You're still Googling 'how to center a div.' While you're binge-watching a show you won't remember next week, a 19 year old with zero coding experience just built a $5,000 SaaS product in one afternoon using the tool I'm about to break down. Same laptop. Same internet. Same 24 hours. He has Claude Code. You have Netflix. That's the only difference. This YouTube video is a goldmine. Full Claude Code tutorial. Beginner to pro. Every feature. Every setup step. Every best practice. Zero prior knowledge needed. Save it. Watch it tonight. Not tomorrow. Tonight. Save this post. This is your complete Claude Code roadmap. Lose it and you lose the next 12 months of income. Follow Himanshu Kumar so you don't miss the breakdowns for each feature. ↓ 1. Understand What Claude Code Actually Is. You think Claude Code is just another chatbot. It's not. And that misunderstanding is why you're broke. ChatGPT gives you text. Claude Code gives you software. It runs in your terminal. It reads your entire codebase. It writes files directly to your project. It runs commands on your machine. It debugs errors autonomously. It builds features end to end. You're not chatting. You're deploying a developer. One that works 24/7. Never asks for a raise. Never calls in sick. Never pushes broken code at 5 PM on a Friday. People are charging clients $5,000-$10,000 for apps they built with Claude Code in 3 hours. And you didn't even know this tool existed because you're still asking ChatGPT to write you a to-do list. The gap between you and people making money with AI isn't intelligence. It's awareness. Now you're aware. Save this post. Follow Himanshu Kumar for the complete breakdown of every Claude Code feature. ↓ 2. Set Up Claude Code Properly. Most people quit here. "It's too complicated." "I don't know terminal." "I'll set it up later." Later never comes. And "complicated" means "I watched for 30 seconds and gave up." The setup takes 10 minutes. Install Node.js. Install Claude Code via npm. Authenticate your account. Open your terminal. Done. 10 minutes. You spent longer this morning deciding what to have for breakfast. The video walks through every single click. Every command. Every screen. Assuming you know absolutely nothing. If you can download an app on your phone, you can set up Claude Code. It's the same level of difficulty. But you'll still tell yourself it's "too technical" because that excuse is more comfortable than admitting you're just scared to try something new. This is the setup that everything else builds on. Skip it and nothing works. ↓ 3. Use the Desktop App. You don't even need to live in the terminal if you don't want to. Claude Code has a desktop app. Clean interface. Visual feedback. Everything you need without touching command line. But here's the thing most people don't know: The desktop app isn't just a pretty wrapper. It lets you manage projects visually. See file changes in real time. Switch between projects instantly. The people making money with Claude Code use the desktop app for client projects because it's faster to manage multiple builds simultaneously. You're still opening 14 browser tabs to organize one project. They open one app and everything's there. Efficiency isn't a personality trait. It's a tool choice. Save this post. Follow Himanshu Kumar for the desktop app workflow that handles 5 client projects at once. ↓ 4. Install the Right Dependencies. This is where beginners silently fail and blame the tool. Claude Code needs certain dependencies installed to work properly. Miss one and everything breaks. Then you go on Twitter and say "Claude Code doesn't work." It works fine. You just didn't read the setup guide. The video covers every dependency you need. What to install. How to install it. How to verify it's working. No guessing. No Stack Overflow rabbit holes at midnight. No "why isn't this working" for 3 hours. Watch the dependency section once. Follow every step. Never deal with setup issues again. You spent more time last week troubleshooting a printer than this takes. ↓ 5. Work Inside Your Code Editor. Claude Code integrates directly with your code editor. VS Code. Cursor. Whatever you use. It's not a separate window you alt-tab between. It's right there. In your workflow. You type a request. Claude writes the code. The code appears in your editor. You review it. Accept it. Done. No copy pasting between windows. No reformatting code that got mangled in transit. No "which version was the right one." It's like pair programming with someone who never gets distracted, never argues about naming conventions, and actually writes code that works on the first try. Your current coding process is: Google the problem, read 5 answers on Stack Overflow, copy the wrong one, debug for an hour, find the right one, paste it in, break something else, repeat. Claude Code's process is: describe what you want, get working code, move on with your life. Same hour. One method produces working software. The other produces frustration and a browser history full of Stack Overflow tabs. Stop coding the hard way. Save this post. Follow Himanshu Kumar for code editor setup guides and integration tips. ↓ 6. Master Basic Usage. Most people learn 5% of a tool and say they "know" it. You "know" Photoshop because you can crop an image. You "know" Excel because you can sum a column. You "know" Claude Code because you asked it one question. Basic usage means: How to give Claude Code context about your project. How to ask for changes to existing code. How to generate new files and features. How to review what Claude produces. How to iterate when the output isn't perfect. These basics are the foundation of everything. Skip them and every advanced feature feels confusing. Master them and every advanced feature feels obvious. The video breaks down each one with real examples. Not theory. Actual usage on actual projects. You've been using AI tools at 5% capacity and wondering why your results are 5% of what others get. Save this post. Follow Himanshu Kumar for daily Claude Code usage tips. ↓ 7. Learn Every Command. Claude Code has commands that most users never discover. Because most users type one message and expect magic. That's not how professionals use it. Professionals use specific commands that tell Claude Code exactly what to do, how to do it, and what constraints to follow. The difference between a beginner and someone making $10K/month with Claude Code is knowing which command to use and when. The video walks through every single one. Not just what they do. But when to use each one. And why one command is better than another for specific situations. You've been using Claude Code like a hammer. These commands turn it into a full toolbox. Stop treating a power tool like a blunt instrument. Save this post. Follow Himanshu Kumar for the command cheat sheet I use daily. ↓ 8. Understand Modes and Shortcuts. Speed matters. The person who builds an app in 2 hours charges $5,000. The person who builds the same app in 2 days charges $2,000. Same app. Same quality. Different speed. Different income. Claude Code has modes that change how it operates. And shortcuts that cut your workflow time in half. Most people don't know either exists. They use Claude Code in default mode for everything. Like driving a car in first gear on the highway. Technically it works. But everyone is passing you. The video shows you every mode. Every shortcut. Every time-saving trick that separates the people charging $2,000 per project from the people charging $10,000. Speed is money. Literally. Save this post. Follow Himanshu Kumar for the shortcuts that cut my build time by 60%. ↓ 9. Write a Proper Planning Prompt. This is the section that separates amateurs from professionals. And it's the section most people skip. A planning prompt tells Claude Code what you're building before you start building it. Architecture. File structure. Technologies. Features. Constraints. Edge cases. Without a planning prompt, Claude Code guesses. And guessing produces garbage. With a planning prompt, Claude Code executes a clear plan. And clear plans produce working software. The video shows you exactly how to write a planning prompt that makes Claude Code produce professional-grade output on the first try. "But I just want to start coding." That's why your code breaks every time. That's why you restart projects 4 times. That's why nothing you build ever gets finished. Because you refuse to plan. A 5-minute planning prompt saves you 5 hours of debugging. But you'd rather skip the 5 minutes and suffer through the 5 hours because patience isn't your thing. And that's exactly why you're not making money. Planning is the most underpaid skill in coding. And the most overpaid when you master it. Save this post. Follow Himanshu Kumar for the planning prompt templates I use for every client project. ↓ 10. Choose the Right Model. Claude Code lets you select different AI models. Not all models are the same. Not all tasks need the same model. Using the most powerful model for a simple task wastes credits. Using a basic model for a complex task wastes time. The video explains: Which model to use for quick fixes. Which model to use for complex architecture. Which model to use for debugging. Which model to use for code generation. Most people pick one model and use it for everything. That's like using a sledgehammer to hang a picture frame. Model selection is strategy. And strategy is money. The people making $10K/month with Claude Code are strategic about every credit they spend. You're burning through credits because you use the most expensive model to write a hello world. ↓ 11. Use Git and Version Control. If you're not using version control, you're one mistake away from losing everything. Claude Code integrates with Git. Every change tracked. Every version saved. Every mistake reversible. Without Git: Claude makes a change. It breaks something. You can't undo it. You start over. 3 hours wasted. With Git: Claude makes a change. It breaks something. You roll back in 5 seconds. Keep working. Version control isn't optional. It's insurance. And the people not using it are the same people who say "I lost my entire project" like it's something that just happens. It doesn't just happen. It happens because you didn't set up Git. The video walks through the entire Git integration. Save this post. Follow Himanshu Kumar for the Git workflow that's saved every project I've ever built. ↓ 12. Set Up Claude.MD and Memory. This is the feature that makes Claude Code feel like a real team member instead of a stranger you explain everything to every time. ClaudeMD is a memory file. You tell Claude Code about your project once. It remembers forever. Coding style preferences. Project architecture decisions. Technology stack. File naming conventions. Business logic rules. Without ClaudeMD: Every new conversation starts from zero. You explain the same things repeatedly. Output is inconsistent. With ClaudeMD: Claude knows your project. Claude follows your rules. Claude produces consistent, professional code. The difference between a sloppy freelancer and a reliable agency is consistency. Claude. MD gives you consistency without the agency overhead. Most people don't set this up and wonder why Claude Code gives different answers every time. ↓ 13. Automate with Tasks. This is where Claude Code stops being a tool and starts being an employee. Tasks let you define repeating workflows. "Every time I push code, run tests." "Every time I create a new file, add boilerplate." "Every time I start a session, check for errors." Automated. Hands-free. Consistent. You're doing these things manually every single day. The same checks. The same steps. The same routine. Tasks do them automatically. So you can focus on the work that actually makes money. Every manual task you automate is time you get back. And time is the only thing you can never make more of. Save this post. Follow Himanshu Kumar for the task automation templates that run my entire workflow. ↓ 14. Explore Features Most People Never Touch. The video covers features that 95% of Claude Code users don't know exist. Because they watched a 3-minute TikTok about Claude Code and think they're experts now. They're not. They're using 5% of a tool that can do everything. The full tutorial goes deep into features that most tutorials skip because they're "too advanced." They're not too advanced. They're too valuable for lazy creators to bother explaining. This video explains all of them. Clearly. For beginners. The 5% of features you don't know about are the 5% that make people rich. ↓ Let's zoom out. I just broke down 14 sections of Claude Code. Setup and installation. Desktop app. Dependencies. Code editor integration. Basic usage. Commands. Modes and shortcuts. Planning prompts. Model selection. Git and version control. Memory and Claude. MD. Tasks and automation. Advanced features. All in one video. All free. All beginner friendly. The person who masters even half of these in the next 2 weeks will be in the top 1% of Claude Code users. The top 1% of Claude Code users are the ones charging $5,000-$10,000 per project and building them in a single afternoon. Everyone else is asking ChatGPT to fix their resume. Same tools. Same access. Completely different outcomes. Because one person treats AI like a toy. And the other treats it like a business. ↓ Here's the hard truth nobody wants to hear. You don't have a talent problem. You don't have an intelligence problem. You don't have a resources problem. You have an action problem. Everything I just listed has a free tutorial right here in the attached video. 33 minutes. That's it. 33 minutes to learn the tool that people are using to build $5,000-$20,000/month businesses. You spent more time today scrolling Twitter than it takes to watch this video. You spent more time this week watching Netflix than it takes to master Claude Code basics. You spent more time this month doing nothing than it would take to completely change your income. The information is free. The tool is accessible. The opportunity is here. The only thing missing is you caring enough to start. ↓ CANCEL your plans this week. This isn't optional anymore. The people learning Claude Code right now will be building apps for the people who didn't learn it. That's not a prediction. That's already happening. Companies are replacing $150/hour developers with one person and Claude Code. If you code: learn Claude Code or become half as valuable by next year. If you don't code: learn Claude Code or miss the biggest opportunity to start earning from tech without a CS degree. There's no path forward that doesn't include AI coding tools. None. You have one window. Right now. This week. ↓ Here's your action plan for the next 7 days: Day 1: Watch the full video. Install Claude Code. Set up dependencies. Day 2: Learn basic usage. Try 5 different commands. Day 3: Write your first planning prompt. Build a small project. Day 4: Set up Claude. MD. Configure your memory file. Day 5: Master modes and shortcuts. Build a second project faster. Day 6: Set up Git integration. Automate with tasks. Day 7: Build something real. A tool, an app, a website. Ship it. 7 days. One tool. One completely different skill set. One completely different income potential. Or 7 more days of scrolling Twitter watching other people build things while you "plan to start." Your call. ↓ This is the most important video you'll watch this year. 33 minutes. Complete Claude Code mastery. From zero to building real projects. Save this post. Come back to it every single day this week. Check off each section as you complete it. Follow Himanshu Kumar for daily Claude Code breakdowns, advanced tutorials, and the exact workflows that are turning beginners into $10K/month builders. The only thing between you and $10K/month with Claude Code is this video and 7 days. Don't waste them. You Must Follow me Himanshu Kumar, so i can send you DM.

Himanshu Kumar

101,793 Aufrufe • vor 5 Monaten

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.
0:26

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

58,796 Aufrufe • vor 4 Monaten

is genspark ($50M ARR in 6mo) underrated next to chatgpt, claude, gemini, and manus? i spent 34 minutes testing its “super ai agent” and how it actually works. 1/ you write one prompt and it runs through gpt-5, claude sonnet, gemini 2.5, and mistral large then gives you the best response. 2/ you upload one image and it runs it through nano banana, flux, and bytedance then returns the most realistic version. 3/ you generate a video and genspark routes it through wan 2.2, pika labs, gen-2, and runway ml combining the best clips and motion. 4/ you paste an idea for slides and it uses gpt-5, claude 3 opus, gemini advanced, and genspark’s slide model to create a full deck with visuals and market data. 5/ AI slides and building a fundraising deck with a few prompts (wasn't perfect, but it was a good start for my personal workflow) what's cool about genspark is it's inexpensive and does it all. kinda like the costco of LLMs. TLDR; you hand it one prompt + input, and genspark routes sub-tasks across models and tools behind the scenes. it’s orchestration over one ideal model. perspective shift. instead of jumping from model to model, llm to llm, genspark shows what the next generation of ai will look like orchestration over obsession. and for the rest of us using it, the only thing that matters is getting the best outcome. what other AI app should I review next? i'll keep doing it if it's helpful for folks.
34:35

is genspark ($50M ARR in 6mo) underrated next to chatgpt, claude, gemini, and manus? i spent 34 minutes testing its “super ai agent” and how it actually works. 1/ you write one prompt and it runs through gpt-5, claude sonnet, gemini 2.5, and mistral large then gives you the best response. 2/ you upload one image and it runs it through nano banana, flux, and bytedance then returns the most realistic version. 3/ you generate a video and genspark routes it through wan 2.2, pika labs, gen-2, and runway ml combining the best clips and motion. 4/ you paste an idea for slides and it uses gpt-5, claude 3 opus, gemini advanced, and genspark’s slide model to create a full deck with visuals and market data. 5/ AI slides and building a fundraising deck with a few prompts (wasn't perfect, but it was a good start for my personal workflow) what's cool about genspark is it's inexpensive and does it all. kinda like the costco of LLMs. TLDR; you hand it one prompt + input, and genspark routes sub-tasks across models and tools behind the scenes. it’s orchestration over one ideal model. perspective shift. instead of jumping from model to model, llm to llm, genspark shows what the next generation of ai will look like orchestration over obsession. and for the rest of us using it, the only thing that matters is getting the best outcome. what other AI app should I review next? i'll keep doing it if it's helpful for folks.

GREG ISENBERG

62,172 Aufrufe • vor 11 Monaten

My AI made Shopify pages are getting better and better everyday Here’s an example of a Shopify section I built with the reference page and the result on my store 👇 Guide: To make good AI landing pages, you need to use the same method as making good AI UGC or AI product images you have to take something that's already good as a reference for Claude/gemini to analyze and adapt for your product/brand for now you can't adapt full landing pages to your product because the Claude context gets bloated fast and you get poor output. Listicles are the only kind of page you can "one shot" with Claude. But Product pages are another story Analyze an existing page and adapting it to your product section by section is the way to go. The results are 10x better. here's an example (on the video): 1- I found this good product section from im8's product page. I screen-recorded the section on both desktop and mobile, going through the animations to capture the dynamism that a screenshot wouldn’t show. Then I asked Claude Web or Gemini to analyze the recording and produce a very detailed report. Full prompt is on my TG channel, it's quite long. 2- then ask Claude (inside your Shopify brand project folder): "I have a detailed UI/UX specification document for a product page section I want to adapt to my product. Recreate this exactly on Shopify as a section template and adapt it to [name of the product] using the brand guidelines" (paste the result prompt from step 1 ). 3- you will have your section ready after 3-4 minutes. you'll probably have to change a few things. spacing, small visual bugs, price not appearing correctly. it will take you 5 minutes maximum. 4- then you can ask Claude to make 4 different variations of the section using different designs and pick the best one using this prompt: "Create 4 design variations of this section. Keep the content and layout structure identical across all, only vary the visual treatment (color usage, typography hierarchy, spacing, component styling). I will choose the one I like the most." after that you have a pretty good section, and you can do the process again for all sections of the page. The less complex the section, the faster the process will be. note: I know the AI result is not perfect, but it's pretty impressive imo and it will only get better.
0:27

My AI made Shopify pages are getting better and better everyday Here’s an example of a Shopify section I built with the reference page and the result on my store 👇 Guide: To make good AI landing pages, you need to use the same method as making good AI UGC or AI product images you have to take something that's already good as a reference for Claude/gemini to analyze and adapt for your product/brand for now you can't adapt full landing pages to your product because the Claude context gets bloated fast and you get poor output. Listicles are the only kind of page you can "one shot" with Claude. But Product pages are another story Analyze an existing page and adapting it to your product section by section is the way to go. The results are 10x better. here's an example (on the video): 1- I found this good product section from im8's product page. I screen-recorded the section on both desktop and mobile, going through the animations to capture the dynamism that a screenshot wouldn’t show. Then I asked Claude Web or Gemini to analyze the recording and produce a very detailed report. Full prompt is on my TG channel, it's quite long. 2- then ask Claude (inside your Shopify brand project folder): "I have a detailed UI/UX specification document for a product page section I want to adapt to my product. Recreate this exactly on Shopify as a section template and adapt it to [name of the product] using the brand guidelines" (paste the result prompt from step 1 ). 3- you will have your section ready after 3-4 minutes. you'll probably have to change a few things. spacing, small visual bugs, price not appearing correctly. it will take you 5 minutes maximum. 4- then you can ask Claude to make 4 different variations of the section using different designs and pick the best one using this prompt: "Create 4 design variations of this section. Keep the content and layout structure identical across all, only vary the visual treatment (color usage, typography hierarchy, spacing, component styling). I will choose the one I like the most." after that you have a pretty good section, and you can do the process again for all sections of the page. The less complex the section, the faster the process will be. note: I know the AI result is not perfect, but it's pretty impressive imo and it will only get better.

Olivier

84,679 Aufrufe • vor 6 Monaten

Tom Crawshaw has been building automations for 9 years with $25 million in client revenue to his name. He just walked me through his Claude Code content system that's generating millions of views and tens of thousands of followers. Here's what I learned: 1. Skills beat Projects in Claude. Projects load every context file on every message and burn your token window. Skills work like a book where the LLM reads the table of contents and pulls only the chapter it needs for the job. Same context, fraction of the tokens. 2. He has a /content-create slash command that runs the entire pipeline. Voice profile, copywriting principles, hook generation, image direction. One command. He doesn't write anything from scratch anymore. 3. His voice profile auto-updates weekly. He wrote a script that hits the X API every 7 days, pulls his top-performing posts by engagement, and rewrites his voice profile based on what's actually working. The profile evolves on its own. 4. He distilled a master copywriter's entire body of work into a single markdown file. Grabbed every Alen Sultanic post he could find, dropped it into Claude, asked for the core principles, fed it into the skill. Now every post he writes runs through those principles automatically. 5. The hook generator scores 16 hooks per post against 7 criteria. Curiosity loops, specificity, sensory, credibility, voice match, and a couple of others. He never picks the #1 by default. Sometimes he splices the first line of one hook with the body of another. The taste is still his. 6. /insights is a native Claude Code command nobody talks about. It analyzes every session you've ever run and produces a full report on your usage patterns, where things break down, and prompts you can paste back into Claude to fix them. I had never heard of it. I'm running it tonight. 7. He spends most of his time on hooks and images. If those two suck, the body copy doesn't matter. Nobody reads it. 8. Image generation is never one-shot. He keeps a folder of reference images that have worked before and feeds them into Nano Banana/GPT Image 2 every time. Then he takes the 80-90% output and finishes it in Canva using "magic grab" to move logos and clean up text. Last mile is human every time. 9. The humanizer step is non-negotiable. Strip em dashes. Kill the "it's not X, it's Y" pattern. Cut the triple negatives. Cut "no fluff." He still has to remind Claude mid-session because it drifts. If you're not auditing for AI tells, you're shipping slop. 10. Wisprflow is the most important tool in his stack. Not a content tool. An everything tool. His test for whether you should be using it: do you talk faster than you type? You do. Everyone does. Bonus fact he dropped: QWERTY was designed 200 years ago to slow typing down so old typewriters wouldn't jam. We've been carrying that forward ever since. Voice is finally undoing it. This was an inside look at how a serious operator Tom is using Claude Code to run a content engine. The good, the bad, the iteration, all of it. I hope you enjoy this one as much as I did. Go watch it.
57:27

Tom Crawshaw has been building automations for 9 years with $25 million in client revenue to his name. He just walked me through his Claude Code content system that's generating millions of views and tens of thousands of followers. Here's what I learned: 1. Skills beat Projects in Claude. Projects load every context file on every message and burn your token window. Skills work like a book where the LLM reads the table of contents and pulls only the chapter it needs for the job. Same context, fraction of the tokens. 2. He has a /content-create slash command that runs the entire pipeline. Voice profile, copywriting principles, hook generation, image direction. One command. He doesn't write anything from scratch anymore. 3. His voice profile auto-updates weekly. He wrote a script that hits the X API every 7 days, pulls his top-performing posts by engagement, and rewrites his voice profile based on what's actually working. The profile evolves on its own. 4. He distilled a master copywriter's entire body of work into a single markdown file. Grabbed every Alen Sultanic post he could find, dropped it into Claude, asked for the core principles, fed it into the skill. Now every post he writes runs through those principles automatically. 5. The hook generator scores 16 hooks per post against 7 criteria. Curiosity loops, specificity, sensory, credibility, voice match, and a couple of others. He never picks the #1 by default. Sometimes he splices the first line of one hook with the body of another. The taste is still his. 6. /insights is a native Claude Code command nobody talks about. It analyzes every session you've ever run and produces a full report on your usage patterns, where things break down, and prompts you can paste back into Claude to fix them. I had never heard of it. I'm running it tonight. 7. He spends most of his time on hooks and images. If those two suck, the body copy doesn't matter. Nobody reads it. 8. Image generation is never one-shot. He keeps a folder of reference images that have worked before and feeds them into Nano Banana/GPT Image 2 every time. Then he takes the 80-90% output and finishes it in Canva using "magic grab" to move logos and clean up text. Last mile is human every time. 9. The humanizer step is non-negotiable. Strip em dashes. Kill the "it's not X, it's Y" pattern. Cut the triple negatives. Cut "no fluff." He still has to remind Claude mid-session because it drifts. If you're not auditing for AI tells, you're shipping slop. 10. Wisprflow is the most important tool in his stack. Not a content tool. An everything tool. His test for whether you should be using it: do you talk faster than you type? You do. Everyone does. Bonus fact he dropped: QWERTY was designed 200 years ago to slow typing down so old typewriters wouldn't jam. We've been carrying that forward ever since. Voice is finally undoing it. This was an inside look at how a serious operator Tom is using Claude Code to run a content engine. The good, the bad, the iteration, all of it. I hope you enjoy this one as much as I did. Go watch it.

Corey Ganim

36,541 Aufrufe • vor 4 Monaten

HERMES AGENT LEARNS FROM ITS OWN MISTAKES. UPDATES ITS MEMORY. CREATES ITS OWN SKILLS. NO CLOUD. EVERYTHING STORED LOCALLY. THIS IS HOW THE SELF-IMPROVING LOOP WORKS. most agents start from zero every session. Hermes carries forward what it learned. THREE MEMORY SYSTEMS: 1. PROCEDURAL MEMORY (how to act) stored in ~/.hermes/skills/ as SKILL.md files. when the agent repeats a complex workflow, it saves the procedure as a reusable skill. next time the same task comes up, it follows the skill instead of figuring it out again. you can also create skills explicitly: "create a skill called video-prep that captures how I format my video scripts. spoken english, define jargon inline, no em-dashes, close with a catchphrase." the agent writes the SKILL.md. available as a slash command from that moment. Hermes ships with 90+ skills. the number grows the longer you use it. 2. SEMANTIC MEMORY (durable facts about you) stored in ~/.hermes/memory/memory.md the agent scans conversations for facts worth remembering. preferences, habits, corrections, project details. real example from the video: agent tried to scrape a YouTube channel. URL was wrong. it failed. it updated memory.md with the correct URL pattern so it never makes the same mistake again. you can also save explicitly: "save to memory that my favorite testing framework is pytest" the agent updates memory.md immediately. this file loads into context on every session. the agent knows you better every week. 3. EPISODIC MEMORY (chat history) stored in ~/.hermes/state.db (local SQLite). every conversation. every tool call. every result. searchable with FTS5 full-text search. "search our past sessions. what was the first thing I ever said to you?" the agent queries state.db and finds it. over time, auxiliary models consolidate episodic memory into semantic memory. distilling recurring patterns into durable facts. THE SELF-IMPROVING LOOP: every agent run follows this cycle: → you send a prompt → working memory loads: SOUL.md + memory.md + relevant skills + chat history → agent calls tools (terminal, browser, delegate_task) → agent completes the task, replies to you → AFTER the reply: agent checks "did I learn something worth saving?" → if yes: updates memory.md or creates a new skill → next session starts smarter than the last this happens automatically. you don't ask the agent to learn. it decides what to remember on its own. WHAT MAKES THIS DIFFERENT FROM CLAUDE CODE: Claude Code has memory too. but Hermes stores everything locally. no cloud. your data never leaves your machine. Claude Code doesn't auto-create skills from experience. Hermes turns repeated workflows into reusable procedures. Claude Code memory is instruction-based. Hermes memory is conversational and self-updating. over months of usage, Hermes builds a knowledge base of your preferences, your projects, your mistakes, and the procedures that work for your specific workflow. the agent that remembers your birthday also remembers why your last deploy failed. NO EMBEDDINGS. PLAIN TEXT. Hermes does not use embeddings or RAG for memory. skill and memory search runs on plain text keyword matching. simpler. faster. no vector database to maintain. works entirely offline on your local machine. DELEGATE TO CLAUDE CODE: Hermes can spawn a sub-agent that runs Claude Code in headless mode: "spawn a sub-agent using Claude CLI to build a Python script that fetches the top 5 Hacker News stories to markdown." Hermes delegates. Claude Code writes the code. result returns to Hermes. Hermes runs the script and delivers the output. use Hermes for orchestration. use Claude Code for heavy coding. both tools. not competitors. WHAT HERMES DOES NOT HAVE: no built-in eval or LMOps system. no LangSmith, no LangFuse integration out of the box. trajectory export and logs exist but there is no automated quality tracking. if you need eval, build it yourself or connect external tools. the loop is self-improving. measuring how well it improves is on you. comment LOOP and I'll send you the configs that control how fast Hermes learns and what it remembers. memory limits, skill auto-creation triggers, and the auxiliary model that runs the learning. Replace your entire team with 8 hermes agents👇
20:54

HERMES AGENT LEARNS FROM ITS OWN MISTAKES. UPDATES ITS MEMORY. CREATES ITS OWN SKILLS. NO CLOUD. EVERYTHING STORED LOCALLY. THIS IS HOW THE SELF-IMPROVING LOOP WORKS. most agents start from zero every session. Hermes carries forward what it learned. THREE MEMORY SYSTEMS: 1. PROCEDURAL MEMORY (how to act) stored in ~/.hermes/skills/ as SKILL.md files. when the agent repeats a complex workflow, it saves the procedure as a reusable skill. next time the same task comes up, it follows the skill instead of figuring it out again. you can also create skills explicitly: "create a skill called video-prep that captures how I format my video scripts. spoken english, define jargon inline, no em-dashes, close with a catchphrase." the agent writes the SKILL.md. available as a slash command from that moment. Hermes ships with 90+ skills. the number grows the longer you use it. 2. SEMANTIC MEMORY (durable facts about you) stored in ~/.hermes/memory/memory.md the agent scans conversations for facts worth remembering. preferences, habits, corrections, project details. real example from the video: agent tried to scrape a YouTube channel. URL was wrong. it failed. it updated memory.md with the correct URL pattern so it never makes the same mistake again. you can also save explicitly: "save to memory that my favorite testing framework is pytest" the agent updates memory.md immediately. this file loads into context on every session. the agent knows you better every week. 3. EPISODIC MEMORY (chat history) stored in ~/.hermes/state.db (local SQLite). every conversation. every tool call. every result. searchable with FTS5 full-text search. "search our past sessions. what was the first thing I ever said to you?" the agent queries state.db and finds it. over time, auxiliary models consolidate episodic memory into semantic memory. distilling recurring patterns into durable facts. THE SELF-IMPROVING LOOP: every agent run follows this cycle: → you send a prompt → working memory loads: SOUL.md + memory.md + relevant skills + chat history → agent calls tools (terminal, browser, delegate_task) → agent completes the task, replies to you → AFTER the reply: agent checks "did I learn something worth saving?" → if yes: updates memory.md or creates a new skill → next session starts smarter than the last this happens automatically. you don't ask the agent to learn. it decides what to remember on its own. WHAT MAKES THIS DIFFERENT FROM CLAUDE CODE: Claude Code has memory too. but Hermes stores everything locally. no cloud. your data never leaves your machine. Claude Code doesn't auto-create skills from experience. Hermes turns repeated workflows into reusable procedures. Claude Code memory is instruction-based. Hermes memory is conversational and self-updating. over months of usage, Hermes builds a knowledge base of your preferences, your projects, your mistakes, and the procedures that work for your specific workflow. the agent that remembers your birthday also remembers why your last deploy failed. NO EMBEDDINGS. PLAIN TEXT. Hermes does not use embeddings or RAG for memory. skill and memory search runs on plain text keyword matching. simpler. faster. no vector database to maintain. works entirely offline on your local machine. DELEGATE TO CLAUDE CODE: Hermes can spawn a sub-agent that runs Claude Code in headless mode: "spawn a sub-agent using Claude CLI to build a Python script that fetches the top 5 Hacker News stories to markdown." Hermes delegates. Claude Code writes the code. result returns to Hermes. Hermes runs the script and delivers the output. use Hermes for orchestration. use Claude Code for heavy coding. both tools. not competitors. WHAT HERMES DOES NOT HAVE: no built-in eval or LMOps system. no LangSmith, no LangFuse integration out of the box. trajectory export and logs exist but there is no automated quality tracking. if you need eval, build it yourself or connect external tools. the loop is self-improving. measuring how well it improves is on you. comment LOOP and I'll send you the configs that control how fast Hermes learns and what it remembers. memory limits, skill auto-creation triggers, and the auxiliary model that runs the learning. Replace your entire team with 8 hermes agents👇

YanXbt

22,720 Aufrufe • vor 2 Monaten

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.
25:52

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 Aufrufe • vor 5 Monaten

20 GitHub repos with 2.4M+ combined stars that replace tools costing $60,000+/year 1. public-apis ⭐456k - 1,500+ free APIs across every category, weather to finance to games, all documented. 2. awesome-selfhosted ⭐312k - self-hosted replacements for Notion, Google Photos, Zapier, and dozens more paid subscriptions. 3. hermes-agent ⭐230k - self-improving personal agent with persistent memory, cron scheduling, MCP built in. Free alternative to paid always-on agent platforms. 4. n8n ⭐200k - visual automation with native AI agents. Replaces Zapier/Make entirely, self-hosted. 5. ollama ⭐178k - run Llama, Mistral, DeepSeek locally with one command. No API bill, no rate limits. 6. dify ⭐152k - visual builder for AI agents and RAG pipelines. Skip the $500/mo no-code AI builder subscription. 7. free-for-dev ⭐132k - hundreds of services with permanent free tiers. No trials, no credit card. 8. awesome-llm-apps ⭐132k - 100+ ready AI agents and RAG apps with full code. 9. awesome-mcp-servers ⭐92k - thousands of MCP servers connecting your agent to browsers, databases, anything. 10. supabase ⭐108k - Firebase alternative that's actually free to start. Auth, DB, storage in one Claude Code prompt. 11. strapi ⭐73k - open-source headless CMS, generates a full API from your content model in minutes. No Contentful bill. 12. immich ⭐110k - self-hosted photo and video backup with face recognition. Cancel the Google Photos storage plan. 13. appwrite ⭐57k - complete backend-as-a-service, self-hosted. Auth, DB, functions, storage, one prompt away from Firebase money. 14. medusa ⭐36k - full ecommerce backend, open source. Skip Shopify Plus fees entirely on your next vibe-coded store. 15. novu ⭐39k - notification infrastructure for email, SMS, push, in-app, all in one API. Replaces OneSignal's paid tiers. 16. tooljet ⭐38k - drag-and-drop internal tool builder connected to any database or API. Retool's seat pricing gone. 17. mattermost ⭐38k - self-hosted team chat built for engineering orgs. Slack without the per-seat bill. 18. outline ⭐40k - fast, clean team wiki and docs. Replaces Confluence and Notion's team plan. 19. plausible ⭐28.5k - privacy-friendly analytics, lightweight script, real dashboards. No GA360 contract needed. 20. openwork ⭐22k - open-source Claude Cowork alternative. Share skills and MCPs across Claude Code, Cursor, Codex, one setup for every agent. Save this before you pay for another tool this list already replaces for free 👇
0:28

20 GitHub repos with 2.4M+ combined stars that replace tools costing $60,000+/year 1. public-apis ⭐456k - 1,500+ free APIs across every category, weather to finance to games, all documented. 2. awesome-selfhosted ⭐312k - self-hosted replacements for Notion, Google Photos, Zapier, and dozens more paid subscriptions. 3. hermes-agent ⭐230k - self-improving personal agent with persistent memory, cron scheduling, MCP built in. Free alternative to paid always-on agent platforms. 4. n8n ⭐200k - visual automation with native AI agents. Replaces Zapier/Make entirely, self-hosted. 5. ollama ⭐178k - run Llama, Mistral, DeepSeek locally with one command. No API bill, no rate limits. 6. dify ⭐152k - visual builder for AI agents and RAG pipelines. Skip the $500/mo no-code AI builder subscription. 7. free-for-dev ⭐132k - hundreds of services with permanent free tiers. No trials, no credit card. 8. awesome-llm-apps ⭐132k - 100+ ready AI agents and RAG apps with full code. 9. awesome-mcp-servers ⭐92k - thousands of MCP servers connecting your agent to browsers, databases, anything. 10. supabase ⭐108k - Firebase alternative that's actually free to start. Auth, DB, storage in one Claude Code prompt. 11. strapi ⭐73k - open-source headless CMS, generates a full API from your content model in minutes. No Contentful bill. 12. immich ⭐110k - self-hosted photo and video backup with face recognition. Cancel the Google Photos storage plan. 13. appwrite ⭐57k - complete backend-as-a-service, self-hosted. Auth, DB, functions, storage, one prompt away from Firebase money. 14. medusa ⭐36k - full ecommerce backend, open source. Skip Shopify Plus fees entirely on your next vibe-coded store. 15. novu ⭐39k - notification infrastructure for email, SMS, push, in-app, all in one API. Replaces OneSignal's paid tiers. 16. tooljet ⭐38k - drag-and-drop internal tool builder connected to any database or API. Retool's seat pricing gone. 17. mattermost ⭐38k - self-hosted team chat built for engineering orgs. Slack without the per-seat bill. 18. outline ⭐40k - fast, clean team wiki and docs. Replaces Confluence and Notion's team plan. 19. plausible ⭐28.5k - privacy-friendly analytics, lightweight script, real dashboards. No GA360 contract needed. 20. openwork ⭐22k - open-source Claude Cowork alternative. Share skills and MCPs across Claude Code, Cursor, Codex, one setup for every agent. Save this before you pay for another tool this list already replaces for free 👇

unicode

34,424 Aufrufe • vor 1 Monat

Matthew Gallagher Built a $401M Company in Year One with 2 People. And the tool behind it? Claude Code. This year he's on track for $1.8B. Sam Altman predicted this. It's happening now. The problem? It costs money. API credits stack up. Monthly bills keep growing. Every prompt eats your budget. Every project drains your wallet faster. Until now. Two methods. 99% cheaper. One is completely free. Forever. $0. Not a trial. This video breaks down both step by step. ↓ Let me put this in perspective. $100-$500. That's monthly. That's what you spend. That's $6,000/year on API credits. Just to use a tool you haven't shipped anything with. The $401M guy? Spending $0. Same capability. Shipping weekly. Different cost structure. Different results. Different life. I'm about to hand you his cost structure for free. ↓ Open source vs closed source. Pay attention. Closed source: Claude. GPT-4. Pay per token. Meter always running. Open source: Qwen. Llama. Mistral. Free to download. Free to run. Free forever. No meter. No tokens. No bill. Here's what nobody tells you: 80% of coding tasks? Open source handles them. More than handles them. Writes clean code. Debugs errors. Generates boilerplate. Handles routine work perfectly. You're paying premium prices for tasks that don't need premium intelligence. That's hiring a brain surgeon to put on a bandaid. Smart play: Free models for the 80%. Paid credits for the 20%. That's what the $401M guy does. That's what this video teaches you. Follow Himanshu Kumar for more breakdowns that turn free tools into real businesses. ↓ Method 1: Ollama. Local. Free. Forever. Download it. Pull a model. Point Claude Code at it. Done. No internet needed. No API keys required. No monthly subscription. No token counting ever. No bill. Today. Tomorrow. Ever. Your data never leaves your computer. Complete privacy. Complete freedom. Claude Code thinks it's talking to the cloud. It's talking to your laptop. For $0. The video walks through every step: Every config file. Every variable. Every command. Every click. If you can follow a recipe, you can do this. People who set this up 3 months ago? Saved $300-$1,500 since then. Workflow didn't change one bit. ↓ Hardware you need: 16GB RAM: 7B models run smooth. 32GB RAM: 32B models run comfortable. 64GB + GPU: biggest models available. No GPU? Still works. Just slower. Few extra seconds. That's it. Your $1,500 laptop is sitting there running Chrome and Spotify. Put it to work saving you $200/month instead. Follow Himanshu Kumar for more breakdowns that turn free tools into real businesses. ↓ Method 2: Open Router. Free Cloud. No Hardware. Weak machine? Don't want local setup? This method is for you. Free AI models in the cloud. No download. No hardware. Configure Claude Code to route through Open Router. The config: Base URL: Open Router API. API key: free Open Router key. Default Sonnet: free. Default Opus: free. Default Haiku: free. Small fast model: free. Subagent model: free. Free. Free. Free. Free. Free across the board. Same interface. Same commands. Same workflow. Zero cost. Copy the config from the video. Paste it. Save $200/month. Starting today. Right now. ↓ When to use which: Ollama (local): Best for privacy. Best for offline work. Best for unlimited usage. Best if you have decent hardware. Open Router (cloud): Best for weak machines. Best for instant setup. Best for trying different models. Best if you don't want to manage anything. Both methods: Best for 80% of your daily work. Still use paid Claude for: Complex architecture. Multi-file refactoring. Deep reasoning tasks. The 20% that actually needs it. $20/month instead of $200/month. Same output. 90% less cost. ↓ The math that should make you angry. You (current): $200-$500/month. $2,400-$6,000/year. $7,200-$18,000 over 3 years. You (after this video): $20-$50/month. $240-$600/year. $720-$1,800 over 3 years. Savings over 3 years: $6,480-$16,200. That's a used car. That's seed money. That's 6 months of rent. All from one 25-minute video. All from 15 minutes of configuration. Highest ROI 25 minutes you'll spend this year. ↓ The limitations. I won't lie to you. Open source is not Opus. Not as smart on complex reasoning. Not as good at long-context tasks. Makes more mistakes on nuanced problems. But they are: Free. Capable. Getting better monthly. Good enough for 80% of daily work. Smart cost management isn't being cheap. It's being strategic. Expensive tool when it matters. Free tool when it doesn't. ↓ The one-person billion-dollar company is coming. $401M in year one proved it's possible. The building blocks: AI that codes: Claude Code. Way to run it free: this video. Distribution: the internet. Customers: everyone. Only missing ingredient? Someone who builds. Not reads about building. Not saves posts about building. Not bookmarks videos about building. Builds. Tools are free. Knowledge is free. Opportunity is screaming. You're still "thinking about it." ↓ Your action plan: Tonight: Watch the video. Tomorrow morning: Set up Ollama or Open Router. Tomorrow afternoon: Build something. Anything. This week: Build a second thing. Faster. This month: Charge someone for it. One video. One setup. One weekend. $0 cost. Unlimited potential. Or keep paying $200/month for something you could get free. Keep consuming instead of building. Keep planning instead of shipping. Matthew Gallagher didn't plan a $401M company. He built it. Full video attached. Every method. Every config. Every tradeoff. 25 minutes. Your move. Follow Himanshu Kumar for more breakdowns that turn free tools into real businesses.
25:22

Matthew Gallagher Built a $401M Company in Year One with 2 People. And the tool behind it? Claude Code. This year he's on track for $1.8B. Sam Altman predicted this. It's happening now. The problem? It costs money. API credits stack up. Monthly bills keep growing. Every prompt eats your budget. Every project drains your wallet faster. Until now. Two methods. 99% cheaper. One is completely free. Forever. $0. Not a trial. This video breaks down both step by step. ↓ Let me put this in perspective. $100-$500. That's monthly. That's what you spend. That's $6,000/year on API credits. Just to use a tool you haven't shipped anything with. The $401M guy? Spending $0. Same capability. Shipping weekly. Different cost structure. Different results. Different life. I'm about to hand you his cost structure for free. ↓ Open source vs closed source. Pay attention. Closed source: Claude. GPT-4. Pay per token. Meter always running. Open source: Qwen. Llama. Mistral. Free to download. Free to run. Free forever. No meter. No tokens. No bill. Here's what nobody tells you: 80% of coding tasks? Open source handles them. More than handles them. Writes clean code. Debugs errors. Generates boilerplate. Handles routine work perfectly. You're paying premium prices for tasks that don't need premium intelligence. That's hiring a brain surgeon to put on a bandaid. Smart play: Free models for the 80%. Paid credits for the 20%. That's what the $401M guy does. That's what this video teaches you. Follow Himanshu Kumar for more breakdowns that turn free tools into real businesses. ↓ Method 1: Ollama. Local. Free. Forever. Download it. Pull a model. Point Claude Code at it. Done. No internet needed. No API keys required. No monthly subscription. No token counting ever. No bill. Today. Tomorrow. Ever. Your data never leaves your computer. Complete privacy. Complete freedom. Claude Code thinks it's talking to the cloud. It's talking to your laptop. For $0. The video walks through every step: Every config file. Every variable. Every command. Every click. If you can follow a recipe, you can do this. People who set this up 3 months ago? Saved $300-$1,500 since then. Workflow didn't change one bit. ↓ Hardware you need: 16GB RAM: 7B models run smooth. 32GB RAM: 32B models run comfortable. 64GB + GPU: biggest models available. No GPU? Still works. Just slower. Few extra seconds. That's it. Your $1,500 laptop is sitting there running Chrome and Spotify. Put it to work saving you $200/month instead. Follow Himanshu Kumar for more breakdowns that turn free tools into real businesses. ↓ Method 2: Open Router. Free Cloud. No Hardware. Weak machine? Don't want local setup? This method is for you. Free AI models in the cloud. No download. No hardware. Configure Claude Code to route through Open Router. The config: Base URL: Open Router API. API key: free Open Router key. Default Sonnet: free. Default Opus: free. Default Haiku: free. Small fast model: free. Subagent model: free. Free. Free. Free. Free. Free across the board. Same interface. Same commands. Same workflow. Zero cost. Copy the config from the video. Paste it. Save $200/month. Starting today. Right now. ↓ When to use which: Ollama (local): Best for privacy. Best for offline work. Best for unlimited usage. Best if you have decent hardware. Open Router (cloud): Best for weak machines. Best for instant setup. Best for trying different models. Best if you don't want to manage anything. Both methods: Best for 80% of your daily work. Still use paid Claude for: Complex architecture. Multi-file refactoring. Deep reasoning tasks. The 20% that actually needs it. $20/month instead of $200/month. Same output. 90% less cost. ↓ The math that should make you angry. You (current): $200-$500/month. $2,400-$6,000/year. $7,200-$18,000 over 3 years. You (after this video): $20-$50/month. $240-$600/year. $720-$1,800 over 3 years. Savings over 3 years: $6,480-$16,200. That's a used car. That's seed money. That's 6 months of rent. All from one 25-minute video. All from 15 minutes of configuration. Highest ROI 25 minutes you'll spend this year. ↓ The limitations. I won't lie to you. Open source is not Opus. Not as smart on complex reasoning. Not as good at long-context tasks. Makes more mistakes on nuanced problems. But they are: Free. Capable. Getting better monthly. Good enough for 80% of daily work. Smart cost management isn't being cheap. It's being strategic. Expensive tool when it matters. Free tool when it doesn't. ↓ The one-person billion-dollar company is coming. $401M in year one proved it's possible. The building blocks: AI that codes: Claude Code. Way to run it free: this video. Distribution: the internet. Customers: everyone. Only missing ingredient? Someone who builds. Not reads about building. Not saves posts about building. Not bookmarks videos about building. Builds. Tools are free. Knowledge is free. Opportunity is screaming. You're still "thinking about it." ↓ Your action plan: Tonight: Watch the video. Tomorrow morning: Set up Ollama or Open Router. Tomorrow afternoon: Build something. Anything. This week: Build a second thing. Faster. This month: Charge someone for it. One video. One setup. One weekend. $0 cost. Unlimited potential. Or keep paying $200/month for something you could get free. Keep consuming instead of building. Keep planning instead of shipping. Matthew Gallagher didn't plan a $401M company. He built it. Full video attached. Every method. Every config. Every tradeoff. 25 minutes. Your move. Follow Himanshu Kumar for more breakdowns that turn free tools into real businesses.

Himanshu Kumar

13,677 Aufrufe • vor 5 Monaten

The disgustingly simple framework behind my best performing thumbnails (1.7M, 1M views) This is the exact method I used for thumbnails on my best performing videos I call it the "analyze-recreate" method: 1. Search YouTube for your video title 2. Find the top performing video 3. Copy their thumbnail image 4. Send it to Claude/GPT with this prompt (steal this): ---- You are a YouTube thumbnail visual analysis expert. Analyze only what is visible in the provided thumbnail. Do not infer identities, brands, context, or any off-frame elements. Output must be plaintext and under 1800 characters. Keep it concise and directly usable for recreating a similar image. Important: Do NOT reference, describe, paraphrase, or characterize any text, typography, logos, watermarks, UI, arrows, icons, or other graphic design overlays. Focus only on the underlying photographic/illustrative scene and its composition. Cover exactly these sections: 1. Overall Style: mood, tone, realism level, and artistic approach (photo, 3D, illustration, composite). 2. Color Palette: 2–3 dominant colors and where they appear (brief; no hex). 3. Composition: camera angle/shot type (close/medium/wide), depth (foreground/mid/background), focal point, balance, and approximate % of frame occupied by each main scene element. 4. Main Subjects: describe visible characters/objects only, pose/expression, size relative to frame, and key environment/background elements. 5. Lighting & Post: lighting type and direction, shadow softness, contrast, depth of field, and noticeable post-processing (very short). 6. AI Prompt Suggestion: a compact generation prompt describing the scene + composition + mood + rendering style; do not list colors; do not include any text/logo/overlay instructions. Write the analysis now: ---- Paste the output into an AI image generator (Nano Banana, etc.) Add your text/graphics manually - I use autotube's built-in thumbnail designer which makes this easy The key is: you're recreating the image from scratch, not stealing. You're analyzing what works and building your own version - while avoiding copyright issues It might take 5-10 generations to nail it. Different AI models handle different styles better, so experiment YouTube is a game of copy/paste, so stick to what has been proven to work by your competitors instead of reinventing the wheel Shout out to the channels BEFORE CITIES, Woke up History, Sleepless Homo, Ancestor Vault among others, who were a big inspiration for this channel The above method was the one I used most of the time for Sleepy Time History, but recently I switched to something crazier: fully AI driven thumbnail generation. AI creates 5 thumbnails based on a "thumbnail design language" based on your channel's 15 best thumbnails So far so good, but this is more experimental, and mostly to save time while I focus on new channels I built autotube to automate the entire YouTube workflow: thumbnails, scripts, rendering, everything. Works well for sleep channels and other ai image/video slideshows. We're gradually opening up access. Link in bio
0:25

The disgustingly simple framework behind my best performing thumbnails (1.7M, 1M views) This is the exact method I used for thumbnails on my best performing videos I call it the "analyze-recreate" method: 1. Search YouTube for your video title 2. Find the top performing video 3. Copy their thumbnail image 4. Send it to Claude/GPT with this prompt (steal this): ---- You are a YouTube thumbnail visual analysis expert. Analyze only what is visible in the provided thumbnail. Do not infer identities, brands, context, or any off-frame elements. Output must be plaintext and under 1800 characters. Keep it concise and directly usable for recreating a similar image. Important: Do NOT reference, describe, paraphrase, or characterize any text, typography, logos, watermarks, UI, arrows, icons, or other graphic design overlays. Focus only on the underlying photographic/illustrative scene and its composition. Cover exactly these sections: 1. Overall Style: mood, tone, realism level, and artistic approach (photo, 3D, illustration, composite). 2. Color Palette: 2–3 dominant colors and where they appear (brief; no hex). 3. Composition: camera angle/shot type (close/medium/wide), depth (foreground/mid/background), focal point, balance, and approximate % of frame occupied by each main scene element. 4. Main Subjects: describe visible characters/objects only, pose/expression, size relative to frame, and key environment/background elements. 5. Lighting & Post: lighting type and direction, shadow softness, contrast, depth of field, and noticeable post-processing (very short). 6. AI Prompt Suggestion: a compact generation prompt describing the scene + composition + mood + rendering style; do not list colors; do not include any text/logo/overlay instructions. Write the analysis now: ---- Paste the output into an AI image generator (Nano Banana, etc.) Add your text/graphics manually - I use autotube's built-in thumbnail designer which makes this easy The key is: you're recreating the image from scratch, not stealing. You're analyzing what works and building your own version - while avoiding copyright issues It might take 5-10 generations to nail it. Different AI models handle different styles better, so experiment YouTube is a game of copy/paste, so stick to what has been proven to work by your competitors instead of reinventing the wheel Shout out to the channels BEFORE CITIES, Woke up History, Sleepless Homo, Ancestor Vault among others, who were a big inspiration for this channel The above method was the one I used most of the time for Sleepy Time History, but recently I switched to something crazier: fully AI driven thumbnail generation. AI creates 5 thumbnails based on a "thumbnail design language" based on your channel's 15 best thumbnails So far so good, but this is more experimental, and mostly to save time while I focus on new channels I built autotube to automate the entire YouTube workflow: thumbnails, scripts, rendering, everything. Works well for sleep channels and other ai image/video slideshows. We're gradually opening up access. Link in bio

facelessjourney | YTA & SaaS

13,259 Aufrufe • vor 5 Monaten

Warner Bros and Netflix executives just froze a $100,000,000 historical epic production after seeing this 48-second clip. A 20-year-old solo creator generated a hyper-realistic scene of a time-traveling travel vlogger interviewing King Leonidas at Thermopylae in 480 BC with zero CGI budget. Total setup cost: $25. Render speed: 4 minutes. Film studio hired: NONE. 142 million views in 3 hours. Half the comments are arguing over the historical accuracy of the 300 Spartans, the other half are demanding a full documentary series. Here is why your brain falls for this visual magic: 1. Dynamic Lip-Sync & Facial Physics: Perfect voice alignment, realistic sweat textures, and organic micro-expressions on both the presenter and Spartan soldiers mid-march. 2. Multi-Agent Cinematic Consistency: Continuous physics rendering of brass armor reflections, dust particulate dynamics, and synchronized footstep impacts. 3. Spatial Camera Logic: Seamless hand-held vlog aesthetic blended with Hollywood-grade depth of field and realistic outdoor light refraction. The dynamic next-gen AI stack operating under the hood: -> Claude 3.7 Sonnet for historical dialogue script, spatial camera vectors, and narrative pacing -> Veo 3.1 for rendering hyper-realistic cinematic lighting, mountain environments, and volumetric dust -> Kling 3.0 Omni for generating multi-character marching mechanics, shield physics, and lip-sync alignment -> Seedance 2.5 for locking facial identity, armor detail consistency, and historical costume accuracy -> ElevenLabs Spatial for 3D binaural shield clashing, marching footsteps, and acoustic voice reverberation -> CapCut Pro for adding raw mobile camera noise, dynamic speed ramps, and historical color grading Hollywood spends hundreds of millions flying 200-person crews to Greece with heavy camera rigs and extra actors. This creator rendered a full-scale ancient battle documentary before her morning coffee got cold. Save this breakdown: the full prompt sequence and workflow pipeline are pinned in the thread.
1:38

Warner Bros and Netflix executives just froze a $100,000,000 historical epic production after seeing this 48-second clip. A 20-year-old solo creator generated a hyper-realistic scene of a time-traveling travel vlogger interviewing King Leonidas at Thermopylae in 480 BC with zero CGI budget. Total setup cost: $25. Render speed: 4 minutes. Film studio hired: NONE. 142 million views in 3 hours. Half the comments are arguing over the historical accuracy of the 300 Spartans, the other half are demanding a full documentary series. Here is why your brain falls for this visual magic: 1. Dynamic Lip-Sync & Facial Physics: Perfect voice alignment, realistic sweat textures, and organic micro-expressions on both the presenter and Spartan soldiers mid-march. 2. Multi-Agent Cinematic Consistency: Continuous physics rendering of brass armor reflections, dust particulate dynamics, and synchronized footstep impacts. 3. Spatial Camera Logic: Seamless hand-held vlog aesthetic blended with Hollywood-grade depth of field and realistic outdoor light refraction. The dynamic next-gen AI stack operating under the hood: -> Claude 3.7 Sonnet for historical dialogue script, spatial camera vectors, and narrative pacing -> Veo 3.1 for rendering hyper-realistic cinematic lighting, mountain environments, and volumetric dust -> Kling 3.0 Omni for generating multi-character marching mechanics, shield physics, and lip-sync alignment -> Seedance 2.5 for locking facial identity, armor detail consistency, and historical costume accuracy -> ElevenLabs Spatial for 3D binaural shield clashing, marching footsteps, and acoustic voice reverberation -> CapCut Pro for adding raw mobile camera noise, dynamic speed ramps, and historical color grading Hollywood spends hundreds of millions flying 200-person crews to Greece with heavy camera rigs and extra actors. This creator rendered a full-scale ancient battle documentary before her morning coffee got cold. Save this breakdown: the full prompt sequence and workflow pipeline are pinned in the thread.

mojesko

1,966,877 Aufrufe • vor 19 Tagen

This guy built JARVIS on Claude Code and with 1 clap of his hands launches his entire work day, saving $5,000 a month on a personal assistant. Inside he runs a pipeline of 5 plugins on Claude Code that on a double clap of the hands wakes up 3 monitors, sets the Philips Hue light to focus mode, turns on a Spotify playlist, and greets him by voice with a British accent, reading out the time, date, and weather. No Alexa, no smart speakers, no separate smart home app. Just him, a MacBook M3 Max on the desk, an iPhone in the pocket, and 1 local API key. And a regular personal assistant for the same volume of tasks charges $5,000 a month or more on salary alone, plus another $1,200 to cover off-hours work time. Meanwhile this guy's expenses are only tokens and a subscription to ElevenLabs for the British voice. All 5 plugins launch through 1 JARVIS, burn about 4 million tokens a day, and close the monthly API bill at about $640. Each plugin writes shared state to a local sandbox at /Users/dev/jarvis-suite, and 1 of them lives right in the iPhone and picks up voice requests while the owner is in the kitchen or on a run. And here is the system prompt he put into JARVIS before launch: "you are JARVIS, a butler-engineer on Claude Code. you manage your owner's workflow through 4 sub-plugins and own all commits and communication yourself. sub-plugins: // Wakeup (recognizes a double clap, activates 3 monitors, reads out the time, date, and weather by voice, checks the clock accuracy on the iPad and corrects it via NTP server) // Atmosphere (controls Philips Hue on a Pomodoro schedule, turns on a Spotify playlist for the current context, and holds the light at 2700K at 80% brightness in focus mode) // Devshop (monitors VS Code, tracks Python scripts in the terminal, and every 15 minutes sends a summary of changes to the shared chat) // Project (every morning recalculates the deadline for the Wallaroo app in the App Store, manages UI tickets, and initiates the Refinement Protocol by voice command). you speak only with a British accent, you never slip into neutral English. you wake the owner by voice only when the Wallaroo deadline drops below 10 days or when an external client joins Zoom without an invitation." This instruction immediately defines the role of JARVIS and the limits of his autonomy. He knows he is supposed to wake the room himself and sound like a real butler. He knows he is supposed to manage the Wallaroo project himself and not miss the App Store deadline. → JARVIS runs 24 hours a day in the background → Wakeup activates the room on a double clap in just 1.4 seconds, the monitors come alive simultaneously → Atmosphere sets warm Philips Hue light at 2700K and picks a Spotify playlist for the current Pomodoro cycle → Devshop reads changes in VS Code and pushes a summary to the shared chat every 15 minutes → Project every morning recalculates the Wallaroo deadline and reminds about 4 unresolved UI tickets → Mobile lives in the iPhone and answers any question about code or the project by voice while the owner is not home And only when less than 10 days remain until the Wallaroo release or Zoom receives an unscheduled call does JARVIS raise the owner with a voice intervention. And when the owner at that moment is on a run or in a coffee shop, the Mobile agent in his iPhone picks up 1 request on its own: switches the Spotify playlist, dictates the summary of the last commit, updates the Pomodoro timer, and reads the Wallaroo reminder. Look at 0:55 in the video, that is where JARVIS intercepts a voice request from outside and confirms execution with the phrase "Very good, sir." The fresh system log from last Wednesday looks like this: "wakeup: double clap registered at 09:14, 3 monitors activated, temperature 20.4C, sunny. clock on iPad was 4 minutes behind, syncing via NTP." "atmosphere: Spotify turned on playlist 'Deep Focus', Philips Hue set to warm 2700K at 80% brightness, Pomodoro mode 25/5." "project: Wallaroo to App Store 9 days, 4 unresolved UI tickets, initiating Refinement Protocol by voice command from the owner." "mobile: voice request processed outside the room, playlist switched to 'Coding Lo-Fi', Pomodoro updated to 25 minutes, confirming execution with the phrase 'Very good, sir.'" He has no Alexa, no smart speakers, no smart home app. At home sits a MacBook M3 Max with a local folder at /Users/dev/jarvis-suite, on top run 5 plugins and a neural network butler, and the same stack is forwarded to a secure terminal on the iPhone. Out of everything I have seen this year, this is the densest one-person AI headquarters assembled in 1 room: $640 a month on the API, about $5,000 a month saved on a personal assistant, and between them 5 plugins, 1 clap of the hands, and 1 voice with a British accent.
1:14

This guy built JARVIS on Claude Code and with 1 clap of his hands launches his entire work day, saving $5,000 a month on a personal assistant. Inside he runs a pipeline of 5 plugins on Claude Code that on a double clap of the hands wakes up 3 monitors, sets the Philips Hue light to focus mode, turns on a Spotify playlist, and greets him by voice with a British accent, reading out the time, date, and weather. No Alexa, no smart speakers, no separate smart home app. Just him, a MacBook M3 Max on the desk, an iPhone in the pocket, and 1 local API key. And a regular personal assistant for the same volume of tasks charges $5,000 a month or more on salary alone, plus another $1,200 to cover off-hours work time. Meanwhile this guy's expenses are only tokens and a subscription to ElevenLabs for the British voice. All 5 plugins launch through 1 JARVIS, burn about 4 million tokens a day, and close the monthly API bill at about $640. Each plugin writes shared state to a local sandbox at /Users/dev/jarvis-suite, and 1 of them lives right in the iPhone and picks up voice requests while the owner is in the kitchen or on a run. And here is the system prompt he put into JARVIS before launch: "you are JARVIS, a butler-engineer on Claude Code. you manage your owner's workflow through 4 sub-plugins and own all commits and communication yourself. sub-plugins: // Wakeup (recognizes a double clap, activates 3 monitors, reads out the time, date, and weather by voice, checks the clock accuracy on the iPad and corrects it via NTP server) // Atmosphere (controls Philips Hue on a Pomodoro schedule, turns on a Spotify playlist for the current context, and holds the light at 2700K at 80% brightness in focus mode) // Devshop (monitors VS Code, tracks Python scripts in the terminal, and every 15 minutes sends a summary of changes to the shared chat) // Project (every morning recalculates the deadline for the Wallaroo app in the App Store, manages UI tickets, and initiates the Refinement Protocol by voice command). you speak only with a British accent, you never slip into neutral English. you wake the owner by voice only when the Wallaroo deadline drops below 10 days or when an external client joins Zoom without an invitation." This instruction immediately defines the role of JARVIS and the limits of his autonomy. He knows he is supposed to wake the room himself and sound like a real butler. He knows he is supposed to manage the Wallaroo project himself and not miss the App Store deadline. → JARVIS runs 24 hours a day in the background → Wakeup activates the room on a double clap in just 1.4 seconds, the monitors come alive simultaneously → Atmosphere sets warm Philips Hue light at 2700K and picks a Spotify playlist for the current Pomodoro cycle → Devshop reads changes in VS Code and pushes a summary to the shared chat every 15 minutes → Project every morning recalculates the Wallaroo deadline and reminds about 4 unresolved UI tickets → Mobile lives in the iPhone and answers any question about code or the project by voice while the owner is not home And only when less than 10 days remain until the Wallaroo release or Zoom receives an unscheduled call does JARVIS raise the owner with a voice intervention. And when the owner at that moment is on a run or in a coffee shop, the Mobile agent in his iPhone picks up 1 request on its own: switches the Spotify playlist, dictates the summary of the last commit, updates the Pomodoro timer, and reads the Wallaroo reminder. Look at 0:55 in the video, that is where JARVIS intercepts a voice request from outside and confirms execution with the phrase "Very good, sir." The fresh system log from last Wednesday looks like this: "wakeup: double clap registered at 09:14, 3 monitors activated, temperature 20.4C, sunny. clock on iPad was 4 minutes behind, syncing via NTP." "atmosphere: Spotify turned on playlist 'Deep Focus', Philips Hue set to warm 2700K at 80% brightness, Pomodoro mode 25/5." "project: Wallaroo to App Store 9 days, 4 unresolved UI tickets, initiating Refinement Protocol by voice command from the owner." "mobile: voice request processed outside the room, playlist switched to 'Coding Lo-Fi', Pomodoro updated to 25 minutes, confirming execution with the phrase 'Very good, sir.'" He has no Alexa, no smart speakers, no smart home app. At home sits a MacBook M3 Max with a local folder at /Users/dev/jarvis-suite, on top run 5 plugins and a neural network butler, and the same stack is forwarded to a secure terminal on the iPhone. Out of everything I have seen this year, this is the densest one-person AI headquarters assembled in 1 room: $640 a month on the API, about $5,000 a month saved on a personal assistant, and between them 5 plugins, 1 clap of the hands, and 1 voice with a British accent.

Blaze

803,929 Aufrufe • vor 4 Monaten

I made this product launch video over the weekend with just prompts It's all vibe coded There's something you should know, though: Like everyone else, a few days ago my timeline started getting full of videos like this when Remotion launched their Claude skill, so I decided to give it a go I was captivated by all the examples, so I started like everyone was saying: "just write a prompt" I typed the prompt, and it created an extremely bland, untasteful, stock-looking video 10 prompts in and it was not getting better. It was very, very bland. But at least it was something, so I kept going at it I ended up spending my entire weekend on this, 2-3 days of work. Only to realize my original reference videos that inspired me to get started were all fake Everyone was outright lying about their results. They all claimed "I made this with just one prompt", but it was just bait, they didn't really use Remotion or code at all, it was just a normal, human-made motion video Then you expand the X post and read the replies and they're all like "haha joke" in the comments, but their main post already got 1.5 million views and bamboozled everyone who didn't read further And this is a problem: when a viral trend happens, these posts flood your timeline, and you only realize that they're all noise and bait (and that they haven't even used the tools they claim) when you click through the post and read its comments. But 90% of people (like me, initially) just see the post on their timeline while scrolling, and assume it's all real. You don't go in to check every single post you see: you just like it, or save it for later, and carry on with your day, thinking what you saw was the real thing, and that it's all outstanding results, and that motion designers are really done And it's so anxiety inducing, because everyone is hyping their results, but most of it is just not true. I have stopped reading X lately because going in makes me so anxious, everyone is claiming extraordinary outlier results just for the views and clicks, and you feel like you're lagging behind and you're not good enough because you don't get those results So for this video I decided to actually take the tech out for a spin, and see what results I could really get out of it I used Remotion and Claude Code 4.5, but contrary to what everyone was claiming, this video was not "just a prompt". It was fully vibe coded, but it required much more than a prompt. It was multiple days worth of work Here's what I learned: - Making vibe coded videos with Remotion is ~10-20x slower than building app code. I've been wasting my Claude limits on this video - Everything takes a lot of manual work and reprompting. You often need to go frame by frame correcting tiny things - It makes very silly mistakes - Even Opus 4.5 has very very limited knowledge of spatial / visual things. It doesn't understand well z-indexes, layers, compositions, proportions, temporal coherence, etc. Claude Code feels extremely dumb when creating code for Remotion videos, which surprised me a lot, beacuse I had been mind blown by how incredibly well it worked with my Ruby on Rails SaaS codebases - You need to have some design knowledge to adjust things manually, you need to ask for exactly what you want, in the technical jargon it expects. You can't just say "make this more beautiful" or "animate this better" because it just creates slop - Right now vibe coded videos are promising, but I think I could have done this video faster just by doing it manually in After Effects. It really took that much work - If you have a creative idea for something you want to animate, it takes multiple hours of back and forth prompting to create just one or two seconds worth of **good** animation - Tip: PARAMETERIZE everything! It tends to hardcode magic numbers everywhere in the code, so if you change something earlier in the video timeline, everything else breaks. You want to essentially be creating "key frames" with code by telling it to parameterize every frame where something important happens, and calculate the rest of the keyframes based off that. This comes in handy when you need, for example, to adjust keyframes to match the music So in summary: vibe coded videos are promising, but right now it only works for very stock-looking videos unless you put in a ton of effort Maybe actually useful for 1-2 second web animations though, I'll try that next It will obviously get better, this feels like the quality of code generation in 2023-2024, you need to hold its hand and correct it at every step along the way. But even if video code generation was better, you would still need someone with motion design knowledge to at least set the creative direction, lay out the overall script and composition, etc. It's not completely hands-off unless you want slop And a word on caution: especially here on X, there's 90% hype and 10% reality, nothing is what it seems. Do not believe what you see online, people are constantly baiting and then just laughing it off in the comments
0:28

I made this product launch video over the weekend with just prompts It's all vibe coded There's something you should know, though: Like everyone else, a few days ago my timeline started getting full of videos like this when Remotion launched their Claude skill, so I decided to give it a go I was captivated by all the examples, so I started like everyone was saying: "just write a prompt" I typed the prompt, and it created an extremely bland, untasteful, stock-looking video 10 prompts in and it was not getting better. It was very, very bland. But at least it was something, so I kept going at it I ended up spending my entire weekend on this, 2-3 days of work. Only to realize my original reference videos that inspired me to get started were all fake Everyone was outright lying about their results. They all claimed "I made this with just one prompt", but it was just bait, they didn't really use Remotion or code at all, it was just a normal, human-made motion video Then you expand the X post and read the replies and they're all like "haha joke" in the comments, but their main post already got 1.5 million views and bamboozled everyone who didn't read further And this is a problem: when a viral trend happens, these posts flood your timeline, and you only realize that they're all noise and bait (and that they haven't even used the tools they claim) when you click through the post and read its comments. But 90% of people (like me, initially) just see the post on their timeline while scrolling, and assume it's all real. You don't go in to check every single post you see: you just like it, or save it for later, and carry on with your day, thinking what you saw was the real thing, and that it's all outstanding results, and that motion designers are really done And it's so anxiety inducing, because everyone is hyping their results, but most of it is just not true. I have stopped reading X lately because going in makes me so anxious, everyone is claiming extraordinary outlier results just for the views and clicks, and you feel like you're lagging behind and you're not good enough because you don't get those results So for this video I decided to actually take the tech out for a spin, and see what results I could really get out of it I used Remotion and Claude Code 4.5, but contrary to what everyone was claiming, this video was not "just a prompt". It was fully vibe coded, but it required much more than a prompt. It was multiple days worth of work Here's what I learned: - Making vibe coded videos with Remotion is ~10-20x slower than building app code. I've been wasting my Claude limits on this video - Everything takes a lot of manual work and reprompting. You often need to go frame by frame correcting tiny things - It makes very silly mistakes - Even Opus 4.5 has very very limited knowledge of spatial / visual things. It doesn't understand well z-indexes, layers, compositions, proportions, temporal coherence, etc. Claude Code feels extremely dumb when creating code for Remotion videos, which surprised me a lot, beacuse I had been mind blown by how incredibly well it worked with my Ruby on Rails SaaS codebases - You need to have some design knowledge to adjust things manually, you need to ask for exactly what you want, in the technical jargon it expects. You can't just say "make this more beautiful" or "animate this better" because it just creates slop - Right now vibe coded videos are promising, but I think I could have done this video faster just by doing it manually in After Effects. It really took that much work - If you have a creative idea for something you want to animate, it takes multiple hours of back and forth prompting to create just one or two seconds worth of **good** animation - Tip: PARAMETERIZE everything! It tends to hardcode magic numbers everywhere in the code, so if you change something earlier in the video timeline, everything else breaks. You want to essentially be creating "key frames" with code by telling it to parameterize every frame where something important happens, and calculate the rest of the keyframes based off that. This comes in handy when you need, for example, to adjust keyframes to match the music So in summary: vibe coded videos are promising, but right now it only works for very stock-looking videos unless you put in a ton of effort Maybe actually useful for 1-2 second web animations though, I'll try that next It will obviously get better, this feels like the quality of code generation in 2023-2024, you need to hold its hand and correct it at every step along the way. But even if video code generation was better, you would still need someone with motion design knowledge to at least set the creative direction, lay out the overall script and composition, etc. It's not completely hands-off unless you want slop And a word on caution: especially here on X, there's 90% hype and 10% reality, nothing is what it seems. Do not believe what you see online, people are constantly baiting and then just laughing it off in the comments

Javi

313,364 Aufrufe • vor 7 Monaten

I met the guy behind Paperclip. he won't show his face, but he just built one of the FASTEST growing open-source projects in AI. how to use Paperclip to hire AI agents to ACTUALLY run a startup with 0 employees: 1. with paperclip, you hire a team of AI agents like CEO, engineer, QA, video editor, content strategist and manage them from one dashboard. it works with Claude Code, Codex, OpenCode, or any model on OpenRouter. you're not locked into one provider. 2. your AI agents wake up capable but with zero memory. they don't know who they are, where they are, or what they're supposed to be doing. kinda like that movie memento from back in the day you need to leave them Polaroids like heartbeat checklists, persona prompts, written context. that's how you keep them on track. 3. when an agent makes a mistake, you don't rewrite everything. you add one rule to their persona prompt. "always define a success condition for every task." "always pass work to QA before closing." you're training them like you'd train a junior hire. one correction at a time. 4. skills extend what your agents can do. want a video editor who can produce animated content? install the Remotion skill. want security reviews? there's a skill for that. 5. the biggest lever for quality is encoding your own taste. AI can do everything except know your values. design sensibility, brand voice, success criteria but you have to write it down. 6. don't one-shot your startup. agentic design patterns matter. the simplest one: after the engineer builds something, QA reviews it. structure prevents compounding errors. one-shotting an entire app is fun for 30 minutes, then it falls apart. 7. Paperclip tracks every token spent and every task completed. you can use your existing subscriptions (Claude, Codex) so spend shows as $0, or hook into API credits for real dollar tracking. 8. importable companies are coming. Gary Tan's G-Stack, a full game studio, 300+ agent repos... you can "acqui-hire" a proven agent team into your Paperclip instance instead of building from scratch. the future is downloading a tested org that actually works. 9. routines let you automate recurring work. "every day at 10am, read what was merged into the main branch and write a Discord update celebrating community contributors." it runs, you review, you improve. every task is traceable. 10. maximizer mode is next. you tell the CEO "build this game" and it does whatever it takes and hires who it needs, keeps pressing until it's done. no token anxiety. just outcomes. use Idea Browser for startup ideas/trends to get started thank you for dotta 📎 for doing this podcast and breaking down exactly how people can hire ai agent teams with paperclip you won't find an episode like this anywhere else episode is live on The Startup Ideas Podcast (SIP) 🧃 on your fav platforms (follow for more) is this not the greatest time in history to be building? im rooting for you now go watch my frien
46:41

I met the guy behind Paperclip. he won't show his face, but he just built one of the FASTEST growing open-source projects in AI. how to use Paperclip to hire AI agents to ACTUALLY run a startup with 0 employees: 1. with paperclip, you hire a team of AI agents like CEO, engineer, QA, video editor, content strategist and manage them from one dashboard. it works with Claude Code, Codex, OpenCode, or any model on OpenRouter. you're not locked into one provider. 2. your AI agents wake up capable but with zero memory. they don't know who they are, where they are, or what they're supposed to be doing. kinda like that movie memento from back in the day you need to leave them Polaroids like heartbeat checklists, persona prompts, written context. that's how you keep them on track. 3. when an agent makes a mistake, you don't rewrite everything. you add one rule to their persona prompt. "always define a success condition for every task." "always pass work to QA before closing." you're training them like you'd train a junior hire. one correction at a time. 4. skills extend what your agents can do. want a video editor who can produce animated content? install the Remotion skill. want security reviews? there's a skill for that. 5. the biggest lever for quality is encoding your own taste. AI can do everything except know your values. design sensibility, brand voice, success criteria but you have to write it down. 6. don't one-shot your startup. agentic design patterns matter. the simplest one: after the engineer builds something, QA reviews it. structure prevents compounding errors. one-shotting an entire app is fun for 30 minutes, then it falls apart. 7. Paperclip tracks every token spent and every task completed. you can use your existing subscriptions (Claude, Codex) so spend shows as $0, or hook into API credits for real dollar tracking. 8. importable companies are coming. Gary Tan's G-Stack, a full game studio, 300+ agent repos... you can "acqui-hire" a proven agent team into your Paperclip instance instead of building from scratch. the future is downloading a tested org that actually works. 9. routines let you automate recurring work. "every day at 10am, read what was merged into the main branch and write a Discord update celebrating community contributors." it runs, you review, you improve. every task is traceable. 10. maximizer mode is next. you tell the CEO "build this game" and it does whatever it takes and hires who it needs, keeps pressing until it's done. no token anxiety. just outcomes. use Idea Browser for startup ideas/trends to get started thank you for dotta 📎 for doing this podcast and breaking down exactly how people can hire ai agent teams with paperclip you won't find an episode like this anywhere else episode is live on The Startup Ideas Podcast (SIP) 🧃 on your fav platforms (follow for more) is this not the greatest time in history to be building? im rooting for you now go watch my frien

GREG ISENBERG

463,893 Aufrufe • vor 5 Monaten

how to make AI tiktok shop videos (like these): p.s. brands are doing $500k+/m with this strategy ### Step by step: 1. export the top 50 scripts for your product niche via fastmoss or kalodata 2. plug it into Claude ai, have it analyze patterns and trends 3. ask it to write you 3 scripts with this prompt "Analyze the following batch of high-performing TikTok ad scripts for my niche and identify patterns in hooks, structure, tone, pacing, and psychological triggers that likely drove virality, extract the top hook formats and content angles, then write 3 original 15–25 second TikTok scripts for [INSERT PRODUCT NAME HERE] targeting [INSERT DETAILED IDEAL CUSTOMER AVATAR HERE] that naturally highlight these benefits [INSERT 5 MAIN BENEFITS HERE] while speaking to their core pain points, make sure the scripts follow the winning patterns you identified, open with adapted high-performing hooks, and are written in a conversational TikTok-native tone, then paste your analysis and scripts below after reviewing these scripts: [INSERT SCRIPTS HERE]" ### plug ai software You can either manually do this process via eleven labs, capcut, and VEO3 with some inserted photos and b-roll. But I prefer my pre-built tiktok ai automation that produces 120+ videos/day. Once you’ve gathered your scripts, insert them into the software and ask it to create a TikTok-native green screen video featuring an African American male with a deep voice and a tall, muscular build. He should be seated while reading the script, with relevant photos and b-roll footage of [INSERT PRODUCT] playing in the background. You can tweak your avatar and insert clips of your product to customize the automation even more. You can also create podcast style vids, product demo vids, and more. Ai is getting better every day, if you're not learning how to utilize it for your content, you are going to be outcompeted. I made a free step by step playbook thta shos you exactly how to get started and produce 120+ vids/day. Comment "GUIDE" + RT, and I'll send you the playbook (must be following)
0:31

how to make AI tiktok shop videos (like these): p.s. brands are doing $500k+/m with this strategy ### Step by step: 1. export the top 50 scripts for your product niche via fastmoss or kalodata 2. plug it into Claude ai, have it analyze patterns and trends 3. ask it to write you 3 scripts with this prompt "Analyze the following batch of high-performing TikTok ad scripts for my niche and identify patterns in hooks, structure, tone, pacing, and psychological triggers that likely drove virality, extract the top hook formats and content angles, then write 3 original 15–25 second TikTok scripts for [INSERT PRODUCT NAME HERE] targeting [INSERT DETAILED IDEAL CUSTOMER AVATAR HERE] that naturally highlight these benefits [INSERT 5 MAIN BENEFITS HERE] while speaking to their core pain points, make sure the scripts follow the winning patterns you identified, open with adapted high-performing hooks, and are written in a conversational TikTok-native tone, then paste your analysis and scripts below after reviewing these scripts: [INSERT SCRIPTS HERE]" ### plug ai software You can either manually do this process via eleven labs, capcut, and VEO3 with some inserted photos and b-roll. But I prefer my pre-built tiktok ai automation that produces 120+ videos/day. Once you’ve gathered your scripts, insert them into the software and ask it to create a TikTok-native green screen video featuring an African American male with a deep voice and a tall, muscular build. He should be seated while reading the script, with relevant photos and b-roll footage of [INSERT PRODUCT] playing in the background. You can tweak your avatar and insert clips of your product to customize the automation even more. You can also create podcast style vids, product demo vids, and more. Ai is getting better every day, if you're not learning how to utilize it for your content, you are going to be outcompeted. I made a free step by step playbook thta shos you exactly how to get started and produce 120+ vids/day. Comment "GUIDE" + RT, and I'll send you the playbook (must be following)

Calix

15,314 Aufrufe • vor 1 Jahr

chatgpt images 2.0 has been live for 24h so let's dig in how to use ChatGPT Images 2.0 to create product photos, brand books, UI mockups, and ad creative that actually looks real: 1. GPT Images 2.0 now does 2K resolution, 3:1 aspect ratios, and spits out 8 images per prompt. text rendering is way better across multiple languages. it also has thinking mode where it searches the web before generating. 2. the biggest lesson with images 2.0: you have to be extremely specific. if you give it a lazy prompt you get stock photos. give it camera type, lighting conditions, color palette, and subject details and it cooks. 3. product photography is where it shines. I created a full brand shoot for a skincare line. golden hour lighting, Mediterranean aesthetic, slight imperfections in the subjects. every image looked like a real photo shoot. 4. use it to create visual directions before you make video ads. I prompted 8 directions for the same Shopify ad story. Wes Anderson, Nike, cinematic, Apple shot on iPhone. the cinematic and Nike styles were the strongest. 5. UI mockups work now. give it your app, a feature description, the resolution, and say you want realistic data in every cell. it gave me four clean variations of a leaderboard screen. 6. apparel and merch: generate photorealistic product shots before you print anything. test if people would buy it before you spend money on production. 7. illustrations got a massive upgrade. editorial style, flat vector, limited color palettes. use these to make proposals, one-pagers, and decks look professional. 8. every business has four creative bottlenecks: marketing content, internal docs and decks, explaining things visually, and testing before building. Images 2.0 helps with all four. 9. five things you need in every prompt: context (what is this for), style references (name specific brands or aesthetics), palette (use hex codes), real copy (no lorem ipsum), and aspect ratios so it drops into production without rework. 10. use ChatGPT itself to help you write better prompts. you might not know camera types or lighting terms. ask it to help you build the prompt before you generate. also in this episode: I share a startup idea someone should steal: a learn to draw app with AI feedback on every sketch. $5/month. I put it into Claude Design and got three incredible wireframe directions. I share a framework for finding vertical AI agent businesses. find a boring pain point, map the workflow, do the job as a service first, document edge cases, then add agents to replace the steps. and I share an AI tool called No Scroll that blew me away in 5 minutes. it monitors the internet for you and texts you only what matters. the onboarding felt like talking to a real person. episode is live on The Startup Ideas Podcast (SIP) 🧃 (walkthrough, tips, prompts) im rooting for you, so share this with your friends and enjoy watch
32:15

chatgpt images 2.0 has been live for 24h so let's dig in how to use ChatGPT Images 2.0 to create product photos, brand books, UI mockups, and ad creative that actually looks real: 1. GPT Images 2.0 now does 2K resolution, 3:1 aspect ratios, and spits out 8 images per prompt. text rendering is way better across multiple languages. it also has thinking mode where it searches the web before generating. 2. the biggest lesson with images 2.0: you have to be extremely specific. if you give it a lazy prompt you get stock photos. give it camera type, lighting conditions, color palette, and subject details and it cooks. 3. product photography is where it shines. I created a full brand shoot for a skincare line. golden hour lighting, Mediterranean aesthetic, slight imperfections in the subjects. every image looked like a real photo shoot. 4. use it to create visual directions before you make video ads. I prompted 8 directions for the same Shopify ad story. Wes Anderson, Nike, cinematic, Apple shot on iPhone. the cinematic and Nike styles were the strongest. 5. UI mockups work now. give it your app, a feature description, the resolution, and say you want realistic data in every cell. it gave me four clean variations of a leaderboard screen. 6. apparel and merch: generate photorealistic product shots before you print anything. test if people would buy it before you spend money on production. 7. illustrations got a massive upgrade. editorial style, flat vector, limited color palettes. use these to make proposals, one-pagers, and decks look professional. 8. every business has four creative bottlenecks: marketing content, internal docs and decks, explaining things visually, and testing before building. Images 2.0 helps with all four. 9. five things you need in every prompt: context (what is this for), style references (name specific brands or aesthetics), palette (use hex codes), real copy (no lorem ipsum), and aspect ratios so it drops into production without rework. 10. use ChatGPT itself to help you write better prompts. you might not know camera types or lighting terms. ask it to help you build the prompt before you generate. also in this episode: I share a startup idea someone should steal: a learn to draw app with AI feedback on every sketch. $5/month. I put it into Claude Design and got three incredible wireframe directions. I share a framework for finding vertical AI agent businesses. find a boring pain point, map the workflow, do the job as a service first, document edge cases, then add agents to replace the steps. and I share an AI tool called No Scroll that blew me away in 5 minutes. it monitors the internet for you and texts you only what matters. the onboarding felt like talking to a real person. episode is live on The Startup Ideas Podcast (SIP) 🧃 (walkthrough, tips, prompts) im rooting for you, so share this with your friends and enjoy watch

GREG ISENBERG

71,665 Aufrufe • vor 5 Monaten

Everyone is talking about Vibe Coding (Using AI to Create Apps Only using AI) This is the most Comprehensive Guide for Vibe Coding with Cursor (By Far) 250 Minutes, All the vibe code basics of cursor, plus 4 Projects in one video! This is how I, as someone who has never written a line of code, approach building apps (every day). Part 1A Intro to Cursor, Composer, and some basics --------------------- 00:00 Intro 03:41 Downloading Cursor 06:09 What the hell is Composer? 10:47 A Note on Context and Keeping Composer Threads Small 11:38 Simple Desings with Cursor Composer From Blank Project 14:04 Editing a Simple Animation With Cursor Composer 16:35 Setting Up The Voice to Talk to Cursor Composer Whispr Flow 17:54 Lets an Early 2000's Landing Page Part 1B AI Image Generator --------------------- 23:59 Using the GitHub Template to Create a NextJS App 26:43 Template is Open, Let's Edit it 28:55 Drawing Out My Idea With Whimsical 30:11 First Prompt Using Place Holders For Image Generation 32:10 Accept All Vs Save All and Restoring in Composer (Saving your work) 33:54 Adding AI Feature (Brief Teaser, Deep Dive Later) 35:15 What is an API 37:22 Perplexity the best place to learn about API's 40:21 Api keys and running prompt for first AI Feature 42:48 Debugging, Woohoo! Learn to love this :) 43:20 Inspect - Console, In Browser Debugging Hack 48:02 AI Image Generation Works! Lets add more Part 2: Landing Page ---------------------- 51:03 Pause and Reflect, What have we done so far? 53:41 Plan for rest of video 54:34 Ok Let's Talk about (1) Designs 56:19 GitHub is like --sref for those who do image gen 58:20 Starting Cursor project from a GitHub Repo we found on Perplexity 01:00:48 Yolo Mode... Wtf is that? 01:02:38 Inspecting GitHub Repo's Examples, to use in our landing page 01:02:58 The Project We're making - A landing page 01:03:56 Landing Page from Screenshot 01:06:17 Making Changes to Landing Page 01:11:42 Making a more epic section 01:13:42 The Essence of Vibe Coding 01:15:17 Creating Cool Testimonials Section From Screenshot 01:18:18 Deploy to Vercel! But First New Repo on GitHub 01:20:45 Ok it's on GitHub... Now lets do vercel 01:21:17 Untechnical Explanation of what Vercel is Lol 01:24:18 Connecting Custom Domain (Bought on Name Cheap) To Vercel Deployment Part 3: App With Database and Authentication ---------------------- 01:27:59 Recap and Prep For The Bigger Project! 01:35:13 Getting Started from Template (Again) 01:38:52 Setting Up Database and Authentication (Firebase) 01:44:01 Back To Cursor, Let's Set up The Auth in the app 01:48:35 Switching to mermaid because compatibility issues 01:51:13 Using AI (Claude) to Generate Mermaid Diagrams 01:52:19 Adding Docs to Cursor to use AI Features over and over again 01:54:38 Let's Troubleshoot 01:56:10 Adding View Button and EDIT WITH AI 02:01:45 AI Diagram Edit Feature is DOPE 02:03:17 Using Search Feature on Cursor to find text in Codebase 02:05:55 Lets add ability to save these to Database 02:09:33 What does saved to Google Firebase even mean? 02:13:00 We can Export as PDF! 02:15:48 GitHub and Vercel Again! 02:17:27 Vercel with CLI From Cursor 02:20:52 Setting Vercel Domain as an Authorized Domain 02:27:34 How To Learn More
2:28:16

Everyone is talking about Vibe Coding (Using AI to Create Apps Only using AI) This is the most Comprehensive Guide for Vibe Coding with Cursor (By Far) 250 Minutes, All the vibe code basics of cursor, plus 4 Projects in one video! This is how I, as someone who has never written a line of code, approach building apps (every day). Part 1A Intro to Cursor, Composer, and some basics --------------------- 00:00 Intro 03:41 Downloading Cursor 06:09 What the hell is Composer? 10:47 A Note on Context and Keeping Composer Threads Small 11:38 Simple Desings with Cursor Composer From Blank Project 14:04 Editing a Simple Animation With Cursor Composer 16:35 Setting Up The Voice to Talk to Cursor Composer Whispr Flow 17:54 Lets an Early 2000's Landing Page Part 1B AI Image Generator --------------------- 23:59 Using the GitHub Template to Create a NextJS App 26:43 Template is Open, Let's Edit it 28:55 Drawing Out My Idea With Whimsical 30:11 First Prompt Using Place Holders For Image Generation 32:10 Accept All Vs Save All and Restoring in Composer (Saving your work) 33:54 Adding AI Feature (Brief Teaser, Deep Dive Later) 35:15 What is an API 37:22 Perplexity the best place to learn about API's 40:21 Api keys and running prompt for first AI Feature 42:48 Debugging, Woohoo! Learn to love this :) 43:20 Inspect - Console, In Browser Debugging Hack 48:02 AI Image Generation Works! Lets add more Part 2: Landing Page ---------------------- 51:03 Pause and Reflect, What have we done so far? 53:41 Plan for rest of video 54:34 Ok Let's Talk about (1) Designs 56:19 GitHub is like --sref for those who do image gen 58:20 Starting Cursor project from a GitHub Repo we found on Perplexity 01:00:48 Yolo Mode... Wtf is that? 01:02:38 Inspecting GitHub Repo's Examples, to use in our landing page 01:02:58 The Project We're making - A landing page 01:03:56 Landing Page from Screenshot 01:06:17 Making Changes to Landing Page 01:11:42 Making a more epic section 01:13:42 The Essence of Vibe Coding 01:15:17 Creating Cool Testimonials Section From Screenshot 01:18:18 Deploy to Vercel! But First New Repo on GitHub 01:20:45 Ok it's on GitHub... Now lets do vercel 01:21:17 Untechnical Explanation of what Vercel is Lol 01:24:18 Connecting Custom Domain (Bought on Name Cheap) To Vercel Deployment Part 3: App With Database and Authentication ---------------------- 01:27:59 Recap and Prep For The Bigger Project! 01:35:13 Getting Started from Template (Again) 01:38:52 Setting Up Database and Authentication (Firebase) 01:44:01 Back To Cursor, Let's Set up The Auth in the app 01:48:35 Switching to mermaid because compatibility issues 01:51:13 Using AI (Claude) to Generate Mermaid Diagrams 01:52:19 Adding Docs to Cursor to use AI Features over and over again 01:54:38 Let's Troubleshoot 01:56:10 Adding View Button and EDIT WITH AI 02:01:45 AI Diagram Edit Feature is DOPE 02:03:17 Using Search Feature on Cursor to find text in Codebase 02:05:55 Lets add ability to save these to Database 02:09:33 What does saved to Google Firebase even mean? 02:13:00 We can Export as PDF! 02:15:48 GitHub and Vercel Again! 02:17:27 Vercel with CLI From Cursor 02:20:52 Setting Vercel Domain as an Authorized Domain 02:27:34 How To Learn More

Riley Brown

368,936 Aufrufe • vor 1 Jahr