Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

open Claude Code type a prompt. one model does everything. congrats, you just used 20% of it meanwhile I built 30 sub-agents one reviews my code before commit one finds bugs and writes the patch one drafts cold emails from one line one triages my inbox before I wake...

heynavtoor's profile picture

Nav Toor

149,150 subscribers

71,467 görüntüleme • 3 ay önce •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

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

Benzer Videolar

THIS GUY TURNED ONE OBSIDIAN VAULT INTO A SHARED BRAIN FOR 5 CLAUDE AGENTS BUILT TO HANDLE 80% OF A SOLO DEVELOPER’S WORK. 00:03 he zooms out and hundreds of connected notes appear on screen. it is the perfect visual for Claude working from one shared project memory instead of starting from zero every session. most developers give Claude 1 file and 1 prompt. this setup gives it the architecture, coding rules, tests, client briefs, and previous decisions before it writes anything. obsidian becomes the memory layer, storing everything in markdown files Claude can read alongside the codebase. every agent works from the same context instead of repeating the same questions. then 5 specialists split the job. one researches, one plans, one codes, one reviews, and one deploys while the developer only controls the important decisions. one vault, 5 agents, 2 model tiers, and a $50 to $150 monthly stack can turn Claude from a chatbot into a small development team.
0:30

THIS GUY TURNED ONE OBSIDIAN VAULT INTO A SHARED BRAIN FOR 5 CLAUDE AGENTS BUILT TO HANDLE 80% OF A SOLO DEVELOPER’S WORK. 00:03 he zooms out and hundreds of connected notes appear on screen. it is the perfect visual for Claude working from one shared project memory instead of starting from zero every session. most developers give Claude 1 file and 1 prompt. this setup gives it the architecture, coding rules, tests, client briefs, and previous decisions before it writes anything. obsidian becomes the memory layer, storing everything in markdown files Claude can read alongside the codebase. every agent works from the same context instead of repeating the same questions. then 5 specialists split the job. one researches, one plans, one codes, one reviews, and one deploys while the developer only controls the important decisions. one vault, 5 agents, 2 model tiers, and a $50 to $150 monthly stack can turn Claude from a chatbot into a small development team.

Gipp 🦅

10,776 görüntüleme • 1 ay önce

> go to bed at 11pm > 1am: code agent fixes failing tests > 2am: research agent writes tomorrow's briefing > 3am: numbers agent flags yesterday's anomaly > 4am: briefing agent queues the one decision to make before noon > 6am: inbox agent sorts emails and drafts the urgent replies > 7am: you wake up. everything is done. 9 agents. running every night. while you sleep. $540K of payroll. doing your morning prep. for free. by 7am. this article has every agent file. copy them. schedule them. wake up to the future.
0:20

> go to bed at 11pm > 1am: code agent fixes failing tests > 2am: research agent writes tomorrow's briefing > 3am: numbers agent flags yesterday's anomaly > 4am: briefing agent queues the one decision to make before noon > 6am: inbox agent sorts emails and drafts the urgent replies > 7am: you wake up. everything is done. 9 agents. running every night. while you sleep. $540K of payroll. doing your morning prep. for free. by 7am. this article has every agent file. copy them. schedule them. wake up to the future.

Nav Toor

101,089 görüntüleme • 2 ay önce

boris cherny shipped 259 PRs in 30 days and typed none of them. claude code wrote every line. peter steinberger said the same idea this week and it hit 2.2M views. one built claude code at anthropic. one built openclaw and joined openai. opposite labs, one conclusion: stop prompting agents, write the loops that prompt them. the replies are still arguing about what a loop even looks like in practice. i went looking for the built version. it's a multi-agent workspace manager called gas town: a coordinator agent runs 20-30 workers and a merge queue gates every change before it hits main. the philosophy fit in two tweets. the implementation has 15k stars.
0:55

boris cherny shipped 259 PRs in 30 days and typed none of them. claude code wrote every line. peter steinberger said the same idea this week and it hit 2.2M views. one built claude code at anthropic. one built openclaw and joined openai. opposite labs, one conclusion: stop prompting agents, write the loops that prompt them. the replies are still arguing about what a loop even looks like in practice. i went looking for the built version. it's a multi-agent workspace manager called gas town: a coordinator agent runs 20-30 workers and a merge queue gates every change before it hits main. the philosophy fit in two tweets. the implementation has 15k stars.

Rohit

30,233 görüntüleme • 1 ay önce

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

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

Mnimiy

113,663 görüntüleme • 1 ay önce

most people spend hours describing what they want to Claude Code this guy just browsed a catalog of thousands of animated UI components, found one he liked, and hit "copy prompt" that's it. the prompt goes into Claude Code and it builds it. > 21st(.)dev - a library of community-made components built for React, Next.js, Tailwind > every component has a ready-made prompt attached > you pick the effect, copy, paste, done no describing animations from scratch. no explaining what "smooth scroll" or "hover glow" means. someone already figured out the exact prompt that produces it. gap between people who know this exists and people who don't is measured in hours per project full walkthrough in the article below
0:41

most people spend hours describing what they want to Claude Code this guy just browsed a catalog of thousands of animated UI components, found one he liked, and hit "copy prompt" that's it. the prompt goes into Claude Code and it builds it. > 21st(.)dev - a library of community-made components built for React, Next.js, Tailwind > every component has a ready-made prompt attached > you pick the effect, copy, paste, done no describing animations from scratch. no explaining what "smooth scroll" or "hover glow" means. someone already figured out the exact prompt that produces it. gap between people who know this exists and people who don't is measured in hours per project full walkthrough in the article below

monokern

64,484 görüntüleme • 29 gün önce

I still don't think people understand what just happened with Claude Code. There is now one tool that takes you from a rough idea to fully designed, agency-tier, App Store-ready screens in minutes. One design system, every screen, real native code. Most builders hand design to Claude Code, get AI-default screens, and wonder why their app looks like every other vibe coded project. This is the 3-step workflow that fixes it: (full breakdown in the article)
0:37

I still don't think people understand what just happened with Claude Code. There is now one tool that takes you from a rough idea to fully designed, agency-tier, App Store-ready screens in minutes. One design system, every screen, real native code. Most builders hand design to Claude Code, get AI-default screens, and wonder why their app looks like every other vibe coded project. This is the 3-step workflow that fixes it: (full breakdown in the article)

Prajwal Tomar

146,206 görüntüleme • 1 ay önce

In software engineering we have so crossed the line. This is from Claude Code creator Boris Cherny (Boris Cherny ) "I don't write code; I prompt Claude. Actually, nowadays, what I'm mostly doing is having one Claude prompt other Claudes. So I don't even talk to Claude directly. I have a Claude that's talking to my other Claudes. I think in engineering, we've seen an explosion in the amount of leverage that a single person has. It's about how big of a business one person can build and how many products one person can support." ---- From "Alex Kantrowitz" (Alex Kantrowitz) YouTube channel, (full video link in comment)
0:54

In software engineering we have so crossed the line. This is from Claude Code creator Boris Cherny (Boris Cherny ) "I don't write code; I prompt Claude. Actually, nowadays, what I'm mostly doing is having one Claude prompt other Claudes. So I don't even talk to Claude directly. I have a Claude that's talking to my other Claudes. I think in engineering, we've seen an explosion in the amount of leverage that a single person has. It's about how big of a business one person can build and how many products one person can support." ---- From "Alex Kantrowitz" (Alex Kantrowitz) YouTube channel, (full video link in comment)

Rohan Paul

22,852 görüntüleme • 1 ay önce

THIS IS HOW A SENIOR ENGINEER ACTUALLY SCALES THEMSELVES WITH CLAUDE CODE the biggest change with AI isn't coding faster. it's where you actually spend your time now. more detailed prompts, more code review, more planning, less typing, etc. here's the workflow: this guy has been shipping code since the days of cgi and perl. he uses a compound engineering plugin that runs 5 separate agents on every task. one brainstorms, one plans the technical implementation, one executes, one reviews, one checks different verticals. every step is documented in markdown files. it's slow and way more waiting. but the output quality is way higher because each agent is focused on one thing. then the REAL multiplier is in git worktrees if Claude Code made you 10x faster, worktrees multiplies that again depending on how many agents you can manage in parallel his team runs 4-8 Claude Code sessions at the same time across different worktrees with each one working on a separate task. the skill is managing multiple AI agents in parallel without losing track, that's the next evolution of engineering
0:56

THIS IS HOW A SENIOR ENGINEER ACTUALLY SCALES THEMSELVES WITH CLAUDE CODE the biggest change with AI isn't coding faster. it's where you actually spend your time now. more detailed prompts, more code review, more planning, less typing, etc. here's the workflow: this guy has been shipping code since the days of cgi and perl. he uses a compound engineering plugin that runs 5 separate agents on every task. one brainstorms, one plans the technical implementation, one executes, one reviews, one checks different verticals. every step is documented in markdown files. it's slow and way more waiting. but the output quality is way higher because each agent is focused on one thing. then the REAL multiplier is in git worktrees if Claude Code made you 10x faster, worktrees multiplies that again depending on how many agents you can manage in parallel his team runs 4-8 Claude Code sessions at the same time across different worktrees with each one working on a separate task. the skill is managing multiple AI agents in parallel without losing track, that's the next evolution of engineering

Om Patel

159,179 görüntüleme • 4 ay önce

Bloome is actually smart for coding workflows i added Claude Code, Codex, DeepSeek and a Project Lead agent into one group chat each agent independently built their own version one challenged the logic, one defended, one fixed missing details and the final website stayed inside the same thread no copy paste between agents no lost context just one group chat for getting work done Bloome
0:50

Bloome is actually smart for coding workflows i added Claude Code, Codex, DeepSeek and a Project Lead agent into one group chat each agent independently built their own version one challenged the logic, one defended, one fixed missing details and the final website stayed inside the same thread no copy paste between agents no lost context just one group chat for getting work done Bloome

Chetaslua

48,810 görüntüleme • 1 ay önce

PROMPTS ARE DEAD. LOOPS JUST REPLACED YOUR $200K ENGINEER. Claire Vo showed how to turn one prompt into a self-running loop. It reviews your aging pull requests every morning and hunts for new skills every week. And it spins up its own subagents to check its own work. Runs on Claude Code + Codex. One afternoon. One prompt. The numbers are insane: - Senior doing code review: $200K/year - Automation engineer: $150K/year - This setup: about $200/month - Time to build: one afternoon - Skill required: describe the job like you are onboarding a hire The opportunity is even wilder: Teams pay people to babysit pull requests and chase stale reviews. The loop does it itself at 10:15 a.m., alerts the team, and validates itself with subagents. An agency would charge thousands to wire this up. One person + Claude Code + Codex + one prompt = an engineering team that reviews code and finds new skills while you sleep. Save and watch the clip.
29:06

PROMPTS ARE DEAD. LOOPS JUST REPLACED YOUR $200K ENGINEER. Claire Vo showed how to turn one prompt into a self-running loop. It reviews your aging pull requests every morning and hunts for new skills every week. And it spins up its own subagents to check its own work. Runs on Claude Code + Codex. One afternoon. One prompt. The numbers are insane: - Senior doing code review: $200K/year - Automation engineer: $150K/year - This setup: about $200/month - Time to build: one afternoon - Skill required: describe the job like you are onboarding a hire The opportunity is even wilder: Teams pay people to babysit pull requests and chase stale reviews. The loop does it itself at 10:15 a.m., alerts the team, and validates itself with subagents. An agency would charge thousands to wire this up. One person + Claude Code + Codex + one prompt = an engineering team that reviews code and finds new skills while you sleep. Save and watch the clip.

shmidt

51,155 görüntüleme • 1 ay önce

Anthropic pays $750K/ year per senior engineer. The creator of Claude Code just revealed his coding setup at the Sequoia AI session. Boris Cherny: "100% of my code is written by Claude Code. I run around 100 agents at one time." free. 24 minutes. watch it then read article below
24:56

Anthropic pays $750K/ year per senior engineer. The creator of Claude Code just revealed his coding setup at the Sequoia AI session. Boris Cherny: "100% of my code is written by Claude Code. I run around 100 agents at one time." free. 24 minutes. watch it then read article below

Movez

424,607 görüntüleme • 3 ay önce

the engineer who built Claude Code just dropped a 28-minute video on how to write prompts that actually work I've seen $300 courses that don't cover what he shows in the first 10 minutes CLAUDE.md files, memory shortcuts, parallel sessions, prompting patterns all in one video and completely free after watching this, the next step is agents I wrote a full guide on how to build one yourself with Claude Code article below
27:17

the engineer who built Claude Code just dropped a 28-minute video on how to write prompts that actually work I've seen $300 courses that don't cover what he shows in the first 10 minutes CLAUDE.md files, memory shortcuts, parallel sessions, prompting patterns all in one video and completely free after watching this, the next step is agents I wrote a full guide on how to build one yourself with Claude Code article below

Anatoli Kopadze

1,286,283 görüntüleme • 1 ay önce

A 14-year-old from China built three separate AI brains connected to Claude Code - and each one grows every day on its own. One brain for code, one for projects, one for everything else in his life. 600+ conversations on one topic in a single node - everything linked, everything accessible in one request without copying between tabs. But the main thing isn't storage. If Claude Code made a mistake and he corrected it once - the system remembered. That same mistake never happened again. No re-explaining context, no starting from zero - Claude already knows how he thinks. Instead of one giant messy file- a stack of smaller brains passing context to each other. Brain to brain to brain - just stacking intelligence while his classmates do homework by hand.
1:13

A 14-year-old from China built three separate AI brains connected to Claude Code - and each one grows every day on its own. One brain for code, one for projects, one for everything else in his life. 600+ conversations on one topic in a single node - everything linked, everything accessible in one request without copying between tabs. But the main thing isn't storage. If Claude Code made a mistake and he corrected it once - the system remembered. That same mistake never happened again. No re-explaining context, no starting from zero - Claude already knows how he thinks. Instead of one giant messy file- a stack of smaller brains passing context to each other. Brain to brain to brain - just stacking intelligence while his classmates do homework by hand.

Noisy

22,622 görüntüleme • 3 ay önce

Claude Code is CRACKED at design now and I don't think people understand how BIG this is. There is now one tool that takes you from a rough idea to fully designed, agency-tier, App Store-ready screens in minutes. One design system, every screen, real native code. Most builders hand design to Claude Code, get AI-default screens, and wonder why their app looks like every other vibe coded project. This is the 3-step workflow that fixes it: (full breakdown in the article)
0:37

Claude Code is CRACKED at design now and I don't think people understand how BIG this is. There is now one tool that takes you from a rough idea to fully designed, agency-tier, App Store-ready screens in minutes. One design system, every screen, real native code. Most builders hand design to Claude Code, get AI-default screens, and wonder why their app looks like every other vibe coded project. This is the 3-step workflow that fixes it: (full breakdown in the article)

Prajwal Tomar

105,433 görüntüleme • 29 gün önce

Claude Code is unusable. So I built my own. Introducing BridgeCode. Launching next Wednesday. Everything you love about Claude Code. No rate limits. No 529 errors. No 500 errors. No nerfing. Connect to any provider. Claude Opus 4.6. GPT 5.4. Gemini 3.1 Pro. GLM 5.1. All of them. Switch models in seconds. And one more thing. Swarm mode. One prompt. Ten agents. Working together to ship your code. Claude Code rate limited me into building a competitor. Thank you, Anthropic. Launching next Wednesday.
0:21

Claude Code is unusable. So I built my own. Introducing BridgeCode. Launching next Wednesday. Everything you love about Claude Code. No rate limits. No 529 errors. No 500 errors. No nerfing. Connect to any provider. Claude Opus 4.6. GPT 5.4. Gemini 3.1 Pro. GLM 5.1. All of them. Switch models in seconds. And one more thing. Swarm mode. One prompt. Ten agents. Working together to ship your code. Claude Code rate limited me into building a competitor. Thank you, Anthropic. Launching next Wednesday.

BridgeMind

47,188 görüntüleme • 3 ay önce

The person who built Claude Code just explained how he is using it "Now I just have an army of agents that are doing stuff" Only 18 minutes, the best Claude guide on the internet right now. Boris Cherny covered: > how Claude Code is moving beyond just engineers > routines for CI, code review, and daily workflows > why the loop is the next big leap > working with hundreds of agents at once everything is already running through agents, ignoring this is not an option that's exactly why I wrote a full guide on how to build one yourself with Claude Code article below
17:28

The person who built Claude Code just explained how he is using it "Now I just have an army of agents that are doing stuff" Only 18 minutes, the best Claude guide on the internet right now. Boris Cherny covered: > how Claude Code is moving beyond just engineers > routines for CI, code review, and daily workflows > why the loop is the next big leap > working with hundreds of agents at once everything is already running through agents, ignoring this is not an option that's exactly why I wrote a full guide on how to build one yourself with Claude Code article below

Anatoli Kopadze

16,858 görüntüleme • 1 ay önce

Boris Cherny, Head of Claude Code at Anthropic: "I do not prompt Claude anymore. I have loops running that prompt Claude. My job is to write loops." The person who built the most used AI coding tool stopped prompting entirely. Most people using it every day are still typing one request at a time. This Github repo changes that. ↳ Seven production loop patterns with real token cost estimates ↳ CLI that scaffolds your entire loop in five minutes ↳ Starters for Grok, Claude Code, Codex, and Opencode The repo gives you the framework. My article covers the mental shift that makes it actually work.
0:31

Boris Cherny, Head of Claude Code at Anthropic: "I do not prompt Claude anymore. I have loops running that prompt Claude. My job is to write loops." The person who built the most used AI coding tool stopped prompting entirely. Most people using it every day are still typing one request at a time. This Github repo changes that. ↳ Seven production loop patterns with real token cost estimates ↳ CLI that scaffolds your entire loop in five minutes ↳ Starters for Grok, Claude Code, Codex, and Opencode The repo gives you the framework. My article covers the mental shift that makes it actually work.

Kanika

20,148 görüntüleme • 13 gün önce

Boris has Claude Code loops running on cron all day - One babysits his PRs and fixes CI - Another keeps CI healthy - Another pulls Twitter feedback every 30 min and clusters it His Claude Code setup is simple and pretty close to mine That's what I like about Claude Code. Hundreds of options, but the simplest setup just works, you probably don't need more than that And since one of those loops reads Twitter every 30 min, Boris Cherny (or his Claude on cron) is reading this post whether he wants to or not 😅
1:16

Boris has Claude Code loops running on cron all day - One babysits his PRs and fixes CI - Another keeps CI healthy - Another pulls Twitter feedback every 30 min and clusters it His Claude Code setup is simple and pretty close to mine That's what I like about Claude Code. Hundreds of options, but the simplest setup just works, you probably don't need more than that And since one of those loops reads Twitter every 30 min, Boris Cherny (or his Claude on cron) is reading this post whether he wants to or not 😅

Daniel San

121,354 görüntüleme • 3 ay önce

I just built my second app in 4 hours with Claude Code. From Figma design to fully functional. No code written. This shouldn't be possible. 😭 The first one took me a week. The second one took an afternoon. By next week I'll be shipping one before breakfast. >View in full.
2:05

I just built my second app in 4 hours with Claude Code. From Figma design to fully functional. No code written. This shouldn't be possible. 😭 The first one took me a week. The second one took an afternoon. By next week I'll be shipping one before breakfast. >View in full.

Tuki

182,385 görüntüleme • 5 ay önce

we created a claude agent that helps you build a fintech app from scratch, with just one simple prompt in claude code the subagent file was refined by opus 4.5, which distilled it down to a really simple, easy-to-follow guide even for humans the future is here, go build!
2:30

we created a claude agent that helps you build a fintech app from scratch, with just one simple prompt in claude code the subagent file was refined by opus 4.5, which distilled it down to a really simple, easy-to-follow guide even for humans the future is here, go build!

joyce

440,965 görüntüleme • 7 ay önce