Video yükleniyor...

Video Yüklenemedi

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

Ana Sayfaya Dön

𝐎𝐮𝐭 𝐍𝐨𝐰! Introducing our brand new coaching tool! 𝐔𝐥𝐭𝐢𝐦𝐚𝐭𝐞 𝐒𝐞𝐬𝐬𝐢𝐨𝐧 𝐂𝐚𝐫𝐝𝐬 🔴⚪️ •100 Session Cards •10 Colour Coded Session Topics •Waterproof Session Holder •Watch Full Sessions By Scanning QR Code 👉🏻

UltimateplayerHQ

49,439 subscribers

264,929 görüntüleme • 3 yıl önce •via X (Twitter)

Eğitim Spor Bilim & Teknoloji

Anya Rossi• Live Now

Private livecam show

2 Yorum

Tony Taylor® profil fotoğrafı

Tony Taylor®3 yıl önce

Love these 🔥🔥🔥

Emre Denizli profil fotoğrafı

Emre Denizli3 yıl önce

@SophieIbberson Perfect idea 👏

Benzer Videolar

2025: team, timeline, budget, 8 ads/week 2026: one agent, full brand context, 100 ads/session. Nobody killed the old workflow. It just stopped fitting the speed of the market. The brief takes a day. The strategy takes a day. The production takes two. The revisions take another. By launch the signal you were chasing has moved. One agent loaded with your brand context doesn't chase signals. It catches them through right creative direction. Brief in. 100 engineered ads out. 10 minutes. On brand. Built to convert. Every format. Ready now. The market didn't slow down for the old workflow. The new one doesn't need it to. Join the waitlist

Vinay Jain

36,145 görüntüleme • 7 ay önce

I just vibe-coded a Meta ad research app in Claude Code 🤯 One keyword → winning ads analyzed, creative briefs written, trends mapped, and 10 ad variations generated for your brand. All inside Claude Code. Perfect for DTC brands and agencies still running competitor research by hand inside the Meta Ad Library. This app eliminates the entire loop: → Search and filter winning Facebook ads by niche, country, language, and performance tier → Watch video ads inline without ever leaving the app → Pull the top performers and generate a full creative brief tailored to your brand → Run a trend radar across 100+ ads to see which formats, CTAs, and landing pages are winning your niche → Pick any winning video and Gemini watches it, reverse-engineers the creative DNA, and writes 10 new variations for your product No scrolling the Ad Library for hours. No manual note-taking. No rewriting briefs from scratch. What you get: → Creative briefs built from real winning ads in your niche → Trend analysis: format distribution, top CTAs, landing page intel, and AI insights → 10 brand-specific ad variations from any winning video, with hooks, scripts, and Nano Banana prompts → A full app you host in Replit and customize for your team Built 100% in Claude Code with the gethookd.ai API + Gemini. I put together a free playbook with every prompt I used to build this from scratch, so you can build your own. Want it for free? > Like this post > Comment "META" And I'll send it over (must be following so I can DM)

Mike Futia

13,074 görüntüleme • 3 ay önce

THE GUY WHO WON ANTHROPIC'S HACKATHON JUST GAVE AWAY HIS ENTIRE CLAUDE CODE PLAYBOOK FOR FREE. 10 MONTHS OF WORK, ALL PUBLIC Affaan Mustafa won the Anthropic x Forum Ventures hackathon by building a full startup in 8 hours with Claude Code. Then he open-sourced the exact setup that did it. It's called Everything Claude Code, and it turns Claude from one assistant into an entire engineering team Repo: affaan-m/ecc This isn't a prompt pack. It's a system he refined over 10+ months of daily use shipping real products What's inside: A huge library of skills, dozens of specialized subagents, and ready-made commands, all working together. Each piece does one job. One subagent reviews security against OWASP standards. One optimizes memory so Claude stops forgetting earlier decisions around hour three. One learns from your past sessions and projects so the setup gets smarter the more you use it. Others handle planning, test-driven development, and language-specific code review Instead of one assistant writing code, you get an orchestrated team. A main session delegates to the right specialist when the task calls for it, the way a real dev team splits work The best part: it's not locked to one tool. It runs in Claude Code, Cursor, Codex and OpenCode, across Windows, Mac and Linux. Free, MIT licensed This is the difference between using Claude like a search box and running it like a team that ships. The guy spent 10 months figuring out what actually works so you don't have to Bookmark this

THE GUY WHO WON ANTHROPIC'S HACKATHON JUST GAVE AWAY HIS ENTIRE CLAUDE CODE PLAYBOOK FOR FREE. 10 MONTHS OF WORK, ALL PUBLIC Affaan Mustafa won the Anthropic x Forum Ventures hackathon by building a full startup in 8 hours with Claude Code. Then he open-sourced the exact setup that did it. It's called Everything Claude Code, and it turns Claude from one assistant into an entire engineering team Repo: affaan-m/ecc This isn't a prompt pack. It's a system he refined over 10+ months of daily use shipping real products What's inside: A huge library of skills, dozens of specialized subagents, and ready-made commands, all working together. Each piece does one job. One subagent reviews security against OWASP standards. One optimizes memory so Claude stops forgetting earlier decisions around hour three. One learns from your past sessions and projects so the setup gets smarter the more you use it. Others handle planning, test-driven development, and language-specific code review Instead of one assistant writing code, you get an orchestrated team. A main session delegates to the right specialist when the task calls for it, the way a real dev team splits work The best part: it's not locked to one tool. It runs in Claude Code, Cursor, Codex and OpenCode, across Windows, Mac and Linux. Free, MIT licensed This is the difference between using Claude like a search box and running it like a team that ships. The guy spent 10 months figuring out what actually works so you don't have to Bookmark this

Yarchi

819,166 görüntüleme • 4 ay önce

I just vibe-coded a Meta ad research app in Claude Code 🤯 One keyword search → winning ads analyzed, creative briefs generated, trends mapped, and 10 ad variations written for your brand. All inside Claude Code. Perfect for DTC brands and agencies who are still doing competitor ad research manually inside the Meta Ad Library. If you're clicking through ads one by one, watching videos, taking notes in a Google Doc, trying to reverse-engineer what's working, and then rewriting briefs from scratch every time... This app eliminates the entire loop: → Search and filter winning Facebook ads by niche, country, language, and performance tier → Watch video ads inline without leaving the app → Fetch top-performing ads and generate a full creative brief tailored to your brand → Run a trend radar across 100+ ads to see which formats, CTAs, and landing pages are dominating your niche → Pick any winning video ad and Gemini watches it, reverse-engineers the creative DNA, and generates 10 new ad variations for your product No scrolling the Ad Library for hours. No manual note-taking. No rewriting briefs from scratch. What you get: → Creative briefs generated from real winning ads in your niche → Trend analysis with format distribution, top CTAs, landing page intel, and AI insights → 10 brand-specific ad variations from any winning video — with hooks, scripts, and Nano Banana prompts → A full app you host in Replit and customize for your team Built 100% in Claude Code with the gethookd.ai API + Gemini. I put together a free playbook with every prompt I used to build this app from scratch, so you can build it yourself. Want it for free? > Like this post > Comment "META" And I'll send it over (must be following so I can DM)

Mike Futia

53,889 görüntüleme • 6 ay önce

We’re creating something historic… and I want you to be part of it. 🎤🌍 Donate + join the biggest music movement in history here: On December 16, we’re gathering some of the world’s top artists at the iHeartRadio Theater in Los Angeles to create a brand-new anthem LIVE, produced by my friend and legendary music producer, Jimmy Jam Jimmy Jam. This moment is part of our 100 Billion Meals Challenge, powered by Round It Up®️, a mission to deliver 100 BILLION MEALS over the next decade. With partners around the world, we’ve already helped provide 62 billion meals in the past 3 years, and now, with your help and this song, we can get even closer to that goal. 🙏 And this recording session will be opened to the WORLD. We’re hosting it live on Zoom so anyone, anywhere, can join this movement in real time. ❤️ Here’s how you can be part of history: 👉 Donate $10+ to provide 44 meals and get guaranteed access to participate on the Zoom 👉 Join the Lifesavers Club and provide 1,000 meals this year + guaranteed Zoom access 👉 Submit your own verse on social media using #TheNextVerse and add your words to this global anthem! This isn’t just a recording session, it’s going to be the BIGGEST music movement in HISTORY to end world hunger. It’s a call to rise up, use our voices, and help feed millions more. Let’s make a song that doesn’t just inspire people… Let's make a song that feeds the world. Be the verse. Be the voice. Be the difference. #TheNextVerse

Tony Robbins

101,159 görüntüleme • 10 ay önce

Introducing my newest app, TethrX, made with Grok 4.5 to access Grok Build on your phone. TethrX connects to Grok Build running on your own computer, so you can start a task from anywhere, follow Grok's reasoning as it works, approve every command before it runs, and review the code it writes. Your code never leaves your machine. The public TestFlight is now open, and a demonstration is below. You pair your phone by scanning a QR code, either on your local network or from anywhere through Tailscale. From there TethrX streams Grok's reasoning, tool calls, command output and file changes as they happen, and asks your approval before anything runs. Plan mode lets you read the plan before the work begins. When a task finishes you can review exactly what changed. TethrX lists the modified files in your project, shows a diff for each one, and lets you commit or discard the work without leaving your phone. The app supports slash commands, including /compact and any skills you have installed, along with voice dictation, queued messages and reusable prompts. Sessions can be searched and organised into folders, and you can pair several computers and switch between them. Siri can start a task or tell you what Grok is doing without opening the app, a home screen widget shows whether Grok is working, and a Live Activity tracks progress on your lock screen and Dynamic Island. Every session reports its context window, token usage and cost, the app can be locked behind Face ID, and your computer is kept awake for as long as a task is running. TethrX requires Grok Build installed and signed in on your computer, together with Node.js 20 or newer. A single command starts the bridge: npx tethrx-bridge TethrX is open source under the Apache License 2.0. Both the iOS client and the local bridge are available here: Grok 4.5 helped a lot, thanks to SpaceXAI for making Grok 4.5 exceptional.

Introducing my newest app, TethrX, made with Grok 4.5 to access Grok Build on your phone. TethrX connects to Grok Build running on your own computer, so you can start a task from anywhere, follow Grok's reasoning as it works, approve every command before it runs, and review the code it writes. Your code never leaves your machine. The public TestFlight is now open, and a demonstration is below. You pair your phone by scanning a QR code, either on your local network or from anywhere through Tailscale. From there TethrX streams Grok's reasoning, tool calls, command output and file changes as they happen, and asks your approval before anything runs. Plan mode lets you read the plan before the work begins. When a task finishes you can review exactly what changed. TethrX lists the modified files in your project, shows a diff for each one, and lets you commit or discard the work without leaving your phone. The app supports slash commands, including /compact and any skills you have installed, along with voice dictation, queued messages and reusable prompts. Sessions can be searched and organised into folders, and you can pair several computers and switch between them. Siri can start a task or tell you what Grok is doing without opening the app, a home screen widget shows whether Grok is working, and a Live Activity tracks progress on your lock screen and Dynamic Island. Every session reports its context window, token usage and cost, the app can be locked behind Face ID, and your computer is kept awake for as long as a task is running. TethrX requires Grok Build installed and signed in on your computer, together with Node.js 20 or newer. A single command starts the bridge: npx tethrx-bridge TethrX is open source under the Apache License 2.0. Both the iOS client and the local bridge are available here: Grok 4.5 helped a lot, thanks to SpaceXAI for making Grok 4.5 exceptional.

Myrhe𝕩

13,099 görüntüleme • 2 ay önce

$How I Build My Teams I always liked the idea of ‘possession football’: - Control the game. - A tool to develop players. - The opponent can’t score without the ball. But I built it the wrong way: “Keep the ball. Find a gap to attack.” This turned into “side-to-side” passing. It was boring and ineffective. \ The idea. So, I flipped the idea: Instead of controlling to attack, we attack to control. Play as vertical as possible (while maintaining control). If not possible, pass back. Avoid sideways passes. For better connections and counter-press, we use a vertical, narrow structure: These simple decisions lead to short, vertical, and diagonal passes. This is what I call 'vertical possession' football. \ Make it work. The idea is simple. The execution is not. Over the years, I’ve worked to close the gap between vision and reality. (watch example below) My goal is to get closer to my vision every day. But as Vince Lombardi said: “Perfection is unattainable, but if we chase perfection we can catch excellence.” Here’s my plan to 'catch excellence': 1. Build it my way. Ignore opinions. Opinions lead to conformity. We reduce our philosophy to its essence—and build from there. Everything else is a distraction. 2. Stick to it. We limit ourselves to core principles, and stick to them. When there’s a problem, we don’t change the idea—we improve its execution. 3. Eliminate waste. Building a style of play is like carving a statue. You start with a block of marble and chip away everything unnecessary. All that’s left is the sculpture. We do the same. We cut every unnecessary touch and step: - Fewer touches mean we need less time and space. We have more space to be creative. - The simpler it gets, the more recognizable the style. 4. Obsess over the players. We don’t adapt to opponents. We focus on our players. That's what matters in the long run. When our ideas work, we can compete against anyone. 5. Develop technical and creative players as a by-product. - Possession: Many touches to refine technique. - Vertical: No “easy” sideways passes. Learn to play in tight spaces. - Control: Avoid hectic football. Control the ball to make deliberate decisions. 6. One Training Structure. We compress our philosophy into one structure. Then, we repeat it every session. We make our style of play a habit. And we develop the tools to execute it. 7. Master a Few Exercises. We repeat a small set of core games over and over. We focus on improving execution, not on new drills. The better we execute, the faster we get to our vision. 8. Bottleneck Coaching. We can’t predict what happens, so we don’t over-plan. Instead, we prepare for what might happen. This liberates our coaching: Rather than sticking to pre-planned coaching points, we solve the most critical issue—the bottleneck. 9. Competition Drives Development. Games are the core of our training. Players compete to win. They force each other to get better and better, session after session. 10. Positive Team Culture. I used to react with anger when things didn’t go right. And yes, it can work in the short term. But to build something great, players must stay on the path for a long time. This is more likely when they enjoy the process. Positive reinforcement is harder to do, but more sustainable. \ What's next? That's the plan. Now, it’s all about execution. I'll keep you updated.$

How I Build My Teams I always liked the idea of ‘possession football’: - Control the game. - A tool to develop players. - The opponent can’t score without the ball. But I built it the wrong way: “Keep the ball. Find a gap to attack.” This turned into “side-to-side” passing. It was boring and ineffective. \ The idea. So, I flipped the idea: Instead of controlling to attack, we attack to control. Play as vertical as possible (while maintaining control). If not possible, pass back. Avoid sideways passes. For better connections and counter-press, we use a vertical, narrow structure: These simple decisions lead to short, vertical, and diagonal passes. This is what I call 'vertical possession' football. \ Make it work. The idea is simple. The execution is not. Over the years, I’ve worked to close the gap between vision and reality. (watch example below) My goal is to get closer to my vision every day. But as Vince Lombardi said: “Perfection is unattainable, but if we chase perfection we can catch excellence.” Here’s my plan to 'catch excellence': 1. Build it my way. Ignore opinions. Opinions lead to conformity. We reduce our philosophy to its essence—and build from there. Everything else is a distraction. 2. Stick to it. We limit ourselves to core principles, and stick to them. When there’s a problem, we don’t change the idea—we improve its execution. 3. Eliminate waste. Building a style of play is like carving a statue. You start with a block of marble and chip away everything unnecessary. All that’s left is the sculpture. We do the same. We cut every unnecessary touch and step: - Fewer touches mean we need less time and space. We have more space to be creative. - The simpler it gets, the more recognizable the style. 4. Obsess over the players. We don’t adapt to opponents. We focus on our players. That's what matters in the long run. When our ideas work, we can compete against anyone. 5. Develop technical and creative players as a by-product. - Possession: Many touches to refine technique. - Vertical: No “easy” sideways passes. Learn to play in tight spaces. - Control: Avoid hectic football. Control the ball to make deliberate decisions. 6. One Training Structure. We compress our philosophy into one structure. Then, we repeat it every session. We make our style of play a habit. And we develop the tools to execute it. 7. Master a Few Exercises. We repeat a small set of core games over and over. We focus on improving execution, not on new drills. The better we execute, the faster we get to our vision. 8. Bottleneck Coaching. We can’t predict what happens, so we don’t over-plan. Instead, we prepare for what might happen. This liberates our coaching: Rather than sticking to pre-planned coaching points, we solve the most critical issue—the bottleneck. 9. Competition Drives Development. Games are the core of our training. Players compete to win. They force each other to get better and better, session after session. 10. Positive Team Culture. I used to react with anger when things didn’t go right. And yes, it can work in the short term. But to build something great, players must stay on the path for a long time. This is more likely when they enjoy the process. Positive reinforcement is harder to do, but more sustainable. \ What's next? That's the plan. Now, it’s all about execution. I'll keep you updated.

Bene Schneiderbauer

59,810 görüntüleme • 1 yıl önce

HERMES AGENT v0.17.0 JUST SHIPPED. "THE REACH RELEASE." 1,475 COMMITS. 800 PRs. 245 CONTRIBUTORS. HERMES NOW REACHES IMESSAGE, RAFT NETWORK, AND CURSOR'S COMPOSER MODEL. the highlights: Nous Research iMESSAGE WITHOUT A MAC RELAY Photon Spectrum integration ships native iMessage support. no Mac in a closet. no BlueBubbles bridge. hermes photon login → device code auth → done. Hermes lives in the blue bubbles now. ASYNC SUBAGENTS NO LONGER BLOCK YOUR CHAT delegate_task(background=true) dispatches a subagent that runs in the background. returns a handle immediately. you keep working. result re-enters as a new turn when it finishes. long research dives stop blocking your main session. IMAGE EDITING, NOT JUST GENERATION image_generate now edits source images. "make this logo blue." "remove the background." "turn this sketch into a render." works across every supported image provider. same tool, new mode. CURSOR'S COMPOSER MODEL VIA GROK OAUTH grok-composer-2.5-fast is in the xAI model picker. 200k context window. fast coding model behind Cursor. your Grok subscription. Hermes's agent loop. no separate API key needed. AUTOMATION BLUEPRINTS schedule tasks without learning cron syntax. "daily news briefing at 8am" becomes a form. one blueprint definition renders everywhere: dashboard form, CLI slash command, Telegram chat, docs catalog entry. answer questions, not memorize 0 8 * * *. FULL PROFILE BUILDER IN DASHBOARD build a complete Hermes profile from the browser. pick model. choose skills. attach MCPs. no config.yaml editing. plus unified multi-profile view with global switcher. SKILLS HUB BROWSER REHAUL connected hubs (OpenAI, Anthropic, HuggingFace, NVIDIA). Featured section. full skill previews before install. security scan on each skill. browsing skills is a real browsing experience now. ATOMIC MEMORY OPERATIONS memory tool gained an operations array. batch add/replace/remove edits applied atomically. the model can free space and add entries in ONE call even when individual adds would overflow the budget. memory updates no longer fail mid-edit. CURATOR STOPPED SPENDING TOKENS BY DEFAULT deterministic skill pruning still runs free. LLM-powered consolidation now opt-in only: curator.consolidate: true to enable. routine background curation costs you zero tokens. WHATSAPP BUSINESS CLOUD API official Meta adapter alongside existing Baileys bridge. no QR-scanning bridge process to keep alive. hosted, first-party WhatsApp channel. TELEGRAM RICH MESSAGES (BOT API 10.1) proper rich formatting. cleaner long-message handling. native markup instead of flattened text. on by default. opt-out available. DESKTOP APP IS NOW A DAILY DRIVER rebindable keyboard shortcuts. native OS notifications. live subagent watch-windows streaming activity. composer model selector with per-model presets. automatic RTL/bidi text. resizable VS Code terminal pane. per-thread composer drafts. install ANY VS Code Marketplace theme. RAFT AGENT NETWORK new bundled adapter connects Hermes to raft. build as an external agent. wake-channel bridge. privacy by contract: wake payloads carry metadata only, never message bodies. SECURE DASHBOARD LOGIN every token-required endpoint returns 401 behind OAuth gate. websocket auth uses served dashboard token. public_url override warnings. exposing your dashboard to the network is safer by default. upgrade: hermes update 300+ issues closed. security round included. hermes-agent ecosystem now at 198K GitHub stars.

YanXbt

35,261 görüntüleme • 3 ay önce

$HERMES AGENT HAS FEATURES THAT 90% OF USERS NEVER TOUCH. /BACKGROUND. /STEER. /GOAL. SUB-AGENTS. MODEL SWITCHING. CRON JOBS. 7 LEVELS OF HERMES. ALL EXPLAINED.👇 LEVEL 1 — ONE-SHOT PROMPTS you type a prompt. agent responds. done. this is using Hermes as a chatbot. it works but you leave 90% of the value untouched. LEVEL 2 — MEMORY + SOUL.MD the agent remembers you across sessions. you wrote a SOUL.md with identity, voice, restrictions. Hermes tailors every answer to your context. two people asking the same question get different answers because it knows them differently. LEVEL 3 — COMMANDS THAT MULTIPLY OUTPUT /background → fires a task in the background. your main session stays free. result appears as a panel when done. /steer → injects a message into the current run without interrupting the agent. redirects the work mid-execution. /queue → queues a follow-up for after the current task finishes. /model → switches models mid-session. start with Sonnet for planning. switch to DeepSeek for execution. switch to Opus for review. configure default behavior: display: busy_input_mode: steer # or queue, or interrupt LEVEL 4 — SKILLS + RIGHT MODEL PER SKILL every installed skill becomes a slash command: /competitive-research analyze my top 3 competitors /social-media-copy write 5 LinkedIn posts /code-review check this PR for security issues the unlock: assign a specific model per skill. research skill → GPT-5.5 (cheap, high volume). code review skill → Fable 5 (best at code). content skill → Sonnet (best at writing). you stop paying premium prices for tasks that don't need premium models. LEVEL 5 — MCPs (CONNECT YOUR WORLD) plug Hermes into the tools you already use: Gmail, Calendar, Notion, Slack, ClickUp, Granola. the agent reads your emails, checks your calendar, pulls from your project management tool, and answers questions using YOUR actual data. "what were the numbers this week?" Hermes checks ClickUp, cross-references with your goals in memory, gives a contextualized answer. caveat from the docs: keep MCPs minimal. every MCP adds tools to the context window. 15 MCPs with 10 tools each = 150 tool schemas the model reads every turn. install what you use. disable what you don't. LEVEL 6 — SUB-AGENTS + PARALLEL EXECUTION delegate_task spawns sub-agents with isolated context. batch mode runs children in parallel: delegate_task(tasks=[ {goal: "research best industries for websites", model: "deepseek-v4-flash"}, {goal: "critique the research and find gaps", model: "gpt-5.5"}, ]) max_concurrent_children: 3 (default). each child gets own terminal session and toolset. parent receives summaries when children finish. roles: → leaf (default): cannot re-delegate → orchestrator: can spawn its own workers (bounded by delegation.max_spawn_depth) LEVEL 7 — ASYNC OPERATIONS this is where the agent works without you. /goal — persistent objective across turns. judge model checks after every turn. runs until done or budget hit (default 20 turns). cron jobs — scheduled tasks on repeat. morning briefs, competitor scans, weekly reviews. wakeAgent gates for zero-token monitoring. /background — parallel tasks in current session. results delivered when ready. your main conversation never stops. the shift: from "I ask, it responds" to "it works, I review." WHERE ARE YOU? 1 → chatbot 2 → it knows you 3 → parallel commands 4 → right model per task 5 → connected to your tools 6 → sub-agents working together 7 → runs without you most people are at 2-3. the jump from 4 to 7 is where the real time savings compound. this is just the first 7. beyond this: multi-profile architecture, self-improving knowledge bases, voice mode, kanban orchestration, webhook automation, profile distributions, browser control, IDE integration, and more. comment LEVEL and I'll send you the advanced levels with setup for each. Full guide how to build 3-agent research department with Hermes 👇$

HERMES AGENT HAS FEATURES THAT 90% OF USERS NEVER TOUCH. /BACKGROUND. /STEER. /GOAL. SUB-AGENTS. MODEL SWITCHING. CRON JOBS. 7 LEVELS OF HERMES. ALL EXPLAINED.👇 LEVEL 1 — ONE-SHOT PROMPTS you type a prompt. agent responds. done. this is using Hermes as a chatbot. it works but you leave 90% of the value untouched. LEVEL 2 — MEMORY + SOUL.MD the agent remembers you across sessions. you wrote a SOUL.md with identity, voice, restrictions. Hermes tailors every answer to your context. two people asking the same question get different answers because it knows them differently. LEVEL 3 — COMMANDS THAT MULTIPLY OUTPUT /background → fires a task in the background. your main session stays free. result appears as a panel when done. /steer → injects a message into the current run without interrupting the agent. redirects the work mid-execution. /queue → queues a follow-up for after the current task finishes. /model → switches models mid-session. start with Sonnet for planning. switch to DeepSeek for execution. switch to Opus for review. configure default behavior: display: busy_input_mode: steer # or queue, or interrupt LEVEL 4 — SKILLS + RIGHT MODEL PER SKILL every installed skill becomes a slash command: /competitive-research analyze my top 3 competitors /social-media-copy write 5 LinkedIn posts /code-review check this PR for security issues the unlock: assign a specific model per skill. research skill → GPT-5.5 (cheap, high volume). code review skill → Fable 5 (best at code). content skill → Sonnet (best at writing). you stop paying premium prices for tasks that don't need premium models. LEVEL 5 — MCPs (CONNECT YOUR WORLD) plug Hermes into the tools you already use: Gmail, Calendar, Notion, Slack, ClickUp, Granola. the agent reads your emails, checks your calendar, pulls from your project management tool, and answers questions using YOUR actual data. "what were the numbers this week?" Hermes checks ClickUp, cross-references with your goals in memory, gives a contextualized answer. caveat from the docs: keep MCPs minimal. every MCP adds tools to the context window. 15 MCPs with 10 tools each = 150 tool schemas the model reads every turn. install what you use. disable what you don't. LEVEL 6 — SUB-AGENTS + PARALLEL EXECUTION delegate_task spawns sub-agents with isolated context. batch mode runs children in parallel: delegate_task(tasks=[ {goal: "research best industries for websites", model: "deepseek-v4-flash"}, {goal: "critique the research and find gaps", model: "gpt-5.5"}, ]) max_concurrent_children: 3 (default). each child gets own terminal session and toolset. parent receives summaries when children finish. roles: → leaf (default): cannot re-delegate → orchestrator: can spawn its own workers (bounded by delegation.max_spawn_depth) LEVEL 7 — ASYNC OPERATIONS this is where the agent works without you. /goal — persistent objective across turns. judge model checks after every turn. runs until done or budget hit (default 20 turns). cron jobs — scheduled tasks on repeat. morning briefs, competitor scans, weekly reviews. wakeAgent gates for zero-token monitoring. /background — parallel tasks in current session. results delivered when ready. your main conversation never stops. the shift: from "I ask, it responds" to "it works, I review." WHERE ARE YOU? 1 → chatbot 2 → it knows you 3 → parallel commands 4 → right model per task 5 → connected to your tools 6 → sub-agents working together 7 → runs without you most people are at 2-3. the jump from 4 to 7 is where the real time savings compound. this is just the first 7. beyond this: multi-profile architecture, self-improving knowledge bases, voice mode, kanban orchestration, webhook automation, profile distributions, browser control, IDE integration, and more. comment LEVEL and I'll send you the advanced levels with setup for each. Full guide how to build 3-agent research department with Hermes 👇

YanXbt

31,551 görüntüleme • 3 ay önce

If you watch this ~50 minute screen recording closely (yeah, I know, it's long; there are also some times when my computer was very slow and laggy, just skip past that part. And at one point I had to run and get my 9-month-old a new bottle and left it on a boring screen, sorry!), I believe you can see real signs of the kind of runaway, recursive AI self-improvement that people have been warning of for a while (Mr. Kurzweil most notably and prophetically). Why do I say that? What's different now? Well, there's a reason my set of agent coding tooling is called the Flywheel. These tools all mutually self-reinforce each other. And they all flow directly into my ntm tool (short for "named_tmux_manager"), which acts as a sort of integration point and nerve center for the tools (this is becoming more true by the minute as I'm now seriously working on ntm). Now, ntm was something I started making to automate some aspects of my workflow, but it was the kind of thing where, until it was perfect, it sort of just slowed me down. So I didn't actually use it even though I kept working on it and trying to improve it, and suggested to users that they try it in my tutorials. Well anyway, I finally got around to "dogfooding" ntm last night, and now it's going to get very dramatically better at an alarming rate. Some of that is from applying my "idea wizard" prompt to generate more useful features and building that stuff out and addressing obvious pain points I encountered during my newfound usage of the tool. But a lot comes from my realization that, once again, ntm's true utility is not as a tool for ME, but for an agent. That is, ntm lets one instance of Claude Code or Codex act as, well, me, do the things that I had been doing manually. Do I wish I had started using ntm earlier? No, for two big reasons: 1) Doing it manually helped me build up my intuition massively, which directly led me down the path of creating useful prompt strategies and workflows; these often began as ad-hoc prompts that I realized could be generalized and made more versatile/universal. Lesson: don't prematurely automate until you have an intimate, intuitive feel for your "core value-add loop." Otherwise you'll have a fully automated system quickly that efficiently and automatically does a stupid or otherwise sub-optimal thing. 2) My eyes have been opened to the beauty and power of Skills. I'm not talking about your garden-variety skills that are just a simple markdown file. I'm talking about true tour-de-force directories of perfectly structured and organized files that are filled with good information, insights, workflows, etc., but presented in a way that is highly optimized for consumption by AI agents, with extreme attention paid to things like perfect progressive disclosure, token density, agent-ergonomics, agent-intuitiveness, etc. And also Skills that go way beyond markdown files, with full integration into Claude Code where it makes sense via hooks, sub-agents, and even Python scripts. These kinds of skills are a qualitative difference in expressive power and usefulness and a total game changer. They are also effectively composable, creating almost an algebra of skills that let you use them together in powerful ways. I'm working on a subscription service website and CLI tool now to share what I've learned here most effectively, stay tuned for that in the coming days. Anyway, I now know what to make and how to make it. So, getting back to that screen recording, what does it show that makes me claim recursive self-improvement is here? If you keep your eye on the upper left tmux pane, that's the "controller" agent. It is using ntm to control all the other panes which are also running Claude Code (but ntm fully supports other agent types like Codex and Gemini-CLI, and it's trivially easy to mix and match them if you wanted to have, say, 8 CCs and 6 Codexes for writing the code and 3 Gemini-CLIs for reviewing code.) Now, there's nothing that crazy about this much so far. But where it starts to get very cool is that as the session continues and we encounter real-world problems, things like my ridiculously overloaded computer that keeps hanging for long periods, Claude Code instances that crash and get into a frozen, unresponsive state, it can learn from that. And you can see it using my skill writing skill to refine its ntm vibe coding skill in real time. And then take that skill and refine it to be more intuitive for itself. Or use my cass tool skill to search all the session histories to look for problems that came up and strategize how to solve them. The most useful part was when, towards the end of the session, I told it to reflect on all the things we had done and problems we encountered. One way it can usefully leverage those reflections is by improving its ntm vibe coding skill to make it cover more edge cases and exigencies. But the other, more fundamental, way is for it to conceive of and design the optimal new features and functionality for ntm itself so that the tool embodies those lessons in a first-class way. This offloads cognition from its brain onto its tooling, just like how a person can lean on spellcheck or a calculator. It codifies correct, effective reasoning at the tool level, where it's more reliable and robust and repeatable. And btw, did you notice what code base it was working on the whole time? It was none other than ntm itself! So as it worked on its own tool, it had reflections and ideas about how to further improve the tool. Now, it could have just as easily gotten those insights and ideas while using ntm to work on a different project, but the fact that it was working on itself is almost gloriously meta and recursive. So by the end, after learning from tending to a big group of agent workers (btw, I have previously emphasized doing everything in a really distributed/decentralized way, where each fungible agent gets identical marching orders that tell it to use my bv tool to find the optimal bead to work on. This does work very well, but occasionally results in some contention and overlap from thundering herd, or at least wastes time/tokens/communication in avoiding that before the agents waste time duplicating work. But in this new ntm-oriented workflow, I was able to have the controller agent in the upper left use bv itself and then optimally parcel out the instructions to each agent so that we could know for sure that there's no overlap), I ended up with a ton of new beads for new features, which I had it optimize and polish a few times. Now I can swap to a new Claude Max account and have the swarm implement all those new features! It should only take a couple passes like the one shown in the screen recording to get everything implemented. Then we can rinse and repeat, having the agent read through the full session histories of each agent and its experience from its own session in sending ntm commands and seeing how they worked out in practice, to come up with the next batch of changes to both its ntm vibe coding skill AND to the ntm tool itself. Do you see how rapidly this turns into Skynet? My mistake earlier was in focusing on making myself a "faster horse" as Henry Ford used to joke about customers wanting before he showed them what they should really want (a Model T). That is, something that would make my experience nicer while doing this agent swarm based development workflow. But the obvious lesson is that you should make all your tooling agent-first because the agents are just better at this stuff. You can still watch, and of course I did add a ridiculous number of very nice human-centric features to ntm that you'll be seeing in the next day or two, but those are really kind of "for fun" to make us humans feel better about the process. All the real value-add is happening "by agents, for agents." PS: Towards the end, you can see me switch to my Mac and tell Claude to improve the skill that I made earlier today for taking the mkv screen recording files from OBS Studio and muxing them into MP4 files for sharing, while downloading songs from YouTube to serve as the background music. I made it so it can also grab the thumbnails and generate little song credit cards that show up in the lower right corner. This worked perfectly the first time! I'll include some screenshots in a response post showing how that worked, but it was awesome to witness. Skills are POWERFUL. I'll also post a link to this video on YouTube if you prefer to watch it there.

If you watch this ~50 minute screen recording closely (yeah, I know, it's long; there are also some times when my computer was very slow and laggy, just skip past that part. And at one point I had to run and get my 9-month-old a new bottle and left it on a boring screen, sorry!), I believe you can see real signs of the kind of runaway, recursive AI self-improvement that people have been warning of for a while (Mr. Kurzweil most notably and prophetically). Why do I say that? What's different now? Well, there's a reason my set of agent coding tooling is called the Flywheel. These tools all mutually self-reinforce each other. And they all flow directly into my ntm tool (short for "named_tmux_manager"), which acts as a sort of integration point and nerve center for the tools (this is becoming more true by the minute as I'm now seriously working on ntm). Now, ntm was something I started making to automate some aspects of my workflow, but it was the kind of thing where, until it was perfect, it sort of just slowed me down. So I didn't actually use it even though I kept working on it and trying to improve it, and suggested to users that they try it in my tutorials. Well anyway, I finally got around to "dogfooding" ntm last night, and now it's going to get very dramatically better at an alarming rate. Some of that is from applying my "idea wizard" prompt to generate more useful features and building that stuff out and addressing obvious pain points I encountered during my newfound usage of the tool. But a lot comes from my realization that, once again, ntm's true utility is not as a tool for ME, but for an agent. That is, ntm lets one instance of Claude Code or Codex act as, well, me, do the things that I had been doing manually. Do I wish I had started using ntm earlier? No, for two big reasons: 1) Doing it manually helped me build up my intuition massively, which directly led me down the path of creating useful prompt strategies and workflows; these often began as ad-hoc prompts that I realized could be generalized and made more versatile/universal. Lesson: don't prematurely automate until you have an intimate, intuitive feel for your "core value-add loop." Otherwise you'll have a fully automated system quickly that efficiently and automatically does a stupid or otherwise sub-optimal thing. 2) My eyes have been opened to the beauty and power of Skills. I'm not talking about your garden-variety skills that are just a simple markdown file. I'm talking about true tour-de-force directories of perfectly structured and organized files that are filled with good information, insights, workflows, etc., but presented in a way that is highly optimized for consumption by AI agents, with extreme attention paid to things like perfect progressive disclosure, token density, agent-ergonomics, agent-intuitiveness, etc. And also Skills that go way beyond markdown files, with full integration into Claude Code where it makes sense via hooks, sub-agents, and even Python scripts. These kinds of skills are a qualitative difference in expressive power and usefulness and a total game changer. They are also effectively composable, creating almost an algebra of skills that let you use them together in powerful ways. I'm working on a subscription service website and CLI tool now to share what I've learned here most effectively, stay tuned for that in the coming days. Anyway, I now know what to make and how to make it. So, getting back to that screen recording, what does it show that makes me claim recursive self-improvement is here? If you keep your eye on the upper left tmux pane, that's the "controller" agent. It is using ntm to control all the other panes which are also running Claude Code (but ntm fully supports other agent types like Codex and Gemini-CLI, and it's trivially easy to mix and match them if you wanted to have, say, 8 CCs and 6 Codexes for writing the code and 3 Gemini-CLIs for reviewing code.) Now, there's nothing that crazy about this much so far. But where it starts to get very cool is that as the session continues and we encounter real-world problems, things like my ridiculously overloaded computer that keeps hanging for long periods, Claude Code instances that crash and get into a frozen, unresponsive state, it can learn from that. And you can see it using my skill writing skill to refine its ntm vibe coding skill in real time. And then take that skill and refine it to be more intuitive for itself. Or use my cass tool skill to search all the session histories to look for problems that came up and strategize how to solve them. The most useful part was when, towards the end of the session, I told it to reflect on all the things we had done and problems we encountered. One way it can usefully leverage those reflections is by improving its ntm vibe coding skill to make it cover more edge cases and exigencies. But the other, more fundamental, way is for it to conceive of and design the optimal new features and functionality for ntm itself so that the tool embodies those lessons in a first-class way. This offloads cognition from its brain onto its tooling, just like how a person can lean on spellcheck or a calculator. It codifies correct, effective reasoning at the tool level, where it's more reliable and robust and repeatable. And btw, did you notice what code base it was working on the whole time? It was none other than ntm itself! So as it worked on its own tool, it had reflections and ideas about how to further improve the tool. Now, it could have just as easily gotten those insights and ideas while using ntm to work on a different project, but the fact that it was working on itself is almost gloriously meta and recursive. So by the end, after learning from tending to a big group of agent workers (btw, I have previously emphasized doing everything in a really distributed/decentralized way, where each fungible agent gets identical marching orders that tell it to use my bv tool to find the optimal bead to work on. This does work very well, but occasionally results in some contention and overlap from thundering herd, or at least wastes time/tokens/communication in avoiding that before the agents waste time duplicating work. But in this new ntm-oriented workflow, I was able to have the controller agent in the upper left use bv itself and then optimally parcel out the instructions to each agent so that we could know for sure that there's no overlap), I ended up with a ton of new beads for new features, which I had it optimize and polish a few times. Now I can swap to a new Claude Max account and have the swarm implement all those new features! It should only take a couple passes like the one shown in the screen recording to get everything implemented. Then we can rinse and repeat, having the agent read through the full session histories of each agent and its experience from its own session in sending ntm commands and seeing how they worked out in practice, to come up with the next batch of changes to both its ntm vibe coding skill AND to the ntm tool itself. Do you see how rapidly this turns into Skynet? My mistake earlier was in focusing on making myself a "faster horse" as Henry Ford used to joke about customers wanting before he showed them what they should really want (a Model T). That is, something that would make my experience nicer while doing this agent swarm based development workflow. But the obvious lesson is that you should make all your tooling agent-first because the agents are just better at this stuff. You can still watch, and of course I did add a ridiculous number of very nice human-centric features to ntm that you'll be seeing in the next day or two, but those are really kind of "for fun" to make us humans feel better about the process. All the real value-add is happening "by agents, for agents." PS: Towards the end, you can see me switch to my Mac and tell Claude to improve the skill that I made earlier today for taking the mkv screen recording files from OBS Studio and muxing them into MP4 files for sharing, while downloading songs from YouTube to serve as the background music. I made it so it can also grab the thumbnails and generate little song credit cards that show up in the lower right corner. This worked perfectly the first time! I'll include some screenshots in a response post showing how that worked, but it was awesome to witness. Skills are POWERFUL. I'll also post a link to this video on YouTube if you prefer to watch it there.

Jeffrey Emanuel

25,483 görüntüleme • 8 ay önce

I finally finished my Rust version of Mario Zechner's (Mario Zechner) excellent Pi Agent, which I made with his blessing and which is called pi_agent_rust. You can get it here: If you're not familiar with Pi, it's a minimalist and extensible agent harness (similar to Claude Code and Codex) and, among other uses, serves as the core agent harness inside the OpenClaw project. I say my Rust "version" instead of "port" because it's really quite different in how it's implemented for it to be called a port. Arguably, the incremental functionality in the implementation was more complex than the rest of the project combined. Still, it provides the same features and functionality as the original, and is proven to be compatible with hundreds of popular extensions to Pi (the conformance harness shows 224 out of 224 extensions working perfectly). But the way it's architected has some major changes. Pi Agent relies on node or bun to provide access to the filesystem and for various other tasks, and that is also how Pi's extension system works. I decided early on that I didn't want to do things that way. Instead, I wanted to integrate that functionality directly into the binary itself; that is, to provide equivalent functionality for everything that would normally be provided by node/bun in the original. I did this for several reasons: one, it's a lot more performant in terms of footprint and latency. On realistic end-to-end large-session workloads (not toy microbenchmarks), pi_agent_rust is now: - 4.95x faster than legacy Node and 2.80x faster than legacy Bun at 1mm-token session scale - 4.32x faster than legacy Node and 2.14x faster than legacy Bun at 5mm-token session scale - ~8x to ~13x lower RSS memory footprint in those same scenarios But the other reason is security and control: by handling everything internally in an end-to-end way, we can do all sorts of clever things to harden the system against insecure or malicious extensions. Those extensions no longer have direct access to the ambient filesystem: they now need to go through pi_agent_rust, and we can analyze extensions carefully before ever running them and also block things that look suspicious at runtime. In practice that means explicit capability-gated hostcalls, with policy/risk/quota enforcement and runtime telemetry/auditability. In order to do all this, I had to effectively build the missing runtime substrate from scratch in Rust, not just translate TypeScript syntax: - define and implement a typed hostcall ABI for extension->host interactions - build native Rust connectors for tool/exec/http/session/ui/events instead of ambient Node/Bun access - implement a compatibility/shim layer so real-world Pi extensions still behave correctly - add capability policy evaluation, runtime risk scoring, per-extension quotas, and audit telemetry on the execution path - wire the whole thing through structured concurrency (asupersync) so cancellation/lifetimes are deterministic and failure handling is explicit - build a conformance + benchmark harness large enough to validate behavior/perf across hundreds of extensions and realistic long-session workloads This was a full re-architecture of the execution model while preserving the Pi workflow and extension ecosystem. And indeed, this aspect of it dwarfs the entire rest of the project in size and complexity. To put hard numbers on that: the extension/runtime/security subsystem alone is now about 86.5k lines of Rust across src/extensions.rs (~48.1k), src/extensions_js.rs (~23.4k), src/extension_dispatcher.rs (~13.4k), and src/extension_index.rs (~1.7k), with roughly 2.5k callable units in just those files. For context, the original Pi coding-agent production code is about 27.4k lines total. So this one subsystem by itself is roughly 3.2x the size of the original harness, which is why calling this a “port” would seriously undersell what had to be built. And on top of that, pi_agent_rust introduces a bunch of genuinely new capabilities beyond the legacy harness, not just a faster core: - Security and enforcement are materially stronger at runtime: capability-gated hostcalls with explicit policy profiles (safe/balanced/permissive), per-extension trust lifecycle (pending -> acknowledged -> trusted -> killed), explicit kill-switch operations, and audited state transitions. - Shell execution mediation is deterministic and argument-aware: rule/feature-based risk scoring plus heredoc AST inspection (dcg_rule_hit, dcg_heredoc_hit) before spawn, instead of relying on coarse deny patterns. - Containment and forensics are first-class: tamper-evident runtime risk ledger tooling (verify/replay/calibrate), unified incident evidence bundles, and forced-compat controls that let you contain issues without disabling the whole extension system. - The extension runtime architecture is native: JS extensions run in embedded QuickJS with typed hostcall boundaries and Rust-native connectors for tool/exec/http/session/ui/events, plus compatibility shims for real-world legacy extensions. - Runtime behavior under load is explicitly engineered: deterministic hostcall reactor mesh, fast-lane vs compat-lane routing, and warm-isolate prewarm handoff for more predictable throughput and latency under contention. - Long-session reliability is upgraded: JSONL v3 sessions with indexed sidecar acceleration and optional SQLite-backed sessions, plus operational controls via --session-durability, --no-migrations, and migrate. - Provider and auth coverage are broader and more operationally explicit: native Anthropic/OpenAI (Chat + Responses)/Gemini/Cohere/Azure/Bedrock/Vertex/Copilot/GitLab plus large OpenAI-compatible routing; pi --list-providers currently shows 90 providers with aliases and required auth env keys. - Auth is not just API keys: OAuth (Anthropic/OpenAI Codex/Gemini CLI/Antigravity/Kimi/Copilot/GitLab plus extension-defined OAuth), AWS credential chains (Bedrock), service-key exchange (SAP AI Core), and bearer-token flows. - Operator tooling is stronger: pi doctor supports scoped checks (config, dirs, auth, shell, sessions, extensions), machine-readable output (--format json|markdown), and safe auto-remediation (--fix). - Extension/package lifecycle workflows are built in: install, remove, update, update-index, search, info, and list. I want to thank Mario for making a great harness and for not telling me to get lost when I asked him if he was OK with me porting it to Rust. I may give him a hard time in jest about not going "full clanker," but that doesn't mean that I don't respect his work a huge amount. PS: There could still be bugs. If you find some, please let me know in GitHub Issues and I'll fix them same day. There's always a tradeoff between perfect and getting stuff out the door and I felt like it was time to release this.

I finally finished my Rust version of Mario Zechner's (Mario Zechner) excellent Pi Agent, which I made with his blessing and which is called pi_agent_rust. You can get it here: If you're not familiar with Pi, it's a minimalist and extensible agent harness (similar to Claude Code and Codex) and, among other uses, serves as the core agent harness inside the OpenClaw project. I say my Rust "version" instead of "port" because it's really quite different in how it's implemented for it to be called a port. Arguably, the incremental functionality in the implementation was more complex than the rest of the project combined. Still, it provides the same features and functionality as the original, and is proven to be compatible with hundreds of popular extensions to Pi (the conformance harness shows 224 out of 224 extensions working perfectly). But the way it's architected has some major changes. Pi Agent relies on node or bun to provide access to the filesystem and for various other tasks, and that is also how Pi's extension system works. I decided early on that I didn't want to do things that way. Instead, I wanted to integrate that functionality directly into the binary itself; that is, to provide equivalent functionality for everything that would normally be provided by node/bun in the original. I did this for several reasons: one, it's a lot more performant in terms of footprint and latency. On realistic end-to-end large-session workloads (not toy microbenchmarks), pi_agent_rust is now: - 4.95x faster than legacy Node and 2.80x faster than legacy Bun at 1mm-token session scale - 4.32x faster than legacy Node and 2.14x faster than legacy Bun at 5mm-token session scale - ~8x to ~13x lower RSS memory footprint in those same scenarios But the other reason is security and control: by handling everything internally in an end-to-end way, we can do all sorts of clever things to harden the system against insecure or malicious extensions. Those extensions no longer have direct access to the ambient filesystem: they now need to go through pi_agent_rust, and we can analyze extensions carefully before ever running them and also block things that look suspicious at runtime. In practice that means explicit capability-gated hostcalls, with policy/risk/quota enforcement and runtime telemetry/auditability. In order to do all this, I had to effectively build the missing runtime substrate from scratch in Rust, not just translate TypeScript syntax: - define and implement a typed hostcall ABI for extension->host interactions - build native Rust connectors for tool/exec/http/session/ui/events instead of ambient Node/Bun access - implement a compatibility/shim layer so real-world Pi extensions still behave correctly - add capability policy evaluation, runtime risk scoring, per-extension quotas, and audit telemetry on the execution path - wire the whole thing through structured concurrency (asupersync) so cancellation/lifetimes are deterministic and failure handling is explicit - build a conformance + benchmark harness large enough to validate behavior/perf across hundreds of extensions and realistic long-session workloads This was a full re-architecture of the execution model while preserving the Pi workflow and extension ecosystem. And indeed, this aspect of it dwarfs the entire rest of the project in size and complexity. To put hard numbers on that: the extension/runtime/security subsystem alone is now about 86.5k lines of Rust across src/extensions.rs (~48.1k), src/extensions_js.rs (~23.4k), src/extension_dispatcher.rs (~13.4k), and src/extension_index.rs (~1.7k), with roughly 2.5k callable units in just those files. For context, the original Pi coding-agent production code is about 27.4k lines total. So this one subsystem by itself is roughly 3.2x the size of the original harness, which is why calling this a “port” would seriously undersell what had to be built. And on top of that, pi_agent_rust introduces a bunch of genuinely new capabilities beyond the legacy harness, not just a faster core: - Security and enforcement are materially stronger at runtime: capability-gated hostcalls with explicit policy profiles (safe/balanced/permissive), per-extension trust lifecycle (pending -> acknowledged -> trusted -> killed), explicit kill-switch operations, and audited state transitions. - Shell execution mediation is deterministic and argument-aware: rule/feature-based risk scoring plus heredoc AST inspection (dcg_rule_hit, dcg_heredoc_hit) before spawn, instead of relying on coarse deny patterns. - Containment and forensics are first-class: tamper-evident runtime risk ledger tooling (verify/replay/calibrate), unified incident evidence bundles, and forced-compat controls that let you contain issues without disabling the whole extension system. - The extension runtime architecture is native: JS extensions run in embedded QuickJS with typed hostcall boundaries and Rust-native connectors for tool/exec/http/session/ui/events, plus compatibility shims for real-world legacy extensions. - Runtime behavior under load is explicitly engineered: deterministic hostcall reactor mesh, fast-lane vs compat-lane routing, and warm-isolate prewarm handoff for more predictable throughput and latency under contention. - Long-session reliability is upgraded: JSONL v3 sessions with indexed sidecar acceleration and optional SQLite-backed sessions, plus operational controls via --session-durability, --no-migrations, and migrate. - Provider and auth coverage are broader and more operationally explicit: native Anthropic/OpenAI (Chat + Responses)/Gemini/Cohere/Azure/Bedrock/Vertex/Copilot/GitLab plus large OpenAI-compatible routing; pi --list-providers currently shows 90 providers with aliases and required auth env keys. - Auth is not just API keys: OAuth (Anthropic/OpenAI Codex/Gemini CLI/Antigravity/Kimi/Copilot/GitLab plus extension-defined OAuth), AWS credential chains (Bedrock), service-key exchange (SAP AI Core), and bearer-token flows. - Operator tooling is stronger: pi doctor supports scoped checks (config, dirs, auth, shell, sessions, extensions), machine-readable output (--format json|markdown), and safe auto-remediation (--fix). - Extension/package lifecycle workflows are built in: install, remove, update, update-index, search, info, and list. I want to thank Mario for making a great harness and for not telling me to get lost when I asked him if he was OK with me porting it to Rust. I may give him a hard time in jest about not going "full clanker," but that doesn't mean that I don't respect his work a huge amount. PS: There could still be bugs. If you find some, please let me know in GitHub Issues and I'll fix them same day. There's always a tradeoff between perfect and getting stuff out the door and I felt like it was time to release this.

Jeffrey Emanuel

136,417 görüntüleme • 7 ay önce

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👇

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

23,088 görüntüleme • 3 ay önce

$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.$

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 görüntüleme • 5 ay önce

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.

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 görüntüleme • 6 ay önce

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.

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 görüntüleme • 5 ay önce

Introducing: GTM Elites The premium community for top 1% outbound & GTM operators. Over the last few months, I have been quietly building GTM Elites, what will be THE most valuable outbound/GTM community on the market in 2026. Here’s what the community will include: 1. Access to our end-to-end outbound / GTM / cold email course with over 100 modules covering: > How we setup Claude Code & practical + advanced ways we use it for outbound/GTM > 30+ Clay workflow breakdowns with workbook templates you can plug-n-play > Swipe file of 200+ top performing email scripts (can use as a context file for CC) > Step-by-step walkthrough of the campaign creation process that's driven 30,000+ positive responses for our clients > Full walkthrough to setup a top 0.1% cold email infrastructure > Dozens of masterclasses covering messaging, list building, and campaign creation > All recordings from past internal trainings, insider calls, and webinars Modules will be updated weekly over time to stay up to date with the latest shifts in GTM. 2. THREE weekly 1-hour group calls with myself, Shaw, and Lohit > Wednesday: GTM Strategy workshops with Shaw (head of GTM @ Pipeline tech) > Thursday: Claude Code & Clay sessions with Lohit (COO @ Pipeline tech) > Friday: Campaign & strategy review sessions with Christian (Founder @ Pipeline tech) Combined, our coaches have 11+ years of GTM experience, sent 10,000,000+ emails, generated 30,000+ leads, and $ 70M in pipeline. Our calls will be open floor Q&A style — so any questions you have, we’ll be there to answer no matter how niche or technical. 3. Daily GTM insight posts from myself or the coaches > New skills we’re building with Claude Code > New Clay workbook templates > Internal campaign insights on what's working right now > Real-time market shifts to be aware of > Early GTM tool finds 4. Personal DM access to myself and coaches > #/ask-the-experts channel, get questions answered in 24 hours > DM us individually and we’ll get back within 48 hours > Access on live calls for questions as well 5. Access to exclusive discounts to BEST in market software only available in GTM Elites > Ocean io > ScaledMail > EmailBison > Prospeo > Sending ac Any popular tools that the community wants to get discounts on, we’ll reach out to the providers for the community directly and secure us exclusive discounts. 6. Exclusive weekly workflow drops > Get access to new Claude code skills, Clay workbook templates, & n8n templates that we’re building and using for ourselves and clients in real time 7. Job/Hiring opportunities > Live GTM Job Board Monitoring > Job opportunities from others in the community > Looking to hire? Our community is going to have GTM professionals that are operating in the top 1% 8. Community with other top GTM operators > Meet other pros in the space, share alpha, or just make friends! > We’ll coordinate quarterly in-person meet ups (if you’re in the LA area, I’ll get you a coffee) 9. Exclusive guest appearances with top players > Monthly guest appearances with founders that are making waves in GTM --- If you’ve found value from my content, this premium group is on ANOTHER LEVEL of value, like 1,000X value. And you can get access to all of this for an ALL-TIME LOW pre-sale price for the next 72 hours ONLY. Once Monday hits, this pre-sale offer price is gone FOREVER. Want access to this one time pre-sale offer? 👉 Comment "ELITES" and I'll DM you the link for access.

Introducing: GTM Elites The premium community for top 1% outbound & GTM operators. Over the last few months, I have been quietly building GTM Elites, what will be THE most valuable outbound/GTM community on the market in 2026. Here’s what the community will include: 1. Access to our end-to-end outbound / GTM / cold email course with over 100 modules covering: > How we setup Claude Code & practical + advanced ways we use it for outbound/GTM > 30+ Clay workflow breakdowns with workbook templates you can plug-n-play > Swipe file of 200+ top performing email scripts (can use as a context file for CC) > Step-by-step walkthrough of the campaign creation process that's driven 30,000+ positive responses for our clients > Full walkthrough to setup a top 0.1% cold email infrastructure > Dozens of masterclasses covering messaging, list building, and campaign creation > All recordings from past internal trainings, insider calls, and webinars Modules will be updated weekly over time to stay up to date with the latest shifts in GTM. 2. THREE weekly 1-hour group calls with myself, Shaw, and Lohit > Wednesday: GTM Strategy workshops with Shaw (head of GTM @ Pipeline tech) > Thursday: Claude Code & Clay sessions with Lohit (COO @ Pipeline tech) > Friday: Campaign & strategy review sessions with Christian (Founder @ Pipeline tech) Combined, our coaches have 11+ years of GTM experience, sent 10,000,000+ emails, generated 30,000+ leads, and $ 70M in pipeline. Our calls will be open floor Q&A style — so any questions you have, we’ll be there to answer no matter how niche or technical. 3. Daily GTM insight posts from myself or the coaches > New skills we’re building with Claude Code > New Clay workbook templates > Internal campaign insights on what's working right now > Real-time market shifts to be aware of > Early GTM tool finds 4. Personal DM access to myself and coaches > #/ask-the-experts channel, get questions answered in 24 hours > DM us individually and we’ll get back within 48 hours > Access on live calls for questions as well 5. Access to exclusive discounts to BEST in market software only available in GTM Elites > Ocean io > ScaledMail > EmailBison > Prospeo > Sending ac Any popular tools that the community wants to get discounts on, we’ll reach out to the providers for the community directly and secure us exclusive discounts. 6. Exclusive weekly workflow drops > Get access to new Claude code skills, Clay workbook templates, & n8n templates that we’re building and using for ourselves and clients in real time 7. Job/Hiring opportunities > Live GTM Job Board Monitoring > Job opportunities from others in the community > Looking to hire? Our community is going to have GTM professionals that are operating in the top 1% 8. Community with other top GTM operators > Meet other pros in the space, share alpha, or just make friends! > We’ll coordinate quarterly in-person meet ups (if you’re in the LA area, I’ll get you a coffee) 9. Exclusive guest appearances with top players > Monthly guest appearances with founders that are making waves in GTM --- If you’ve found value from my content, this premium group is on ANOTHER LEVEL of value, like 1,000X value. And you can get access to all of this for an ALL-TIME LOW pre-sale price for the next 72 hours ONLY. Once Monday hits, this pre-sale offer price is gone FOREVER. Want access to this one time pre-sale offer? 👉 Comment "ELITES" and I'll DM you the link for access.

Christian

13,612 görüntüleme • 5 ay önce

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

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

Kid Pak

59,447 görüntüleme • 5 ay önce

Use this prompt in OpenClaw to create your own AI agent command center that syncs up your life like Tony Stark's Jarvis in Iron Man. Adapt the specifics (agent names, data sources, branding) below to your own setup. Prompt: Build me a mission control dashboard for my OpenClaw AI agent system. Stack: Next.js 15 (App Router) + Convex (real-time backend) + Tailwind CSS v4 + Framer Motion + ShadCN UI + Lucide icons. TypeScript throughout. This is the command center where I monitor and control my autonomous AI agent(s) running on OpenClaw. The agent operates 24/7 on a Mac Mini, connected to Telegram/Discord, running cron jobs, spawning sub-agents, and reading/writing to a filesystem-based memory and state system. Dark mode only. Ultra-premium aesthetic, think Iron Man's JARVIS HUD meets a Bloomberg terminal. Subtle glass effects (backdrop-blur-xl, bg-white/[0.03]), no heavy gradients or glow. Rounded corners (16-20px on cards). Framer Motion for page transitions, stagger animations on card grids, spring physics on interactions. Mobile-first responsive. Never cookie-cutter. ## Architecture The dashboard reads live data from TWO sources: 1. Convex: real-time database for structured data (tasks, contacts, content drafts, calendar events, activity logs) 2. Local API routes (`/api/*`): read files from the agent's workspace filesystem at `~/.openclaw/workspace/` and return JSON. This is how live system state flows into the dashboard. ## Pages & Views (8 nav items, some with tab sub-views) ### 1. HOME (`/`) Dashboard overview. Grid of live status cards: - System Health: read from `/api/system-state` (parses `state/servers.json`). Show each service with UP/DOWN indicator, port, last check time. - Agent Status: read from `/api/agents` (parses `agents/registry.json` + agent workspace files). Show active agent count, healthy/unhealthy ratio, active sub-agent count from OpenClaw sessions API. - Cron Health: read from `/api/cron-health` (parses `state/crons.json`). Table of all scheduled jobs with name, schedule, last status (green/red dot), consecutive errors. - Revenue Tracker: read from `/api/revenue` (parses `state/revenue.json`). Current revenue, monthly burn, net. - Content Pipeline: read from `/api/content-pipeline` (parses `content/queue.md`). Kanban-style: Draft | Review | Approved | Published counts. - Quick Stats: total tasks, pending approvals, active sessions, uptime. All panels auto-refresh every 15 seconds. Live indicator dot + "AUTO 15S" badge in header. ### 2. OPS (`/ops`) with 3 tabs: Operations | Tasks | Calendar Operations tab: Full operational view. Server health table, branch status (from `state/branch-check.json`), observations feed (from `state/observations.md`), system priorities (from `shared-context/priorities.md`). Tasks tab: Strategic task suggestion system. API route `/api/suggested-tasks` reads/writes `state/suggested-tasks.json`. Cards grouped by category (Revenue, Product, Community, Content, Operations, Clients, Trading, Brand) with emoji headers. Each card shows title, reasoning, next action, priority badge, effort badge, approve/reject buttons. Filter bar by status and category. Calendar tab: Weekly calendar view from Convex `calendarEvents` table. Drag-to-create, color-coded by type, time slots. ### 3. AGENTS (`/agents`) with 2 tabs: Agents | Models Agents tab: Card grid of all registered agents from `/api/agents`. Each card shows name, role, model, level (L1-L4), status. Cards are CLICKABLE: expanding into a detail panel showing: - Agent personality (reads their SOUL .md) - Capabilities and rules (reads their RULES .md) - Sub-agents they can spawn - Recent outputs (reads from `shared-context/agent-outputs/`) Models tab: Model inventory table showing all available models, their routing (which tasks go to which model), costs, and failover chains. ### 4. CHAT (`/chat`): 2 tabs: Chat | Command Chat tab: Chat interface to communicate with the agent. Left sidebar shows session list (from `/api/chat-history` reading .jsonl transcript files). Main area shows messages with role-aligned bubbles (user right, assistant left), date separators, channel badges (telegram/discord/webchat). Input bar with send button + voice input (Web Speech API with SpeechRecognition). Messages sent via `/api/chat-send` which queues to a file the agent reads. Command tab: Quick command interface for common operations. ### 5. CONTENT (`/content`) Content pipeline management. Read from Convex `contentDrafts` table AND `/api/content-pipeline`. Show drafts in kanban columns. Each card shows title, platform target, draft text preview, status, created date. Edit/approve/reject actions. ### 6. COMMS (`/comms`) with 2 tabs: Comms | CRM Comms tab: Communication hub showing recent Discord digest, Telegram messages, notification history. CRM tab: Client pipeline kanban (Prospect → Contacted → Meeting → Proposal → Active). API route `/api/clients` reads markdown files from `clients/` directory. Each card shows client name, status, contacts, last interaction, next action. ### 7. KNOWLEDGE (`/knowledge`) with 2 tabs: Knowledge | Ecosystem Knowledge tab: Searchable knowledge base. Global search across all workspace files using `/api/knowledge` endpoint. Ecosystem tab: Product grid showing all products/apps in the ecosystem. Each card shows product name, status (Active/Development/Concept), health indicator, key metrics. Cards link to `/ecosystem/[slug]` detail pages with tabbed views (Overview, Brand, Community, Content, Legal, Product, Website, Actions). Detail pages read from `/api/ecosystem/[slug]` which parses workspace memory files. ### 8. CODE (`/code`) Code pipeline view. Shows repositories from `/api/repos` (scans ~/Desktop/Projects/ for git repos). Each repo card shows name, branch, last commit, dirty file count, language breakdown. Detail view at `/api/repos/detail` shows recent commits, file tree, open PRs. ## Navigation Top horizontal nav bar, NOT sidebar. All 8 items visible at all viewport widths. Use `flex` layout with `flex-1` items. Text size uses `clamp(0.45rem, 0.75vw, 0.6875rem)` for fluid scaling. Active item gets `text-primary bg-primary/[0.06]` static highlight (no sliding animation). Agent/app name visible at md+ breakpoints (`hidden md:inline`). Tab sub-views use a reusable `TabBar` component with pill/glass styling and Framer Motion `layoutId` transitions. Tab state stored in URL via `?tab=` search params. ## API Routes (all under `src/app/api/`) Each API route reads from the agent's workspace filesystem and returns JSON: - `/api/system-state` → reads `state/servers.json`, `state/branch-check.json` - `/api/agents` → reads `agents/registry.json`, agent SOUL .md files - `/api/agents/[id]` → reads specific agent's SOUL .md, RULES .md, outputs - `/api/cron-health` → reads `state/crons.json` - `/api/revenue` → reads `state/revenue.json` - `/api/content-pipeline` → parses `content/queue.md` (markdown with status markers) - `/api/suggested-tasks` → GET (read) / POST (approve/reject) on `state/suggested-tasks.json` - `/api/observations` → reads `state/observations.md` - `/api/priorities` → reads `shared-context/priorities.md` - `/api/chat-history` → reads .jsonl transcript files with pagination/search/channel filter - `/api/chat-send` → writes to queue file - `/api/clients` → reads markdown files from `clients/` directory - `/api/ecosystem/[slug]` → reads memory files for specific ecosystem - `/api/repos` → scans project directories for git repos - `/api/health` → returns status, uptime, memory usage, Convex connectivity All filesystem paths should be configurable via environment variable (default: `~/.openclaw/workspace/`). ## Convex Schema Define tables for: activities, calendarEvents, tasks, contacts, contentDrafts, ecosystemProducts. Include seed scripts (`convex/seed.ts`) to populate initial data. ## Key Design Rules - Mobile-first, test at 320px minimum - Font sizes 10-14px for body text, everything must fit naturally at small viewports - Cards use consistent border radius (16-20px) - Glass cards: `bg-white/[0.03] backdrop-blur-xl border border-white/[0.06]` - No heavy blur blobs or grain overlays - Stagger animations on card grids (0.05s delay per item) - Skeleton loading states for all async data - Custom scrollbar styling - Empty states with helpful messaging - All text must use Inter or system font stack - Never mix sharp and rounded corners in the same view - Premium = lighter feel, more whitespace, less visual noise ## File Structure ``` src/ app/ page.tsx, layout.tsx, providers.tsx agents/page.tsx calendar/page.tsx chat/page.tsx code/page.tsx comms/page.tsx content/page.tsx ecosystem/page.tsx, ecosystem/[slug]/page.tsx knowledge/page.tsx ops/page.tsx api/[...all routes above] components/ nav.tsx tab-bar.tsx dashboard-overview.tsx ops-view.tsx, suggested-tasks-view.tsx agents-view.tsx, models-view.tsx chat-center-view.tsx, voice-input.tsx content-view.tsx comms-view.tsx, crm-view.tsx knowledge-base.tsx, ecosystem-view.tsx code-pipeline.tsx activity-feed.tsx, calendar-view.tsx ui/ (ShadCN primitives) hooks/ lib/ convex/ schema.ts functions for each table seed.ts ``` Build the complete application. Every component, every API route, every Convex function. Production-quality code and premium design, not stubs. Dark mode only. Make it look incredibly beautiful and premium, no cookie cutter UI / AI slop.

klöss

202,812 görüntüleme • 8 ay önce

"What NewJeans Wanted to Say" [Full transcript translated to English] 240911 19:00 KST Hyein: Some of you might be surprised by this sudden meeting, but we wanted to share our thoughts and opinions about the recent events, so we prepared this session. First, I want to explain one of the reasons we decided to do this live. It's been hard to see many people who have worked with us continue to suffer from unfair demands and pressure even after our CEO was dismissed. It was frustrating to just stand by and watch these situations unfold, and we were very worried about our future as a group of five. Honestly, while preparing for this live, we were naturally concerned about the reactions we might receive afterward. We were also worried that people might mistakenly think that our CEO instructed us to do this, but I want to clarify that this live was prepared because we five members genuinely wanted to express our thoughts. We received help from directors we trust for things we couldn't prepare ourselves, like setting up the shoot and finding a location. It didn’t feel right for us to stay silent when everyone, including our Bunnies, has been stepping up to support us. Moreover, this is not just a matter of leaving it to the adults because it directly affects the lives of us five members. Since we're the ones going through this, we felt that it would be healthier to speak up ourselves than to do nothing, so we mustered the courage to do so. The main point of what we want to say today is directed towards HYBE. We've already had meetings with the current management to express our opinions, but after seeing what happened afterward, it feels like our concerns weren't clearly conveyed. It seemed like communication was blocked, so we felt that preparing this live was the only way to properly share our thoughts and feelings. Minji: I’m sure that today’s announcement has shocked many of the staff as well, as they were not aware of it, and I imagine everyone watching is quite surprised too. We’ve thought a lot about where to begin, but since the purpose is to express our intentions, we’ll try to explain as clearly as possible. Of course, due to contractual issues, we can’t share everything, but we’ll be as honest as we can. After it was decided that we would debut as NewJeans, our members spent a lot of time getting to know Min Hee-jin Daepyonim, both as a group and individually. At first, I had reservations and a certain fear towards the adults we were working with, but Daepyonim was the first person to approach us in a way that allowed us to open up, which was initially awkward but eventually built trust. From before our debut until now, we’ve been aware of various issues related to our debut schedule and other matters. However, working with Daepyonim made us feel good, and I believe that’s why we were able to debut successfully and continue our activities until now. Danielle: Naturally, we all want to continue working with Daepyonim. Even before debuting as NewJeans and through all of the time that we spent together with Min Hee-jin Daepyonim, all of us felt that the music we wanted to make and the kind of world we wanted to build together, our vision, was similar in so many ways. With Min Hee-jin Daepyonim, we were able to prepare each and every task with sincere hearts, and I believe it shows in our work. Putting our sincere effort into something is only possible because of the people that we're working with have trust in each other and have that same vision. Min Hee-jin Daepyonim is not only the person that produces our music, but someone who makes NewJeans who we are. She discusses even the smallest details with us and explains them in ways that we can understand clearly. NewJeans has a distinct colour and tone, and this was created with Min Hee-jin Daepyonim. She is integral to NewJeans’ identity, and we all feel that she is irreplaceable. Haerin: However, even after our debut, there have been many unfair and incomprehensible incidents that you might not know about, and these incidents have only increased over time. As some of you may know, recently, videos from our trainee days and private records, such as medical information, were leaked. When I first saw that, I was really shocked. It was hard to understand how our company, which is supposed to protect us, failed to manage and allowed such information to be leaked. Naturally, this situation has made us worry that other strange or false information about us might spread in the future. Although we, along with our parents and Min Hee-jin Daepyonim, have raised concerns about this to HYBE, they haven’t resolved the issue, nor have they taken any proactive measures. Then, in the midst of all this, our CEO was dismissed, and we’re left wondering whom we can trust and rely on. We’ve come to the conclusion that if we don’t speak out about this now, no one will know what we’re going through. After much discussion among ourselves, we finally decided to take this step. Hanni: Something happened to me recently. The 4th floor of the HYBE building is where we get our hair and makeup done, so a lot of other artists and staff come and go there. One day, I was waiting alone in the hallway, and some staff from another team passed by. We greeted each other, but when they came back out a bit later, I heard one of their managers say, “Ignore her,” right in front of me. I could hear and see everything clearly. Even now, I still don’t understand why I had to go through that. Minji: When I heard about what Hanni experienced, I was really shocked. How could a manager from another team tell their members to ignore one of us, and say it so loudly that Hanni could hear it? Such unimaginable words and behavior were directed at us, yet there was no apology, nor did they even acknowledge their wrongdoing. Of course, I’m worried about how many more similar incidents might occur in the future and whether we’ll be subtly ostracized without anyone there to protect us. Hanni: I hope no one else has to go through something like that, but since it’s already happened once, I can’t help but feel scared that other members might experience the same thing. I spoke to the new CEO about it, but since I didn’t have evidence and it was considered too late, they seemed to brush it off, making me feel like there’s no one left to protect us. It really felt like the concern for us was gone, and even though I was being honest, it made me feel like I was suddenly being treated as a liar. Before, Min Hee-jin, our previous CEO, used to take care of us a lot. But now, while the new people say they’ll help, it’s just been months of excuses... excuses... excuses... They keep saying that it’s something they can’t resolve. But this is something that I personally went through and experienced, yet they are trying to dismiss it as if it’s my fault. I’m worried and scared about what might happen next. Minji: Of course, I’m worried about our future, but what’s most frightening is that the work we’ve already created is being compromised. Seeing the people who have poured their lives into creating our work being treated this way makes it hard to understand how this could be happening. The new management said they would separate producing and management, but we’ve always worked differently from other labels, and we thought that our way was a good one. Now, Daepyonim can no longer approve all matters, and we’re left wondering how we’re supposed to continue working as we did before. The recent statement from the new management also didn’t make sense to me. If they really didn’t intend to interfere with our producing, then the recent incident with Director Shin Woo-seok should never have happened, and it should have been handled differently. We are the ones directly involved with the copyrights and likeness rights of our content, yet they’re making decisions without our consent. In their statement, they kept saying they were acting to protect us and prevent our anxiety, but why do they keep insisting on this when they haven’t considered our wishes? We don’t want any more unnecessary issues to arise, and we want them to show respect and consideration for Daepyonim and all the directors who have worked with us. The things they’re doing right now are not in our best interest at all. Hanni: Something we all find very important, something that plays a very important role in our team's colour and image is our media content and creative production. Despite saying that they would leave all the creative production to our now former CEO, Min Hee-jin, through official statements that I think a lot of you might have already read or seen, and also during our personal meetings, they infringed our content. Content that not only we worked really hard on, but also our staff who spent endless hours to produce and release them solely for our fans. And if they had any understanding about what type of team we are, and the type of content that we create, they would have thought more deeply for crossing the line that they set for themselves. Because of this incident, we realized that there's not much we can do to prevent these type of issues. Personally, the way that ADOR used to run was the business management and creative production was not separated and was factors that played and worked in harmony with each other. That's how it worked and it was perfectly fine. It was our way of working and it was our CEO's way of producing NewJeans' content, which a lot of you were able to enjoy and appreciate. But now that she's no longer CEO, these factors that should have continued to work together in harmony are now being seen as two different areas of work. Minji: Besides this, there are many other incidents we’ve experienced that are beyond my understanding—things that are frightening and uncomfortable. These incidents naturally make us question whether HYBE really cares about NewJeans, and there are clear signs of this. However, it’s hard to discuss everything today because we’re not sure how far things could escalate. We just hope you can understand a little of what’s been on our minds and why we chose to speak out in this way. Danielle: As I mentioned earlier, our dream was to perform the music we want to make with Daepyonim, and we were working very hard toward that goal. But now, we can’t do that, and the plans we’ve made might not come to fruition. As Hanni unnie said earlier, just like that, the content that we released solely for our fans, for our bunnies, was instantly erased. And I truly can't understand why anyone would do this to a group, or just anyone in general. We were just working hard for the present, so what did we do wrong? A week after Daepyonim was dismissed, we found out that we could no longer work with the director we’ve been working with all this time, and we’re extremely anxious because we don’t know what will happen to the staff who have always worked hard for us. If they really care about us, they should stop saying that they prioritize the artists and instead let us do the music we love in an environment where we can be genuinely happy. Is that really so hard to do? It’s hard to fully express what’s in my heart, but in the end, the five of us just want to continue our activities with Min Hee-jin Daepyonim, as we have done so far. Haerin: Personally, I want to continue working with the people around us who have helped me grow mentally and made me feel alive. However, I can't understand, nor do I think I should have to understand, why external forces are constantly obstructing and hindering us. I absolutely cannot comprehend what is truly in our best interest or what is supposed to help us grow. And I feel so sorry and heartbroken that our Bunnies, who found comfort in us and shared joyful memories with us, have to go through this ordeal and worry about things they shouldn't have to. We almost lost the work that symbolizes the relationship between NewJeans and Bunnies, and we don't want to lose anything else. I refuse to conform to or follow the values of the society those people belong to, and because I believe that direction is not the right one, I will not choose to go that way. Hyein: We found out about the CEO's dismissal through the news on the very day it happened. It was so sudden and unimaginable for all of us, and honestly, it was really difficult for us to process. As artists under HYBE, the company's unilateral notification made it clear to us that they don't respect us at all. In the midst of this confusion, we heard through our manager that the new CEO wanted to meet with us. From the very first action taken by the newly appointed Juyoung, it was clear that there was no consideration for us. He claimed to care for us, to prioritize NewJeans, but looking at everything that has happened, it's evident that his words were just that—empty words. HYBE’s actions, like publishing articles that painted us in a bad light just a week before our comeback, make us question how any of this is supposed to be in our best interest. Minji: It's already been half a year of unnecessary and exhausting discussions about us and NewJeans, and even as a third party, it must be tiring. As the ones directly involved, it’s incredibly uncomfortable for us. We still have music we want to make and goals we want to achieve together, but as things stand now, it’s heartbreaking to think that we might lose not only the work we’ve created so far but also the identity of our team. That’s what makes us feel so helpless. We held this live stream to express our feelings because we sincerely want this tiresome conflict to end. Hanni: Like how we have our own and individual thoughts and feelings, we have the choice to choose how we will react to each situation, and we are not going to follow HYBE's every order blindly. We are more than well aware that this is getting in the way of our work, and that we should be treated much, much better than how we are right now. And it's very hard to believe that they are truly sincere about wanting to help us continue, to be able to continue to work with our Daepyonim, Min Hee-jin Daepyonim. Despite her being in the midst of all this current legal conflict, she's expected to plan and creatively produce our future endeavours in just only two months, which I personally think makes no sense at all. We don't want to hear all the empty words of how they're going to help us continue to work with Min Hee-jin, Daepyonim. And all we want is this legal conflict to be resolved and have our working environment returned back to normal the way it was before. Hyein: The way HYBE is operating right now feels dishonest and wrong to us. Please, stop interfering. Reinstating our CEO and returning us to the original ADOR environment we had before, with familiar people, not strangers, would make things right. We’re not asking for special treatment; we just want everyone to do their jobs well in their respective places. We’ll do our best in our roles too. We sincerely hope our request is heard. Danielle: From a human perspective, I hope you stop harassing our CEO, Min Hee-jin. Honestly, she seems so pitiful, and HYBE just comes across as an inhumane company. What can we possibly learn from a company like this? So, I really hope you stop bothering our CEO. Minji: What we want is the original ADOR, where CEO Min Hee-jin leads both management and production. The reason we're making this request is because it's a way to coexist peacefully without conflict with HYBE. If our message has been conveyed properly, we hope Chairman Bang and HYBE make a wise decision to restore ADOR to its original state by the 25th. Thank you for listening to us. NewJeans: Thank you. #NewJeans_Never_Die #NeverForget

"What NewJeans Wanted to Say" [Full transcript translated to English] 240911 19:00 KST Hyein: Some of you might be surprised by this sudden meeting, but we wanted to share our thoughts and opinions about the recent events, so we prepared this session. First, I want to explain one of the reasons we decided to do this live. It's been hard to see many people who have worked with us continue to suffer from unfair demands and pressure even after our CEO was dismissed. It was frustrating to just stand by and watch these situations unfold, and we were very worried about our future as a group of five. Honestly, while preparing for this live, we were naturally concerned about the reactions we might receive afterward. We were also worried that people might mistakenly think that our CEO instructed us to do this, but I want to clarify that this live was prepared because we five members genuinely wanted to express our thoughts. We received help from directors we trust for things we couldn't prepare ourselves, like setting up the shoot and finding a location. It didn’t feel right for us to stay silent when everyone, including our Bunnies, has been stepping up to support us. Moreover, this is not just a matter of leaving it to the adults because it directly affects the lives of us five members. Since we're the ones going through this, we felt that it would be healthier to speak up ourselves than to do nothing, so we mustered the courage to do so. The main point of what we want to say today is directed towards HYBE. We've already had meetings with the current management to express our opinions, but after seeing what happened afterward, it feels like our concerns weren't clearly conveyed. It seemed like communication was blocked, so we felt that preparing this live was the only way to properly share our thoughts and feelings. Minji: I’m sure that today’s announcement has shocked many of the staff as well, as they were not aware of it, and I imagine everyone watching is quite surprised too. We’ve thought a lot about where to begin, but since the purpose is to express our intentions, we’ll try to explain as clearly as possible. Of course, due to contractual issues, we can’t share everything, but we’ll be as honest as we can. After it was decided that we would debut as NewJeans, our members spent a lot of time getting to know Min Hee-jin Daepyonim, both as a group and individually. At first, I had reservations and a certain fear towards the adults we were working with, but Daepyonim was the first person to approach us in a way that allowed us to open up, which was initially awkward but eventually built trust. From before our debut until now, we’ve been aware of various issues related to our debut schedule and other matters. However, working with Daepyonim made us feel good, and I believe that’s why we were able to debut successfully and continue our activities until now. Danielle: Naturally, we all want to continue working with Daepyonim. Even before debuting as NewJeans and through all of the time that we spent together with Min Hee-jin Daepyonim, all of us felt that the music we wanted to make and the kind of world we wanted to build together, our vision, was similar in so many ways. With Min Hee-jin Daepyonim, we were able to prepare each and every task with sincere hearts, and I believe it shows in our work. Putting our sincere effort into something is only possible because of the people that we're working with have trust in each other and have that same vision. Min Hee-jin Daepyonim is not only the person that produces our music, but someone who makes NewJeans who we are. She discusses even the smallest details with us and explains them in ways that we can understand clearly. NewJeans has a distinct colour and tone, and this was created with Min Hee-jin Daepyonim. She is integral to NewJeans’ identity, and we all feel that she is irreplaceable. Haerin: However, even after our debut, there have been many unfair and incomprehensible incidents that you might not know about, and these incidents have only increased over time. As some of you may know, recently, videos from our trainee days and private records, such as medical information, were leaked. When I first saw that, I was really shocked. It was hard to understand how our company, which is supposed to protect us, failed to manage and allowed such information to be leaked. Naturally, this situation has made us worry that other strange or false information about us might spread in the future. Although we, along with our parents and Min Hee-jin Daepyonim, have raised concerns about this to HYBE, they haven’t resolved the issue, nor have they taken any proactive measures. Then, in the midst of all this, our CEO was dismissed, and we’re left wondering whom we can trust and rely on. We’ve come to the conclusion that if we don’t speak out about this now, no one will know what we’re going through. After much discussion among ourselves, we finally decided to take this step. Hanni: Something happened to me recently. The 4th floor of the HYBE building is where we get our hair and makeup done, so a lot of other artists and staff come and go there. One day, I was waiting alone in the hallway, and some staff from another team passed by. We greeted each other, but when they came back out a bit later, I heard one of their managers say, “Ignore her,” right in front of me. I could hear and see everything clearly. Even now, I still don’t understand why I had to go through that. Minji: When I heard about what Hanni experienced, I was really shocked. How could a manager from another team tell their members to ignore one of us, and say it so loudly that Hanni could hear it? Such unimaginable words and behavior were directed at us, yet there was no apology, nor did they even acknowledge their wrongdoing. Of course, I’m worried about how many more similar incidents might occur in the future and whether we’ll be subtly ostracized without anyone there to protect us. Hanni: I hope no one else has to go through something like that, but since it’s already happened once, I can’t help but feel scared that other members might experience the same thing. I spoke to the new CEO about it, but since I didn’t have evidence and it was considered too late, they seemed to brush it off, making me feel like there’s no one left to protect us. It really felt like the concern for us was gone, and even though I was being honest, it made me feel like I was suddenly being treated as a liar. Before, Min Hee-jin, our previous CEO, used to take care of us a lot. But now, while the new people say they’ll help, it’s just been months of excuses... excuses... excuses... They keep saying that it’s something they can’t resolve. But this is something that I personally went through and experienced, yet they are trying to dismiss it as if it’s my fault. I’m worried and scared about what might happen next. Minji: Of course, I’m worried about our future, but what’s most frightening is that the work we’ve already created is being compromised. Seeing the people who have poured their lives into creating our work being treated this way makes it hard to understand how this could be happening. The new management said they would separate producing and management, but we’ve always worked differently from other labels, and we thought that our way was a good one. Now, Daepyonim can no longer approve all matters, and we’re left wondering how we’re supposed to continue working as we did before. The recent statement from the new management also didn’t make sense to me. If they really didn’t intend to interfere with our producing, then the recent incident with Director Shin Woo-seok should never have happened, and it should have been handled differently. We are the ones directly involved with the copyrights and likeness rights of our content, yet they’re making decisions without our consent. In their statement, they kept saying they were acting to protect us and prevent our anxiety, but why do they keep insisting on this when they haven’t considered our wishes? We don’t want any more unnecessary issues to arise, and we want them to show respect and consideration for Daepyonim and all the directors who have worked with us. The things they’re doing right now are not in our best interest at all. Hanni: Something we all find very important, something that plays a very important role in our team's colour and image is our media content and creative production. Despite saying that they would leave all the creative production to our now former CEO, Min Hee-jin, through official statements that I think a lot of you might have already read or seen, and also during our personal meetings, they infringed our content. Content that not only we worked really hard on, but also our staff who spent endless hours to produce and release them solely for our fans. And if they had any understanding about what type of team we are, and the type of content that we create, they would have thought more deeply for crossing the line that they set for themselves. Because of this incident, we realized that there's not much we can do to prevent these type of issues. Personally, the way that ADOR used to run was the business management and creative production was not separated and was factors that played and worked in harmony with each other. That's how it worked and it was perfectly fine. It was our way of working and it was our CEO's way of producing NewJeans' content, which a lot of you were able to enjoy and appreciate. But now that she's no longer CEO, these factors that should have continued to work together in harmony are now being seen as two different areas of work. Minji: Besides this, there are many other incidents we’ve experienced that are beyond my understanding—things that are frightening and uncomfortable. These incidents naturally make us question whether HYBE really cares about NewJeans, and there are clear signs of this. However, it’s hard to discuss everything today because we’re not sure how far things could escalate. We just hope you can understand a little of what’s been on our minds and why we chose to speak out in this way. Danielle: As I mentioned earlier, our dream was to perform the music we want to make with Daepyonim, and we were working very hard toward that goal. But now, we can’t do that, and the plans we’ve made might not come to fruition. As Hanni unnie said earlier, just like that, the content that we released solely for our fans, for our bunnies, was instantly erased. And I truly can't understand why anyone would do this to a group, or just anyone in general. We were just working hard for the present, so what did we do wrong? A week after Daepyonim was dismissed, we found out that we could no longer work with the director we’ve been working with all this time, and we’re extremely anxious because we don’t know what will happen to the staff who have always worked hard for us. If they really care about us, they should stop saying that they prioritize the artists and instead let us do the music we love in an environment where we can be genuinely happy. Is that really so hard to do? It’s hard to fully express what’s in my heart, but in the end, the five of us just want to continue our activities with Min Hee-jin Daepyonim, as we have done so far. Haerin: Personally, I want to continue working with the people around us who have helped me grow mentally and made me feel alive. However, I can't understand, nor do I think I should have to understand, why external forces are constantly obstructing and hindering us. I absolutely cannot comprehend what is truly in our best interest or what is supposed to help us grow. And I feel so sorry and heartbroken that our Bunnies, who found comfort in us and shared joyful memories with us, have to go through this ordeal and worry about things they shouldn't have to. We almost lost the work that symbolizes the relationship between NewJeans and Bunnies, and we don't want to lose anything else. I refuse to conform to or follow the values of the society those people belong to, and because I believe that direction is not the right one, I will not choose to go that way. Hyein: We found out about the CEO's dismissal through the news on the very day it happened. It was so sudden and unimaginable for all of us, and honestly, it was really difficult for us to process. As artists under HYBE, the company's unilateral notification made it clear to us that they don't respect us at all. In the midst of this confusion, we heard through our manager that the new CEO wanted to meet with us. From the very first action taken by the newly appointed Juyoung, it was clear that there was no consideration for us. He claimed to care for us, to prioritize NewJeans, but looking at everything that has happened, it's evident that his words were just that—empty words. HYBE’s actions, like publishing articles that painted us in a bad light just a week before our comeback, make us question how any of this is supposed to be in our best interest. Minji: It's already been half a year of unnecessary and exhausting discussions about us and NewJeans, and even as a third party, it must be tiring. As the ones directly involved, it’s incredibly uncomfortable for us. We still have music we want to make and goals we want to achieve together, but as things stand now, it’s heartbreaking to think that we might lose not only the work we’ve created so far but also the identity of our team. That’s what makes us feel so helpless. We held this live stream to express our feelings because we sincerely want this tiresome conflict to end. Hanni: Like how we have our own and individual thoughts and feelings, we have the choice to choose how we will react to each situation, and we are not going to follow HYBE's every order blindly. We are more than well aware that this is getting in the way of our work, and that we should be treated much, much better than how we are right now. And it's very hard to believe that they are truly sincere about wanting to help us continue, to be able to continue to work with our Daepyonim, Min Hee-jin Daepyonim. Despite her being in the midst of all this current legal conflict, she's expected to plan and creatively produce our future endeavours in just only two months, which I personally think makes no sense at all. We don't want to hear all the empty words of how they're going to help us continue to work with Min Hee-jin, Daepyonim. And all we want is this legal conflict to be resolved and have our working environment returned back to normal the way it was before. Hyein: The way HYBE is operating right now feels dishonest and wrong to us. Please, stop interfering. Reinstating our CEO and returning us to the original ADOR environment we had before, with familiar people, not strangers, would make things right. We’re not asking for special treatment; we just want everyone to do their jobs well in their respective places. We’ll do our best in our roles too. We sincerely hope our request is heard. Danielle: From a human perspective, I hope you stop harassing our CEO, Min Hee-jin. Honestly, she seems so pitiful, and HYBE just comes across as an inhumane company. What can we possibly learn from a company like this? So, I really hope you stop bothering our CEO. Minji: What we want is the original ADOR, where CEO Min Hee-jin leads both management and production. The reason we're making this request is because it's a way to coexist peacefully without conflict with HYBE. If our message has been conveyed properly, we hope Chairman Bang and HYBE make a wise decision to restore ADOR to its original state by the 25th. Thank you for listening to us. NewJeans: Thank you. #NewJeans_Never_Die #NeverForget

1tokki

19,445 görüntüleme • 11 ay önce